-
Notifications
You must be signed in to change notification settings - Fork 5
Carry aligned reads as CRAM, with --aligned_format cram|bam #207
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
base: dev
Are you sure you want to change the base?
Changes from all commits
83fff3e
5dff4f1
1569c5e
5481adb
77bcf54
28965de
51323c8
2cd3e56
f01a25b
ef82aa0
e2aca1b
f342092
d5b9d7b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No test exercises the duplicate-
RGfix. The CHANGELOG says-x RG"altersMINIMAP2_ALIGNin both formats". Yetdeep_only(--aligned_format bam) keeps everybamfiles/*.bammd5 byte-identical to dev (only the timestamp moved indeep_only.nf.test.snap). So the test uBAMs carry noRGaux tag, and this line is a no-op in the test suite. A regression here (e.g. asamtools resetversion without-x, or the uBAMRGcoming back through-T '*') would not be caught. Please consider a test uBAM with a basecallerRGtag, or an assertion that every aligned record'sRGmatches an@RGheader line.