You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While investigating cov-lineages/pango-designation#590, I noticed that samples with the BA.2 S2M deletion (29734:29759) were being incorrectly visualized as having reference bases in sc2rf:
Consensus View:
sc2rf View:
I think this could be for a couple of reasons:
When --enable-deletions is used, perhaps deletions should not be considered missing data?
I think there is missing logic when detecting a run of Ns, to catch if that runs proceeds to the end of the genome?
ifsinmissings_matches:
# we've been tracking a run of N's, this base marks the end ifstart_n==-1:
start_n=i# mark the start of possible run of N'selifstart_n>=0:
missings.append((start_n, i-1)) # Python-style (closed, open) intervalstart_n=-1# Missing logic to catch missing data at the end of the genome?ifi==len(reference) andsinmissings_matches:
missings.append((start_n, i-1))
With these changes, the sc2rf output more closely matches the consensus sequence/my expectation:
I think this is a bug, but if it's the intended behaviour for deletions, please let me know. Thanks!
The text was updated successfully, but these errors were encountered:
While investigating cov-lineages/pango-designation#590, I noticed that samples with the BA.2 S2M deletion (29734:29759) were being incorrectly visualized as having reference bases in sc2rf:
Consensus View:
sc2rf View:
I think this could be for a couple of reasons:
When
--enable-deletions
is used, perhaps deletions should not be considered missing data?I think there is missing logic when detecting a run of Ns, to catch if that runs proceeds to the end of the genome?
With these changes, the sc2rf output more closely matches the consensus sequence/my expectation:
I think this is a bug, but if it's the intended behaviour for deletions, please let me know. Thanks!
The text was updated successfully, but these errors were encountered: