Closed corneliusroemer closed 5 months ago
This is up to 77 sequences and has been found in 5 different US states and 5 different Canadian provinces. The Usher tree is a total mess though. They're scattered all over the place.
I think the insertion really is ins214YRR, by the way. The only reason Nextclade puts an E in there is because of the V213E mutation, which it interprets as being new.
and pls pay attention to this: https://cov-spectrum.org/explore/World/AllSamples/Past3M/variants?nextcladePangoLineage=JN.1*&aaInsertions1=ins_S%3A212%3AERY&analysisMode=CompareToBaseline& Ok biased by Canada and Minnesota high sequencing intensity but still..
132 now , fast maybe due to canadian targeted sequencing: https://cov-spectrum.org/explore/World/AllSamples/Past3M/variants?nextcladePangoLineage=JN.1*&aaInsertions1=ins_S%3A212%3AERY&analysisMode=CompareToBaseline&
156 @corneliusroemer this should be designated
Four sequences from Manitoba, Canada, from this lineage with S:H52Y were uploaded today but with collection dates from late November. Usher apparently masks this mutation, so it doesn't show up on the tree. EPI_ISL_18822538, EPI_ISL_18822547-18822548, EPI_ISL_18822559
181 now
201 now
This seems to still be growing in Canada, despite JN.1 being over 90%. 250 now while searching GISAID with ins22204TACAGGAGG. 246 with ins214YRR. CoVSpectrum screenshot from JG.3.2* (Nextclade), S:V213R
This seems to still be growing in Canada, despite JN.1 being over 90%. 250 now while searching GISAID with ins22204TACAGGAGG. 246 with ins214YRR.
Thx @JosetteSchoenma i m tracking since the start, unfortunately the insertion has no nucleotide associated with it , so pretty hard to designate. @corneliusroemer what could we do?
@corneliusroemer @JosetteSchoenma noticed that both CovSpectrum and Nextclade read the insertion as S:V213R could be this. a way to designate it?
254
261 now.
@AngieHinrichs It seems that a lot seqs of this branch are not even categorized to JG.3.2 in usher despite all have S:N450D. There seems some bug in usher here.
Is it an UShER bug, or is it that sequences from Canada (and some from the US) tend to have A22910G along with so many other mutations that are shared with sequences from other countries that don't seem to have A22910G? I will try the usual prune/re-optimize/re-place, but the large number of cases in which especially Canada seems to gain A22910G with many other different shared mutations makes me wonder if it could be an artifact, or if other countries tend to miss 22910. I don't have time to look at alignments right now.
Is it an UShER bug, or is it that sequences from Canada (and some from the US) tend to have A22910G along with so many other mutations that are shared with sequences from other countries that don't seem to have A22910G? I will try the usual prune/re-optimize/re-place, but the large number of cases in which especially Canada seems to gain A22910G with many other different shared mutations makes me wonder if it could be an artifact, or if other countries tend to miss 22910. I don't have time to look at alignments right now.
They have to be after the A22910G because they also have the S:ins213RYR thing described in this repo.(not shown in usher)
An S:A475V sub-branch of this appears. #1465.
298 now
No new seqs
Dying or dead
There's a JG.3.2 sublineage in Canada that is defined by a Spike insertion S:212insERY only - there's no defining SNP compared to JG.3.2 unfortunately.
GISAID query:
ins214YRR
It seems to be not doing too badly as it has popped up in multiple states in Canada. The location is one that's known for insertions, so not surprising.
There's nothing we can do here in terms of designation - all we can do is hope that there will be one SNP that has encompasses most of this lineage and designate that were we to designate.
It's also been sequenced in the US twice
Covspectrum: ins_S:212:ERY (Edited)