Recommend 1bp SEQ with QUAL="*" as quality-unavailable. #752
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.
The change is simply a footnote indicating the presence of the ambiguity and a mild recommendation, however it's not likely to make any practical difference in real-world data where even if 1bp reads exist their quality values aren't likely to be a deciding factor over their validity.
Also in attempting to build the SAM spec my latex blew up. This turns out to be due to #670 which added use of
\>
for non-breaking space. Our systems here are pretty old, and latex couldn't cope with that. However in the interests of keeping the spec as easy to build as possible, I did a trivial replacement in its own commit.