-
Notifications
You must be signed in to change notification settings - Fork 61
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
Error in Nextclade-Pangolin annotation #760
Comments
Thanks for raising this. The software does exactly what it's supposed to. Let me explain. We find the nearest neighbour in the reference tree for the sample. The pango lineage reported is then that of the nearest neighbour. If there are lots of reversions and labeled mutations (i.e. There's no pango lineage for this sequence (yet) so there's also no right way to call it.
I'll think about whether it might be worth adding parentheses about Pango lineage calls when the results are not trustworthy. You can read more about caveats here: https://docs.nextstrain.org/projects/nextclade/en/latest/user/algorithm/nextclade-pango.html It's worth noting that we don't claim to be 100% accurate. 98% accuracy means we expect to be wrong in 1 sequence out of 50. This sequence is very unusual, so it's not surprising Nextclade is wrong. Also this:
|
hCoV-19/India/KA-CBR-1402CTD094/2022
Issue raised for this particular sequences in pangolin-designation
This is supposed to be a XF lineage (Delta X BA.2 recombination), but nextclade is calling it XE lineage (BA.1 X BA.2). Kindly look into it
The text was updated successfully, but these errors were encountered: