Documentation error in RNAseq workflow

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.

Wed 11 Jun 2014

sboyle


Thanks for the correction Geraldine!

Wed 11 Jun 2014



Search blog by tag

2013 ad agbt14 appistry baserecalibrator belgium best-practices beta blog bqsr broken-links brussels bug bug-fixed cancer catvariants challenge combinegvcfs combinevariants commercial community compbio competition conferences depthofcoverage diagnosetargets documentation downtime error fastaalternatereferencemaker forum gatk gatk-3-0 gatk-3-1 gatk-3-2 gatk-lite gatk2 gatk3 genotypegvcfs gsa gsa-announce gvcf haploid haplotypecaller hardware holiday indelrealigner intel job job-offer jobs joint-analysis joint-discovery key license lite media meetings multisample multithreading mutect nt optimization pairhmm paper performance phone-home pipeline ploidy polyploid poster presentations press printreads queue randomlysplitvariants readbackedphasing reducereads reference-model release release-notes rnaseq scatter-gather selectvariants slides spam splitncigarreads support talks topstory trivia tutorials unifiedgenotyper userstories validatevariants variantannotator varianteval variantrecalibrator variantstobinaryped version-highlights video videos webinar workshop


GATK Dev Team

@gatk_dev

RT @JohnMHancock: @ Genome Science 2014 today and tomorrow
1 Sep 14
RT @KAngevi: Curious about how much faster GATK 3 is vs. GATK 2?? Check out my blog entry! http://t.co/cmUvJtcNk4 #Appistry
28 Aug 14
We're hiring! Looking for a developer to join us on a part-time basis to fix bugs. Remote OK but USA only. http://t.co/FILZWg07wx
28 Aug 14
Upcoming #GATK workshop at UPenn in Philadelphia, September 18-19, details at http://t.co/6mWQ4kbWct
28 Aug 14
We have a new favorite for best "meaning of SNP" answer: Still No Paper ! http://t.co/tuw7nOQIdt
27 Aug 14