Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • metheuse
    Member
    • Jan 2013
    • 84

    Questions in calling SNPs from RNA-seq reads

    I'm trying to call SNPs from RNA-seq data.
    The workflow I'm trying to follow is: tophat2 --> remove duplicates --> local realignment and base quality recalibration by GATK --> call SNPs by samtools mpileup or GATK

    These are some specific questions:

    1. Should I filter the alignment from tophat2 to get only the uniquely mapped reads (reads that could only be mapped to single location on the genome)? If yes, how should I filter them?
    I know there is a --multihits (-g) parameter in tophat that can be set to 1 to report only one hit per mapped read. But this is not the strict definition of "unique mapping". I saw people saying that in the alignment sam file, if MAPQ=50, that means this read can only be mapped to a single position. Could I, for example, run tophat2 with g=20 (default), and then select only the aligned reads with MAPQ=50?

    2. GATK cannot accept N in cigar. How should I deal with the aligned reads with N in the cigar? GATK has two options: the first is to remove these reads; the second is to allow N in cigar. The former strategy may lose a lot of information, while the latter is at risk (I don't know what the risk is exactly).

    3. To use samtools mpileup, how should I set the -C (parameter for adjusting mapQ) parameter? I know it recommends 50 for bwa aligned reads, but what it is for tophat2 alignment?

    4. If you have experience in this kind of data analysis, can you see any other potential problems in the pipeline or the parameters of each program? Do you have any recommendation?

    By the way, I know there are a lot of caveats of using RNA-seq data to call SNPs. The major purpose of this project is to measure expression, but calling SNPs is to try to get more use of the data (or the money).

    Thanks a lot for any suggestions or advice!
  • bruce01
    Senior Member
    • Mar 2011
    • 160

    #2
    I've done this a few times (call variants in RNAseq). From my experience it was 'easiest' to follow the GATK Best Practices (http://www.broadinstitute.org/gatk/guide/best-practices). I say 'easiest' because GATK is a bit of a hassle to run (the first time, anyway, second time was ok=).

    So I aligned with BWA (Tophat gives potential splice junctions; if you think they may be holding many important variants continue with Tophat, but the majority of SNPs in exon of interest (stops, non-synonymous) will not be in that region I think... and if they are you may be better trying the splice variant/differential splicing analysis...). I used UnifiedGenotyper and HaplotypeCaller to get my VCFs. I tried mpileup before, it was fine but everyone kept saying 'GATK is the gold standard' so I used it in the end: peer (review) pressure=D

    So I recommend: BWA, remove duplicates (Picard), realign, recalibrate, call variants, <other>.

    Hope that is of some help.

    Comment

    • metheuse
      Member
      • Jan 2013
      • 84

      #3
      Originally posted by bruce01 View Post
      I've done this a few times (call variants in RNAseq). From my experience it was 'easiest' to follow the GATK Best Practices (http://www.broadinstitute.org/gatk/guide/best-practices). I say 'easiest' because GATK is a bit of a hassle to run (the first time, anyway, second time was ok=).

      So I aligned with BWA (Tophat gives potential splice junctions; if you think they may be holding many important variants continue with Tophat, but the majority of SNPs in exon of interest (stops, non-synonymous) will not be in that region I think... and if they are you may be better trying the splice variant/differential splicing analysis...). I used UnifiedGenotyper and HaplotypeCaller to get my VCFs. I tried mpileup before, it was fine but everyone kept saying 'GATK is the gold standard' so I used it in the end: peer (review) pressure=D

      So I recommend: BWA, remove duplicates (Picard), realign, recalibrate, call variants, <other>.

      Hope that is of some help.
      Thanks for your information! It's helpful.

      Comment

      • bruce01
        Senior Member
        • Mar 2011
        • 160

        #4
        Hopefully it is helpful, if you have ideas on how to use the variant data specifically in terms of DE genes or otherwise maybe post back?! Also have a look at SNPdat to annotate your VCF, works very well for me.

        Comment

        • metheuse
          Member
          • Jan 2013
          • 84

          #5
          Originally posted by bruce01 View Post
          Hopefully it is helpful, if you have ideas on how to use the variant data specifically in terms of DE genes or otherwise maybe post back?! Also have a look at SNPdat to annotate your VCF, works very well for me.
          Thanks, I'll take a look at SNPdat. We usually use SnipEff to annotate VCF.

          Comment

          • FrankiB
            Member
            • Dec 2013
            • 23

            #6
            What are the specific settings (options, parameters) to use when mapping RNA seq data on human genome using BWA software?

            Comment

            • bruce01
              Senior Member
              • Mar 2011
              • 160

              #7
              To quote Homer: "the two greatest words in the English language: de-fault!"

              That is, I use default settings. Also depends on your data, as per: http://bio-bwa.sourceforge.net/bwa.shtml

              Comment

              • FrankiB
                Member
                • Dec 2013
                • 23

                #8
                OK thanks.

                But first I have to create the index. I'm using the human_g1k_v37 version. It has been 2 hours now that I've send the command and I have still this line:

                [bwa_index] Pack FASTA...

                Is everything okay?

                Comment

                • bruce01
                  Senior Member
                  • Mar 2011
                  • 160

                  #9
                  Hi FrankiB, yes I would say everything is ok. As a general rule if there is no error given, and the rest of your computer is working ok, then you just need to wait for things to build. Have a look at 'screen' and 'top' if you don't know them, nice way to make sure your command is actually doing something!

                  Comment

                  • amodupe
                    Junior Member
                    • Apr 2012
                    • 1

                    #10
                    Originally posted by bruce01 View Post
                    I've done this a few times (call variants in RNAseq). From my experience it was 'easiest' to follow the GATK Best Practices (http://www.broadinstitute.org/gatk/guide/best-practices). I say 'easiest' because GATK is a bit of a hassle to run (the first time, anyway, second time was ok=).

                    So I aligned with BWA (Tophat gives potential splice junctions; if you think they may be holding many important variants continue with Tophat, but the majority of SNPs in exon of interest (stops, non-synonymous) will not be in that region I think... and if they are you may be better trying the splice variant/differential splicing analysis...). I used UnifiedGenotyper and HaplotypeCaller to get my VCFs. I tried mpileup before, it was fine but everyone kept saying 'GATK is the gold standard' so I used it in the end: peer (review) pressure=D

                    So I recommend: BWA, remove duplicates (Picard), realign, recalibrate, call variants, <other>.

                    Hope that is of some help.
                    Hi bruce01, what did you use for your VCFs, UnifiedGenotyper or HaplotypeCaller? or did you use both?

                    Comment

                    • bruce01
                      Senior Member
                      • Mar 2011
                      • 160

                      #11
                      I use(d) HaplotypeCaller which is now recommended by GATK support as the one to use in all circumstances.

                      Comment

                      • exome
                        Junior Member
                        • Mar 2016
                        • 1

                        #12
                        Detecting mutations from RNA-Seq is not a typical approach to detect mutations, mainly due to the intrinsic complexity in the transcriptome (e.g., splicing, high/low gene expression level).

                        Comment

                        Latest Articles

                        Collapse

                        • SEQadmin2
                          Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
                          by SEQadmin2



                          Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
                          ...
                          Yesterday, 11:10 AM
                        • SEQadmin2
                          Cancer Drug Resistance: The Lingering Barrier to Rising Survival
                          by SEQadmin2



                          Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

                          There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
                          07-08-2026, 05:17 AM
                        • GATTACAT
                          Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
                          by GATTACAT
                          Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
                          07-01-2026, 11:43 AM

                        ad_right_rmr

                        Collapse

                        News

                        Collapse

                        Topics Statistics Last Post
                        Started by SEQadmin2, Yesterday, 10:04 AM
                        0 responses
                        11 views
                        0 reactions
                        Last Post SEQadmin2  
                        Started by SEQadmin2, 07-08-2026, 10:08 AM
                        0 responses
                        9 views
                        0 reactions
                        Last Post SEQadmin2  
                        Started by SEQadmin2, 07-07-2026, 11:05 AM
                        0 responses
                        16 views
                        0 reactions
                        Last Post SEQadmin2  
                        Started by SEQadmin2, 07-02-2026, 11:08 AM
                        0 responses
                        31 views
                        0 reactions
                        Last Post SEQadmin2  
                        Working...