Closed AngieHinrichs closed 3 years ago
Does B.1.623
need to be tracked as a VOC/VOI? The original concern was with the E484K - without that there is nothing to justify it being a VOC/VOI and thus perhaps remove the Scorpio definition file?
Actually it looks like the Scorpio file for 'B.1.623' makes no sense with respect to what has be designated. Either the Scorpio file needs to be updated to have the actual mutations or be removed and just let Pangolin assign it.
PHE was tracking B.1.623+E484K -- which, as far as I can tell, has been observed only once aside from the two British travelers (England/MILK-F9DBDB/2021|EPI_ISL_852237 and England/MILK-F9DB71/2021|EPI_ISL_852169) in the PHE report (where is it referred to as B.1.324.1). B.1.623 is a lot broader (UCSC proposed just B.1 + {S:S494P, S:N501Y, S:P681H, N:M234I}).
As @aretchless pointed out in cov-lineages/pangolin#305 the recent update to pangolin to override pangoLEARN/usher assignments with Scorpio caused most B.1.623 sequences to be assigned 'None' now.
I ran scorpio via pangolin on FASTA for the 739 representative sequences for B.1.623 in pango-designation/lineages.csv:
Only 2 of the 739 reps were classified as cB.1.623:
The other 737 sequences have too many reference alleles, implying that cB.1.623 is too specific to the virus sequences from those two travelers:
I suspect the alt_count should be higher than 2 or 3 for those as well (i.e. mutations could be added as well). I will make a pull request that brings cB.1.623.json more in line with my understanding of pango-designation's B.1.623.