Please email us for your comments or questions on this database.
(Important: Our contact Email address (geve@ml.u-tokai.ac.jp) has not work correctly for a while. We fixed the problem now and please email us again if you have not reply from us, 8/19, 2016)

  1. Who are developing this database?
  2. How can I cite this database?
      • Please cite the following paper: Nakagawa S and Takahashi MU, gEVE: a genome-based endogenous viral element database provides comprehensive viral protein-coding sequences in mammalian genomes. Database (Oxford) 2016 baw087. Web PDF
  3. Why only coding sequences stored in this database?
    • Firstly, we would like to provide “reliable” EVE sequences with viral motifs. But we may update the database that non-coding EVE sequences.
  4. Why only 20 genome sequences were analyzed?
    • Again, we carefully chose the genome sequences that were sequenced and assembled with relatively good quality. But in near future we may expand the genome sequences that are stored in the database.
  5. How did you define a sequence derived from viruses?
    • We currently define EVE sequences that meet the following two criteria: 1) possessed an ORF longer than 80 amino acids, 2) had functional viral motif sequences stored in Pfam and Gypsy databases (see About).
  6. What “nt_v1”, “ntm_v1”, “aa_v1”, or “aam_v1” means in the BLAST database?
    • Note that, in the gEVE database, each EVE ORF may not start with an ATG codon.
      • nt_v1: nucleotide sequences of all ORFs in the gEVE database version 1
      • ntm_v1: nucleotide sequence of all ORFs in the gEVE database version1, starting with an ATG codon
      • aa_v1: translated amino acid sequences of nt_v1
      • aam_v1: translated amino acid sequences of ntm_v1
  7. Are there LTR sequences stored in this database?
    • No, currently.