-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support optional .
and ?
in Mm tag
#1418
Comments
It appears I started work on this last year and managed to completely forget about it! (https://github.com/jkbonfield/htslib/tree/base_mod%2B is a WIP.) I'll resurrect it. The plan there was to extend the API to not only not choke on such data, but provide a way of programmatically distinguishing between explicit and implicitly specified base modifications. |
Not choking would be a good start 😄 I was wondering what a useful API should look like. The explicit In the case of the implicit |
Agreed. This should probably be broken into a trivial "make it work" PR and a more complex "make it useful" one. |
These define explicit vs implicit coordinates. They are now part of the MM specification, but we don't do anything with this data yet. This PR simply permits them to be parsed without choking, and ignores the additional markup. A subsequent PR will improve on this. Fixes samtools#1418
These define explicit vs implicit coordinates. They are now part of the MM specification, but we don't do anything with this data yet. This PR simply permits them to be parsed without choking, and ignores the additional markup. A subsequent PR will improve on this. Fixes samtools#1418
These define explicit vs implicit coordinates. They are now part of the MM specification, but we don't do anything with this data yet. This PR simply permits them to be parsed without choking, and ignores the additional markup. A subsequent PR will improve on this. Fixes samtools#1418
These define explicit vs implicit coordinates. They are now part of the MM specification, but we don't do anything with this data yet. This PR simply permits them to be parsed without choking, and ignores the additional markup. A subsequent PR will improve on this. Fixes #1418
Hello, |
That looks like an old issue. Upgrade and your problem should go away. |
@jkbonfield Thanks! I've updated samtools and now it seems to work |
@jts proposed changes to the Mm/Ml tag specification which allow to explicitely record what can be assumed about bases for which no entry in the tag is made. These changes are now in the SAMtags specification, but not supported by the tag parsing code in htslib.
A check needs to be performed around here:
htslib/sam.c
Line 6175 in 9bcb2d2
to see if a
.
or?
is present and (minimally) skip to the next character. Currently a file containing this optional information will cause the parser to trip up eventually emitting the error."Insufficient number of entries in ML tag"
The text was updated successfully, but these errors were encountered: