-
Notifications
You must be signed in to change notification settings - Fork 3
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
JG.4/DV.7.1 recombinant(4 seqs) and XCT: its further recombinant with XBB.1.9.2 #811
Comments
Added to list, should be added when 2023-09-14 build is done, thanks. |
There is a second seq near this . EPI_ISL_18284092 It is a sandwich recombinant of EG.5.1--DV.7.1--EG.5.1, also being removed by usher. |
Thanks @aviczhl2, I added EPI_ISL_18284092 to the list so it should be added in the 2023-09-28 build, sorry about the delay. EPI_ISL_18254485 is being added to the tree daily, but then removed by our filter of max 20 private mutations on a singleton sequence. When EPI_ISL_18284092 is added, then EPI_ISL_18254485 will no longer be a singleton with all those mutations and the two sequences should be retained in the 2023-09-28 tree. |
@AngieHinrichs A 3rd one appears, EPI_ISL_18316684, seems to be the same sandwich recomb of EPI_ISL_18284092. |
OK, added, should be in the 2023-09-29 build. |
@AngieHinrichs There's one more from Switzerland. EPI_ISL_18327700 |
@FedeGueli @ryhisner @NkRMnZr @krosa1910 @HynnSpylor please help me on this. Seems extremely complex. |
For sure inwill look at it tomorrow |
Added, thanks. |
It is looks like a XCM-alike sandwich recombinant between EG.5.1.3/DV.7.1 ( and the french sample could be a further recombination or a recombinant itself parent of this recombinant) to me it could be (please check): from DV.7.1: A19886G,A20741G,T22016C,C22033A,A22115G,A22190G,T22200G,G22331A,A22893C,T22917G,G22927T,T22928C,C24134A,T24991A,G25606A,C25721T,T25959C Private mutations: So it would be 1-18429 EG.5.13 |
Thanks for the analysis. As said this is a complex recomb so there're some problems need fixing. How about 29625 missing? This one doesn't have C29625T however EG.5.1.3 has. Also that DV.7.1 branch of C20320T has additional C27849A which is not present in the French seq (where 19886-3' are all DV.7.1) |
yeah it could be also this one as donor: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_3e515_96edd0.json?c=userOrOld&label=id:node_10941447 (link edited) |
But it also doesn't have 28695? |
Yeah about the orf10 mutation likely the donor was already itself a recombinant within XBB.1.9 family. |
it is dv.7.1 : i mean DV.7.1 side donor |
So concluding: |
XCT |
Designated XCT |
It seems that currently the parental recomb (without G8*, C27507A and T28297C) is designated as XCT? |
only that one? does the designation misses the real XCT? in the other case it catches all i would not make a difference cc @corneliusroemer what do you think? |
I'm not sure, but the 2 recombs shall not be under one name. Either give both a designation, this may create a recomb with only 2 seqs but helpful for explanation. Or remove seqs of the parental recomb from XCT and to clarify the children recomb is XCT. |
@AngieHinrichs new XCT(children recomb) seqs, EPI_ISL_18395595, EPI_ISL_18392290, EPI_ISL_18391834, EPI_ISL_18381777,EPI_ISL_18391799 |
@AngieHinrichs 7 more today, all children recomb EPI_ISL_18403312, EPI_ISL_18403342, EPI_ISL_18403373-18403374, |
2 more from NSW. EPI_ISL_18411444 and EPI_ISL_18411775 |
Thanks @aviczhl2 and @JosetteSchoenma, I added those IDs to my file. In the future would it be too much trouble for you to add sequences to https://github.com/sars-cov-2-variants/lineage-proposals/blob/main/recombinants.tsv ? |
That's for undesignated lineages. Will it cause conflict for designated lineages as they may also appear elsewhere with different labels? recombinants.tsv also has a function for manual search of currently proposed recombs I think it shouldn't be too big (keep it <1000 What's your suggestion? |
OK, I misunderstood the purpose of recombinants.tsv, thanks for clarifying that. Perhaps there could be a separate file just for IDs of sequences that should be exempted from the too-many-reversions filter? Like #991, but just a file of IDs. |
Maybe I shall create one to include those seqs as well as XCT before they are not removed by usher. BTW: Is XCM still being filtered out? When can usher automatically recognize a lineage and stop removing its seqs? |
That would be extremely helpful!
Most XCM should not be filtered out as far as I can tell. The 2023-10-23 tree has 72 sequences placed in XCM even though my local file that exempts sequences from too-many-reversion filtering has only 7 IDs (none in recombinants.tsv). They are right on the edge of filtering, with 5 reversions relative to placement in the nextclade tree version 2023-09-21T12:00:00Z. Any sequence with one or more extra reversions could be filtered.
When these things happen:
|
By nextclade data release, do you mean https://nextstrain.org/staging/nextclade/sars-cov-2 ? I see XCT is already there? |
I believe https://nextstrain.org/staging/nextclade/sars-cov-2 is Cornelius's nightly build -- it's pre-release. By release I mean official releases like https://github.com/nextstrain/nextclade_data/releases/ . When there is a new release, I can download the new release data files and then re-run nextclade on all sequences. My nightly build runs the latest downloaded release on all new sequences, which doesn't take much time -- but re-running nextclade every night on all pre-existing sequences would take a lot more time. |
I see. So whatsoever designated lineages will be included eventually when nextclade performs a formal release every month? |
Yes. |
1 more for the parental recomb. EPI_ISL_18494770 |
1 more for the parental recomb EPI_ISL_18518466 |
I find a EG.5.1.3/DV.7.1 recombinant that usher registers with too many reversions and may be dropped out.
EG.5.1.3--DV.7.1
Breakpoint: Between 18584 and 19325
Extra mutations: C1684T,C7051T,C20320T,T24073C
Orf1b:H2285Y
https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?nucMutations=C24134A%2CC7051T%2CC1889T&nextcladePangoLineage1=EG.5.1.3*&nextcladePangoLineage2=DV.7.1*&analysisMode=CompareEquals&
C1684T,C7051T from an EG.5.1.3-branch.
C20320T,T24073C are private
Some DV.7.1 branches have C20320T however they have additional mutations after that so not possible.
Query: C24134A,C7051T,C1889T
The branch include 2 recombs:
(this one with additional C29546T, private, no DV.7.1 has this)
EG.5.1.3--DV.7.1
For EPI_ISL_18254485(France), C24134A,C7051T,C1889T,C29546T
(this one with additional A27507C, T28297C, G27915T(Orf9b:I5T, Orf8:G8*), indicating 2nd breakpoint between 26276 and 27506
EG.5.1.3--DV.7.1--XBB.1.9.2? (Not EG.5.1.3 for not having C29625T)
3-seq branch: C24134A,C7051T,C1889T,A27507C (USA, Switzerland)
So EG.5.1.3 recombs with DV.7.1 and get recomb 1, while recomb 1 recombs with another XBB.1.9.2 and gets recomb 2?
If that's 1 seq I'll view it as artefact, however now we have 4 seqs from 3 countries.
EG.5.1.3-side donor:
Current usher
usher
The text was updated successfully, but these errors were encountered: