• FluTrackers.com Inc. does not provide medical advice. Information on this web site is collected from various internet resources, and the FluTrackers board of directors makes no warranty to the safety, efficacy, correctness or completeness of the information posted on this site by any author or poster. The information collated here is for instructional and/or discussion purposes only and is NOT intended to diagnose or treat any disease, illness, or other medical condition. Every individual reader or poster should seek advice from their personal physician/healthcare practitioner before considering or using any interventions that are discussed on this website. By continuing to access this website you agree to consult your personal physican before using any interventions posted on this website, and you agree to hold harmless FluTrackers.com Inc., the board of directors, the members, and all authors and posters for any effects from use of any medication, supplement, vitamin or other substance, device, intervention, etc. mentioned in posts on this website, or other internet venues referenced in posts on this website.
  • We are not asking for any donations. Do not donate to any entity who says they are raising funds for us.

Sequencing artifacts in the type A influenza databases and attempts to correct them

tetano

Editor, Senior Moderator
Influenza Other Respir Viruses. 2014 Feb 7. doi: 10.1111/irv.12239. [Epub ahead of print]
Sequencing artifacts in the type A influenza databases and attempts to correct them.
Suarez DL, Chester N, Hatfield J.
Author information
Abstract
BACKGROUND:

There are over 276 000 influenza gene sequences in public databases, with the quality of the sequences determined by the contributor.
OBJECTIVE:

As part of a high school class project, influenza sequences with possible errors were identified in the public databases based on the size of the gene being longer than expected, with the hypothesis that these sequences would have an error. Students contacted sequence submitters alerting them of the possible sequence issue(s) and requested they the suspect sequence(s) be correct as appropriate.
METHODS:

Type A influenza viruses were screened, and gene segments longer than the accepted size were identified for further analysis. Attention was placed on sequences with additional nucleotides upstream or downstream of the highly conserved non-coding ends of the viral segments.
RESULTS AND CONCLUSIONS:

A total of 1081 sequences were identified that met this criterion. Three types of errors were commonly observed: non-influenza primer sequence wasn't removed from the sequence; PCR product was cloned and plasmid sequence was included in the sequence; and Taq polymerase added an adenine at the end of the PCR product. Internal insertions of nucleotide sequence were also commonly observed, but in many cases it was unclear if the sequence was correct or actually contained an error. A total of 215 sequences, or 22.8% of the suspect sequences, were corrected in the public databases in the first year of the student project. Unfortunately 138 additional sequences with possible errors were added to the databases in the second year. Additional awareness of the need for data integrity of sequences submitted to public databases is needed to fully reap the benefits of these large data sets.
CONCLUSIONS:

The findings support the rationale for a prime and boost immunization strategy in young children in whom maternal antibodies are present.

? 2014 The Authors. Influenza and Other Respiratory Viruses Published by John Wiley & Sons Ltd.
KEYWORDS:

databases, errors, influenza, sequence

PMID:
24512607
[PubMed - as supplied by publisher]

http://www.ncbi.nlm.nih.gov/pubmed/24512607
 
Re: Sequencing artifacts in the type A influenza databases and attempts to correct them

While I am all for cleaning up the sequence databases how on earth do you reach the conclusion
The findings support the rationale for a prime and boost immunization strategy in young children in whom maternal antibodies are present.
by finding lab sequencing errors?
 
Back
Top Bottom