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

JN.1+S:F456L with C6968T branch (169 seqs) #2682

Closed
DailyCovidCases opened this issue Jul 2, 2024 · 5 comments
Closed

JN.1+S:F456L with C6968T branch (169 seqs) #2682

DailyCovidCases opened this issue Jul 2, 2024 · 5 comments

Comments

@DailyCovidCases
Copy link

From branch 79 of sars-cov-2-variants/lineage-proposals#1253
JN.1+C6968T+S:F456L
Query: C6968T, T22928C, C18894T
No. of seqs: 30 (Canada 1 China 3 France 1 Singapore 3 South Korea 2 Spain 2 Sweden 1 UK 10 USA 7)
First: EPI_ISL_19051595, 2024-3-23
Latest: PP934275.1, 2024-6-10
usher
Screenshot (131)

@FedeGueli
Copy link
Contributor

thanks for proposing but i suggest to close this down , the query catches multiple lineages
Screenshot 2024-07-02 alle 18 50 49
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_test_462b3_42fab0.json?f_userOrOld=uploaded%20sample&label=id:node_6939135
the one proposed here seems very small:
Screenshot 2024-07-02 alle 18 51 19

When a multiple lineages issue is open it is like a notebook where initial queries are annotated, sometimes they are very good , while more usually they then have to be updated to exclude convergent lineages, so when you go to propose a lineage and you see that the sequences are widespread in the tree better stopping and highlighiting that in the comments before proposing it. thank you for your work anyway

@xz-keg
Copy link
Contributor

xz-keg commented Jul 2, 2024

When a multiple lineages issue is open it is like a notebook where initial queries are annotated, sometimes they are very good , while more usually they then have to be updated to exclude convergent lineages, so when you go to propose a lineage and you see that the sequences are widespread in the tree better stopping and highlighiting that in the comments before proposing it. thank you for your work anyway

Yeah. But it is quite shocking that C6968T is so convergent as a synonym mutation.

@FedeGueli
Copy link
Contributor

When a multiple lineages issue is open it is like a notebook where initial queries are annotated, sometimes they are very good , while more usually they then have to be updated to exclude convergent lineages, so when you go to propose a lineage and you see that the sequences are widespread in the tree better stopping and highlighiting that in the comments before proposing it. thank you for your work anyway

Yeah. But it is quite shocking that C6968T is so convergent as a synonym mutation.

agree

@DailyCovidCases DailyCovidCases changed the title JN.1+S:F456L with C6968T branch (30 seqs, 9 countries) JN.1+S:F456L with C6968T branch (38 seqs, 10 countries) Jul 6, 2024
@DailyCovidCases DailyCovidCases changed the title JN.1+S:F456L with C6968T branch (38 seqs, 10 countries) JN.1+S:F456L with C6968T branch (67 seqs, 12 countries) Jul 17, 2024
@DailyCovidCases
Copy link
Author

Tracked in tracker79

@DailyCovidCases DailyCovidCases changed the title JN.1+S:F456L with C6968T branch (67 seqs, 12 countries) JN.1+S:F456L with C6968T branch (45 seqs) Jul 18, 2024
@DailyCovidCases DailyCovidCases changed the title JN.1+S:F456L with C6968T branch (45 seqs) JN.1+S:F456L with C6968T branch (67 seqs) Jul 18, 2024
@DailyCovidCases DailyCovidCases closed this as not planned Won't fix, can't repro, duplicate, stale Jul 18, 2024
@DailyCovidCases DailyCovidCases changed the title JN.1+S:F456L with C6968T branch (67 seqs) JN.1+S:F456L with C6968T branch (169 seqs) Aug 29, 2024
@FedeGueli
Copy link
Contributor

C6968T, T22928C, C18894T

did you update the query? @DailyCovidCases if not it is not monophyletic as highlighted in a comment above. please check

@DailyCovidCases DailyCovidCases closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants