Add cram support for RetroSeq #25
Open
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
…ts of bam indexes also crai indexes are checked for presents
…coys contigs. Now the start is at least 0
…mark with a small cram file a speedup of at least 2x in the discover phase. Bam files can still be used and do not benefit from this optimisation.
This is set to 1 version higher than actually needed since the CheckBinary function has issues to see that 1.15 Is higher than 1.9 (it does a string compare and not a numeric compare)
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 pull request enables RetroSeq to handle cram files. This is facilitated by using a modern version of samtools (newer than 1.10) and some changes in the code for checking files (e.g. also allow cram files when looking for cram.) Bam support is still supported.