No more header requried for ribosomal interval files in CollectRnaSeqMetrics #1965
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.
With this pull request, CollectRnaSeqMetrics can new be used with ribosomal interval list file without a SAM header. In this case, CollectRnaSeqMetrics will use the header of the BAM input file.
Description
Creating a valid ribosomal interval list for CollectRnaSeqMetrics is a tedious task as the @sq tags of SAM header of this file must be rigorously the same as in the BAM header of the input file (e.g., the exact order of the chromosomes/sequences must be the same; the length of the chromosomes/sequences must be same).
With the patch in this pull request, CollectRnaSeqMetrics will have the same behavior if a header exists in the ribosomal interval list file. If no header is found in the file, the patch will use the header of the input BAM.
This new behavior will streamline the creation of ribosomal interval list files, as it can be creating with just a GTF file without the need to add the sequence lengths at the beginning from the genome FASTA, GFF3 or input BAM header.
Checklist (never delete this)
Never delete this, it is our record that procedure was followed. If you find that for whatever reason one of the checklist points doesn't apply to your PR, you can leave it unchecked but please add an explanation below.
Content
Review
For more detailed guidelines, see https://github.com/broadinstitute/picard/wiki/Guidelines-for-pull-requests