Are indel realignment and base recalibration necessary for RNAseq data?
2
3
Entering edit mode
8.1 years ago
Bnf83 ▴ 150

Hi guys,

I'm performing the RNA sequencing analysis of a set of human samples. Since I'm a newbie of this type of analysis, I followed some published pipelines. Specifically, the pipeline is this one: http://gatkforums.broadinstitute.org/gatk/discussion/3060/how-should-i-pre-process-data-from-multiplexed-sequencing-and-multi-library-designs. Since I only need to measure the gene expression, I don't know if the indel realignment and base recalibration (BQSR) are two necessary steps for my goal. Can you help me to solve my doubts?

Kind regards
B

GATK RNA-Seq gene-expression • 2.9k views
ADD COMMENT
0
Entering edit mode

That is a very good point. If you have time, call mutations for one sample before (i.e. indel realignment and BQSR) and after, and compare the INDELs you are getting.

ADD REPLY
3
Entering edit mode
8.1 years ago

Those best-practice guidelines are for variant calling, not gene expression. BSQR would be useless, and indel realignment might even cause problems for alternatively spliced transcripts b/c it's designed to resolve alignment discrepancies at indel loci.

ADD COMMENT
1
Entering edit mode
8.1 years ago
John 13k

The GATK pipeline for RNA turns reads that are split over an intron into two (or more) individual reads. This is done specifically so you can run BQSR and IndelRealigner on RNA-Seq data. However, as Harold points out, this is far from an established protocol. It could, depending on the data, do more harm than good. As H.Hasani mentions, the only real way to know for sure is try both and find out. I know thats kind of easier-said-than-done... but you're doing cutting-edge research here, so it is unlikely things will go as smoothly as we'd all like. Good luck :)

ADD COMMENT

Login before adding your answer.

Traffic: 2368 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6