Resolve "Chunk bam for parallel tin calculation"
Please fill in the appropriate checklist below (delete those which are not relevant). These are the most common things requested on pull requests.
PR checklist
-
This comment contains a description of changes (with reason) -
If you've fixed a bug or added code that should be tested, add tests! -
Documentation in docsis updated -
Replace dag.png with the most recent CI pipleine integrated_pe artifact -
CHANGELOG.mdis updated -
README.mdis updated -
LICENSE.mdis updated with new contributors
-
Close issue
Closes #45 (closed)
Chunked the BAM file for faster TIN calculation. Chunking takes place in the dedup phase, and all chunks are concatenated together at the end of inferMetadata. Note: this does remove all non-canonical contigs from the calculations, however, after several tests, it appears this was occurring anyway, as tin.py does not calculate anything no present in the BED file.
Merge request reports
Activity
changed milestone to %v0.0.1
added discussion enhancement suggestion ~311 labels
Resolved by Gervaise Henryadded 1 commit
- 4346896f - Changed infer.tsv back to infer.csv with appropriate formatting changes.
added 27 commits
-
563eabd7...7e0d0e5d - 26 commits from branch
develop - ca9e0973 - Merge branch 'develop' into '45-parallelizeTin'
-
563eabd7...7e0d0e5d - 26 commits from branch
enabled an automatic merge when the pipeline for ca9e0973 succeeds
enabled an automatic merge when the pipeline for ab85953a succeeds
added 1 commit
- 9485d137 - Change all multithreading to 6 in unit tests so Daniel doesn't yell at me
added 1 commit
- f64f7ac6 - Replace tower, remove repRID input in parseMetadata
added 1 commit
- 683961cf - Move nextflow module load to integration script
added 1 commit
- f264782a - Revert module location and downgrade to nextflow 0.31.0
added 1 commit
- 13c6a20f - Make test.nf compatible with nextflow 0.31.0
added 1 commit
- 831cadd1 - Try to make test.nf more compatible with 0.31.0