Fix end position for SV insertion types #1776
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#1432
Currently for SV insertions, the end is calculated like so -
But it is probably more appropriate to say -
Because that is the anchoring bases in reference sequence the sequence is inserted. The current implementation adding the SVLEN/END implied a wider length of reference sequence getting affected which is actually not the case.
PS: it will change the consequence, for example the test variant -
1 146985757 . G <INS> . . SVTYPE=INS;SVLEN=17243
previously,
With this fix -