-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implement cram chunking and minimap2-based Hi-C alignments #113
Conversation
Cram handling
Cram handling
@tkchafin : if you want to test the feature, try Myxine_glutinosa from TOLSD-2062. We just finished running it with the version 1.2.1 of the pipeline. The resulting CRAM file is 178 GB 🙀 and contains 6.5 billion reads. bwa-mem2 took more than 7 days to run, as a single process on 64 cores and 174 GB RAM. |
Cram handling
Sent PR reichan1998#2 covering the Illumina case. I think interleaved fastq should be handled correctly there but would be worth a double-check! :) |
Cram handling illumina
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.
We also need to update the copyright and make sure the documentation is clear on interleaved fastq inputs but will send as a separate PR.
Also need to update CI to run both bwamem and minimap2 tests
hic_bwamem2
andhic_minimap2
fromsanger-tol/treeval
to chunk HiC CRAM file into containers and align based on read groups.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).