Skip to content
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 BF.15 Nextclade #966

Closed
FedeGueli opened this issue Aug 24, 2022 · 4 comments
Closed

Error in BF.15 Nextclade #966

FedeGueli opened this issue Aug 24, 2022 · 4 comments
Labels
nextclade_data Concerning dataset part: reference tree, qc definitions etc

Comments

@FedeGueli
Copy link

Hi @corneliusroemer just to highlight something went wrong with the last nextclade update regarding BF.15 : it is defined by S:248H and it is around 150sequences but the nextclade Bf.15* query on covspectrum finds more than 4000 sequences and just a tiny bit with S: 248H

Nextclade for BF.15
https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?nextcladePangoLineage=BF.15*&

Real BF.15:
https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?aaMutations=S%3A248H&nextcladePangoLineage=BA.5.2.1*&

@FedeGueli FedeGueli added needs triage Mark for review and label assignment t:talk Type: discussion of the application or the science behind it labels Aug 24, 2022
@corneliusroemer corneliusroemer added nextclade_data Concerning dataset part: reference tree, qc definitions etc and removed needs triage Mark for review and label assignment t:talk Type: discussion of the application or the science behind it labels Aug 25, 2022
@corneliusroemer
Copy link
Member

Thanks for reporting, I'll have a look.

You can check out the Nextclade tree here: https://nextstrain.org/nextclade/sars-cov-2

@corneliusroemer
Copy link
Member

Branch leading to BF.15* has these mutations - is that wrong?
image

The reason it's getting so many non-248 is that the branch is 3 mutations long, so having 2 mutations is enough to call this as BF.15

Not much I can do right now with the Nextclade algorithm as it is. Having the parent designated would help, so have BF.15 be broadened to the non-248, and then BF.15.1 be the 248 child.

Didn't you propose something like this anyways?

This is effectively what Nextclade does:
https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?variantQuery=nextcladePangoLineage%3ABA.5.2.1*+%26+T6979G+%26+%5B2-of%3A+T22304C+%2C+C26625T+%2C+C27371T%5D&

@corneliusroemer corneliusroemer closed this as not planned Won't fix, can't repro, duplicate, stale Aug 25, 2022
@FedeGueli
Copy link
Author

FedeGueli commented Aug 26, 2022

Thx @corneliusroemer ! Yeah i have proposed the parental lineage with Orf1a:P57L but i have closed the issue after it was designated first the child lineage >>> cov-lineages/pango-designation#932

EDITED**** i see now that there was a designation marathon and one of the newly designated is
" BF.20 Alias of B.1.1.529.5.2.1.20, lineage in Kenya and other countries "

wondering if it is defined by Orf6:p57L

@corneliusroemer
Copy link
Member

@FedeGueli let's find out ;) I'll create a new BA.2/4/5* Pango tree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nextclade_data Concerning dataset part: reference tree, qc definitions etc
Projects
None yet
Development

No branches or pull requests

2 participants