Add CRAM to FASTQ WDL to resolve STAR alignment hang issues #111
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 PR adds a WDL workflow to convert CRAM files to gzipped FASTQs via aligned BAM and uBAM intermediates.
Purpose: This was built to resolve STAR alignment hangs caused by problematic reads near the end of FASTQ files during multithreaded runs. Re-generating FASTQs via Picard’s RevertSam and SamToFastq successfully resolved the issue across STAR versions v2.5.3a, v2.7.10a, and v2.7.11b.
Workflow Steps
Outputs
The wdl has been tested throughout the pipeline and mitigates STAR alignment failures caused by problematic reads accumulating at the end of FASTQ files during multithreaded alignment.