Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • wenhuang
    Member
    • Feb 2010
    • 30

    polyA containing reads in RNA-seq

    Hi,

    I am just curious if any of the existing softwares for RNA-seq analysis handles polyA containing reads. I am not aware of one that explicitly tries to map polyA containing reads.

    Thanks!
  • john_mu
    Member
    • May 2010
    • 88

    #2


    This paper deals with detection of Polyadenylation sites from RNA-seq reads, but they do not release the software.
    SpliceMap: De novo detection of splice junctions from RNA-seq
    Download SpliceMap Comment here

    Comment

    • epigen
      Senior Member
      • May 2010
      • 101

      #3
      It depends on what you want to do with poly-A containing reads. The usual software does not look at your reads to classify them in any way, it just tries to map them. You can create something like an "artificial genome" containing sequences you want to exclude (or specifically want to extract), e.g. poly-A, repeats, rRNA etc., as a reference to which you align your reads. If this is what you're looking for, e.g. the SOLiD BioScope WT pipeline provides such sequences to be used as filters, but I'm sure you can also find them somewhere else.

      Comment

      • ryanmcg
        Junior Member
        • Dec 2012
        • 6

        #4
        Originally posted by john_mu View Post
        http://www.nature.com/nature/journal...ture08872.html

        This paper deals with detection of Polyadenylation sites from RNA-seq reads, but they do not release the software.
        I am interested in doing exactly what this paper describes, but their methods do not give me enough detail to do this (without already having a fair amount of programming knowledge).

        Is there not a tool that is built to do this type of analysis? I imagine it would be popular.

        Comment

        • ryanmcg
          Junior Member
          • Dec 2012
          • 6

          #5
          Here is the passage from their supplement. Any suggestions on how to implement this?

          As described above, our mapping strategy allowed us to find putative novel polyadenylation sites.
          We first identified all sequencing reads that did not initially map to the genome and either began or
          ended with a run of at least four As or T. We then trimmed off the run of As or Ts and remapped
          the reads to the genome using MAQ. At those reads that then mapped uniquely to the genome,
          we inferred the precise base where cleavage occurred. To filter out cleavage sites possibly due
          to sequencing errors, we removed putative polyadenylation sites where the downstream genomic
          regions contained at least three As or Ts, reasoning that a sequencing error at the non-A or T
          site might lead to mis-mismapping and spurious calling of a poly-A site.

          Comment

          • ryanmcg
            Junior Member
            • Dec 2012
            • 6

            #6
            part of the way there: trimest

            Comment

            • Brian Bushnell
              Super Moderator
              • Jan 2014
              • 2709

              #7
              You can filter or trim reads matching certain patterns, like poly-A, with BBDuk. For example:

              bbduk.sh in=reads.fq out=trimmed.fq ktrim=r k=8 literal=AAAAAAAAAAAA mm=f rcomp=f

              That will trim reads to the right, starting at the first poly-A of at least 8 in a row. If you only want to look at tails, you could use "restrictright=20" to only look for matches in the last 20bp of the read. Without the "ktrim=r" flag, it will run in filtering mode:

              bbduk.sh in=reads.fq outm=matched.fq out=unmatched.fq k=8 literal=AAAAAAAAAAAA mm=f rcomp=f

              "rcomp=f" means only look for a kmer and not its reverse complement (in this case, poly-T); you can turn that on or off.

              Comment

              Latest Articles

              Collapse

              • 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
              • SEQadmin2
                Nine Things a Sample Prep Scientist Thinks About Before Sequencing
                by SEQadmin2


                I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

                Here are nine questions we think about, in roughly the order they matter, before...
                06-18-2026, 07:11 AM

              ad_right_rmr

              Collapse

              News

              Collapse

              Topics Statistics Last Post
              Started by SEQadmin2, Yesterday, 11:08 AM
              0 responses
              7 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-30-2026, 05:37 AM
              0 responses
              11 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-26-2026, 11:10 AM
              0 responses
              19 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-17-2026, 06:09 AM
              0 responses
              53 views
              0 reactions
              Last Post SEQadmin2  
              Working...