-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
representation of a nuc conversion do not point a conversion on the genome #1107
Comments
Yes it looks like there are no (or very few) mutations observed at this position. It may have been a typo. Using all 4 defining positions we can see how they identify 22F. Note that these definitions are the ones we use for |
Thanks for your answer! What is the difference between augur clades and nextstrain clades? Are they not same or similar? In my case, I need either full fasta sequences or nucleotide changes of Nextstrain/Nextclade clades so that I can create |
cc @corneliusroemer - I think you have a fasta of representative sequences for each lineage? |
Would be great to hear if this exists. |
Hello,
For our research, I have been using resources from Nextstrain and I encountered an ambiguity that I wanted to ask about.
I am currently working on the tabular file for nuc conversions belonging to Nextstrain clades (https://github.com/nextstrain/ncov/blob/master/defaults/clades.tsv). I have been assuming that the clades.tsv represents nucleotide conversions, so they should inform about a nucleotide change compared to the reference genome.
However, I noticed that one of the conversions listed there, 22F nuc 15461 A, already points to A on the reference genome (NC_045512v2). Does this have an intended purpose or do I misunderstand the concept?
Thank you in advance for your response.
The text was updated successfully, but these errors were encountered: