Fix read vs ref not finding primary alignment on certain CRAM files #2952
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.
Currently, there is a routine to get the primary read if you start with a supplementary read for linear ReadVsRef visualization. It requests reads overlapping a single base pair where the start of the primary read is. One issue though is there is likely an off-by-one error in specifically CRAM feature fetching where if I request reads overlapping ctgA:0-1, it does not return anything. Making it request ctgA:0-2 is a workaround, but fixing the off by one would be worthwhile
Also, fixes error handling on the read vs ref dialog (previously, the error wasn't displayed)