-
Notifications
You must be signed in to change notification settings - Fork 98
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
Proposal to split B.1.640 into two sublineages #362
Comments
Another cluster of sequences from the minor sublineage uploaded from the Provence-Alpes-Cote d Azur region by Colson et al: |
Two more sequence from the minor group are coming by Colson et al. If this help : Commun mutations with Major Group : Specific to the minor clade : |
Thanks @thomasppeacock Agree this split sounds sensible and we've added lineages B.1.640.1 ("Major group" above) and B.1.640.2 ("Minor group" above) in v1.2.108. With this update, there aren't currently any sequences designated to the parental B.1.640 lineage |
We indeed have several cases of this new variant in the Marseille geographical area. We named it "Variant IHU". Two new genomes have jsut been submitted. |
Hello - Just checking - should it be expected that pangolin now calls B.1.640.1 and B.1.640.2? I don't see any of these in GISAID (just B.1.640) and downloading them all and running an up to date version of pangolin and submodules calls them all B.1.640? |
Hi @mattdmem I don't think they're in the current pangolin yet as the latest pangoLEARN was trained on v1.2.106 and B.1.640.1 and B.1.640.2 weren't added until v1.2.108. There's likely to be a new pangoLEARN run very soon that will have these in |
Just a small update here - @c19850727 just pointed out to me a further outlier sequence (EPI_ISL_8428057 uploaded by Coppens et al from Belgium). This sequence is really interesting as it contains both unique mutations and elements of both B.1.640.1 and B.1.640.2 (in a similar manner to the relationship between BA.3 to BA.1/2). Only a single sequence at the moment but worth being aware of. Spike: P9L, T95I, E96Q, Δ136-144, R190S,I210T(.1-like), R346S, N394S, Y449N,E484K (.2-like), F490S (.2-like), Q498R, N501Y, D614G, P681H, T859N, D936H (.1-like), D1139H (.2-like), L1200F |
EPI_ISL_8525350 found another one from Belgium. |
In a similar vein to the recent split of B.1.1.529(Omicron) into two sister sublineages it appears B.1.640 may also have a similar issue with a major group constating of the vast majority of sequences and a small outgroup which appears related but has a very different set of mutations (EPI_ISL_7181977; EPI_ISL_7156959; EPI_ISL_7156955; EPI_ISL_6315910; EPI_ISL_5926666) and includes sequences from France and England, indicating some degree of spread.
Defining mutations (mutations not shared between both groups shown in bold):
Major lineage:
Spike - P9L, E96Q, Δ136-144, R190S*, I210T, R346S, N394S, Y449N, F490R, N501Y, D614G, P681H, T859N, D936H
Non-spike - NSP2 – P129L, E272G; NSP3 – L1301F, A1537S; NSP4 – S386F, R401H, T492I; NSP6 – V149A; NSP12 – P323L; T32I, Q57H; M – I82T; ORF8 – Q27*STOP; N- D22Y, T205I, E378Q; S2m deletion
Minor lineage:
Spike - P9L, E96Q, Δ136-144, R190S, D215H, R346S, N394S, Y449N, E484K, F490S, N501Y, D614G, P681H, T859N, D1139H
Non-spike - NSP2 – P129L; NSP4 – D459N; NSP6 – Δ106-108, T181I; NSP12 – P323L; NSP13 – V371A; NSP14 – P46S, V437F; ORF3a – T32I, Q57H; M – I82S; ORF8 – Q27*STOP; N – D22Y, T205I
Phylogenetic evidence:
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_58c3_f65be0.json?c=pango_lineage&label=nuc%20mutations:C10029T,G23012A,A23063T,C23604A,A26492T,C27925A,C28005T,C28093T,C28887T
Proposed name(s): B.1.640.1 and B.1.640.2?
The text was updated successfully, but these errors were encountered: