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)
- Who are developing this database?
- The main developer of this database is So Nakagawa working at Biomedical Informatics Laboratory, Tokai University School of Medicine
- How can I cite this database?
- 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.
- 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.
- 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).
- 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
- Note that, in the gEVE database, each EVE ORF may not start with an ATG codon.
- Are there LTR sequences stored in this database?
- No, currently.