Documentation error in RNAseq workflow

Wed 11 Jun 2014

We discovered today that we made an error in the documentation article that describes the RNAseq Best Practices workflow. The error is not critical but is likely to cause an increased rate of False Positive calls in your dataset.

The error was made in the description of the "Split & Trim" pre-processing step. We originally wrote that you need to reassign mapping qualities to 60 using the ReassignMappingQuality read filter. However, this causes all MAPQs in the file to be reassigned to 60, whereas what you want to do is reassign MAPQs only for good alignments which STAR identifies with MAPQ 255. This is done with a different read filter, called ReassignOneMappingQuality. The correct command is therefore:

java -jar GenomeAnalysisTK.jar -T SplitNCigarReads -R ref.fasta -I dedupped.bam -o split.bam -rf ReassignOneMappingQuality -RMQF 255 -RMQT 60 -U ALLOW_N_CIGAR_READS


In our hands we see a bump in the rate of FP calls from 4% to 8% when the wrong filter is used. We don't see any significant amount of false negatives (lost true positives) with the bad command, although we do see a few more true positives show up in the results of the bad command. So basically the effect is to excessively increase sensitivity, at the expense of specificity, because poorly mapped reads are taken into account with a "good" mapping quality, where they would normally be discarded.

This effect will be stronger in datasets with lower overall quality, so your results may vary. Let us know if you observe any really dramatic effects, but we don't expect that to happen.

To be clear, we do recommend re-processing your data if you can, but if that is not an option, keep in mind how this affects the rate of false positive discovery in your data.

We apologize for this error (which has now been corrected in the documentation) and for the inconvenience it may cause you.

sirian

Thanks for the correction! I was actually wondering a little bit why you changed every score.

sboyle

Thanks for the correction Geraldine!

GATK Dev Team

@gatk_dev

RT @erlichya: LOL! "Lior's blog is known for its specificity but less for its sensitivity" - @GenomeNathan intro to @lpachter seminar at @n…
27 Aug 15
RT @thatdnaguy: **VERY IMP. #GATK BUG WARNING** Do not run GenotypeGVCFs on gzipped and tabix indexed files. Increased runtime ** ~70X ** …
27 Aug 15
@pjacock @lexnederbragt @illumina @BroadGenomics pipeline converts basecalls direct to unmapped SAM w/ Picard https://t.co/Fz9vRKA7UR
19 Aug 15
Q: How similar is an unmapped BAM (uBAM) to a BAM? A: Close, but no CIGAR.
19 Aug 15
Looking for a Data Scientist and/or Computational Biologist to join the #GATK methods development team https://t.co/2XXhWudra8