Seqanswers Leaderboard Ad

Collapse

Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • HTseq-count : how to get unique reads?

    Hello,

    I used HTseq-count to get number of reads / gene from my RNA-seq data.

    The problem is that the sum of all counted reads (on every gene) is much bigger then the total sequencing depth I got from Illumina. After reading other posts, this could be due to the "duplicate" alignemnt... Anyway, my question is: how to get the true number of reads for some genes (in my case rRNA) in order to see what percentage of my total sequencing depth is actually "lost" on rRNA?

    Thanks in advance for any hints,

    TP

  • #2
    Perhaps, I addressed the question in the wrong way. Simply, i just wanna know how to get the Ribosomal RNA contamination in each of my libraries? I want to be able to say that 1E07 reads out of 1E09 are mapping to rRNA, so my samples are "contaminated" by 1% rRNA. See?

    Thanks

    Comment


    • #3
      This will require additional work but could get rid of the contamination in the process.
      http://seqanswers.com/forums/showthread.php?t=26960 Use the rRNA sequence for the species you are working with.

      Comment


      • #4
        Yeah I saw that thread... I was hoping for faster solution, but well
        Thanks

        Comment


        • #5
          htseq-count should identify the number of multimapped reads and include this number in its own category so that the total number should not exceed your starting number of reads....unless, whatever you mapped the reads with does not output a NH:i field in the SAM file.

          What did you use to map the reads?

          Are you specifically interested in only rRNA reads...not everything that maps multiple times will be an rRNA read.

          Comment


          • #6
            Originally posted by chadn737 View Post
            htseq-count should identify the number of multimapped reads and include this number in its own category so that the total number should not exceed your starting number of reads....unless, whatever you mapped the reads with does not output a NH:i field in the SAM file.

            What did you use to map the reads?

            Are you specifically interested in only rRNA reads...not everything that maps multiple times will be an rRNA read.
            I used bowtie for mapping. After that, I used Htseq-count to get number of reads/gene. If I sum all the reads for one replicate from Htseq table I get like double of what I'm supposed to have. I guess it's because of all multimapped reads. I will try to align my libraries only to rRNA, that should give me number of reads mapping there.

            TP

            Comment


            • #7
              Originally posted by ThePresident View Post
              I used bowtie for mapping. After that, I used Htseq-count to get number of reads/gene. If I sum all the reads for one replicate from Htseq table I get like double of what I'm supposed to have. I guess it's because of all multimapped reads. I will try to align my libraries only to rRNA, that should give me number of reads mapping there.

              TP
              Bowtie does not output a NH:i field in the SAM file and so htseq-count will not be able to identify multimapping reads.

              Furthermore, Bowtie is not ideally suited for RNA-seq data. You should use Tophat instead, Tophat puts out a NH:i field, and so then your htseq-count results will make sense. I would not use htseq-count on data aligned with bowtie unless multi-mapped reads were first removed or identified. Otherwise, your read counts for each gene will be incorrect. Furthermore, bowtie is not a spliced aligner and will preferentially align to the best match, even if its a pseudogene. With tophat, you can deal with splicing. Unless you have good reason to use bowtie, I would realign everything with tophat instead and problem solved.

              Also, as I said previously, not all multimapping reads will be due to rRNA, so if you are trying to identify/eliminate multimapping reads, aligning to rRNA does not solve your problem.

              Depending on whether you used bowtie or bowtie 2 (and if bowtie 2, what mode you ran it in) it is possible to remove all multimapping reads and get the unique reads only by filtering on quality scores.

              Comment


              • #8
                Well, I'm dealing with bacterial RNA-seq data, so a spliced aligner such as Tophat was irrelevant in this case. However, I didn't realize that bowtie is messing up with multimapped reads

                I think that overall my alignment was not so bad, 'cause many genes identified as transcriptionally altered in my RNA-seq were confirmed by qPCR. However, I might try tophat as well.

                About rRNA, it's just that I want to present some data in a paper I'm working on, and would like to give the number of reads that aligned on rRNA in my libraries. That way, it would give the audience some idea about abundance of "real" transcripts in my libraries.

                Comment


                • #9
                  Originally posted by ThePresident View Post
                  Well, I'm dealing with bacterial RNA-seq data, so a spliced aligner such as Tophat was irrelevant in this case. However, I didn't realize that bowtie is messing up with multimapped reads

                  I think that overall my alignment was not so bad, 'cause many genes identified as transcriptionally altered in my RNA-seq were confirmed by qPCR. However, I might try tophat as well.

                  About rRNA, it's just that I want to present some data in a paper I'm working on, and would like to give the number of reads that aligned on rRNA in my libraries. That way, it would give the audience some idea about abundance of "real" transcripts in my libraries.
                  There seems no reason to use tophat then.

                  What version of bowtie did you use and how did you use it. If you want to present data on rRNA, you can align specifically to these, however, to quickly identify uniquely mapped reads, you can filter based on quality score depending on what version of bowtie you used and how you ran it.

                  Comment


                  • #10
                    I used bowtie (not bowtie2) with following command line:

                    Code:
                    bowtie -q -a --best –m50 –p6 -t index 6_Index-1.WT_1_R1.fastq -S AlignWT1
                    So, I used -a for bowtie to report all alignments and --best to give only best hits.

                    Now, how you would filter for quality scores with bowtie?

                    Comment


                    • #11
                      Originally posted by ThePresident View Post
                      I used bowtie (not bowtie2) with following command line:

                      Code:
                      bowtie -q -a --best –m50 –p6 -t index 6_Index-1.WT_1_R1.fastq -S AlignWT1
                      So, I used -a for bowtie to report all alignments and --best to give only best hits.

                      Now, how you would filter for quality scores with bowtie?
                      By default, bowtie should assign a mapping quality of 255 to reads that map once. You can filter using samtools view:

                      Code:
                      samtools view -hb -q 255 input.bam > output.bam
                      Your output should have only uniquely aligned reads.

                      Comment


                      • #12
                        Thanks, I'll try that instead!

                        Comment

                        Latest Articles

                        Collapse

                        • seqadmin
                          Genetic Variation in Immunogenetics and Antibody Diversity
                          by seqadmin



                          The field of immunogenetics explores how genetic variations influence immune responses and susceptibility to disease. In a recent SEQanswers webinar, Oscar Rodriguez, Ph.D., Postdoctoral Researcher at the University of Louisville, and Ruben Martínez Barricarte, Ph.D., Assistant Professor of Medicine at Vanderbilt University, shared recent advancements in immunogenetics. This article discusses their research on genetic variation in antibody loci, antibody production processes,...
                          11-06-2024, 07:24 PM
                        • seqadmin
                          Choosing Between NGS and qPCR
                          by seqadmin



                          Next-generation sequencing (NGS) and quantitative polymerase chain reaction (qPCR) are essential techniques for investigating the genome, transcriptome, and epigenome. In many cases, choosing the appropriate technique is straightforward, but in others, it can be more challenging to determine the most effective option. A simple distinction is that smaller, more focused projects are typically better suited for qPCR, while larger, more complex datasets benefit from NGS. However,...
                          10-18-2024, 07:11 AM

                        ad_right_rmr

                        Collapse

                        News

                        Collapse

                        Topics Statistics Last Post
                        Started by seqadmin, Today, 11:09 AM
                        0 responses
                        22 views
                        0 likes
                        Last Post seqadmin  
                        Started by seqadmin, Today, 06:13 AM
                        0 responses
                        20 views
                        0 likes
                        Last Post seqadmin  
                        Started by seqadmin, 11-01-2024, 06:09 AM
                        0 responses
                        30 views
                        0 likes
                        Last Post seqadmin  
                        Started by seqadmin, 10-30-2024, 05:31 AM
                        0 responses
                        21 views
                        0 likes
                        Last Post seqadmin  
                        Working...
                        X