Correct rendered range of symbolic VCF alleles #1580
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrobinso
requested review from
lbergelson
and removed request for
lbergelson
|
I'm sure this is correct but I'll ask @lbergelson to look, if for no other reason so he is aware. |
|
Thanks @jrobinso, the more eyes on the better. |
lbergelson
reviewed
Sep 25, 2024
Co-authored-by: Louis Bergelson <[email protected]>
Update comment to include non-ref symbolic allele exception in VCF 4.4+
lbergelson
approved these changes
Sep 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch adjusts the start position of symbolic VCF alleles to better match the VCF spec definition:
https://github.com/samtools/hts-specs/blob/4cde0e235b4e4cfbd67a0c3a38abea611d56d256/VCFv4.1.tex#L165
Motivated by discussion on samtools/hts-specs#792 -- cc: @jrobinso / @d-cameron