Seqanswers Leaderboard Ad

Collapse

Announcement

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

  • Bioinyang
    replied
    Originally posted by frozenlyse View Post
    Early RNA-seq protocols were unstranded ie the RNA may have originated on the plus strand, but because the library was created from double stranded cDNA you obtain reads from both the plus and minus strand - in this case the samtools flag for which strand the read mapped to doesnt tell you which strand the RNA it originated from. However, if the read is across a splice junction you can work it out (as charlie_sequencing posted) hence the tophat XS flag. Reads from an unstranded library which do not cross a splice cannot be assigned a strand.

    However, lots of people are doing stranded RNA-seq these days where the reads only come from one strand which is a lot nicer.
    Hi,frozenlyse, As you said, unstranded library we don't konw reads come from which strand. Now I have a dataset of dUTP and I use --library firststrand .Tophat said,"it is assumed that only the strand generated during first strand synthesis is sequenced.",that means, the reads come from minus strand. But I found a half of reads was taged "XS:A:+"

    Leave a comment:


  • flobpf
    replied
    Other posts that may be of help

    Please check out these posts for a discussion of directional sequencing and XS:A tags:

    Bridged amplification & clustering followed by sequencing by synthesis. (Genome Analyzer / HiSeq / MiSeq)

    and
    Discussion of next-gen sequencing related bioinformatics: resources, algorithms, open source efforts, etc

    Leave a comment:


  • frozenlyse
    replied
    Early RNA-seq protocols were unstranded ie the RNA may have originated on the plus strand, but because the library was created from double stranded cDNA you obtain reads from both the plus and minus strand - in this case the samtools flag for which strand the read mapped to doesnt tell you which strand the RNA it originated from. However, if the read is across a splice junction you can work it out (as charlie_sequencing posted) hence the tophat XS flag. Reads from an unstranded library which do not cross a splice cannot be assigned a strand.

    However, lots of people are doing stranded RNA-seq these days where the reads only come from one strand which is a lot nicer.

    Leave a comment:


  • charlie_sequencing
    replied
    Thanks so much for your reply, nilshomer and dagarfield. I found the Cufflinks manual http://cufflinks.cbcb.umd.edu/manual.html where XS field was specified. When a read is mapped to the ref across splicing junctions, the boundary of intron (GT-AG, or CT-AC) will tell you the value of XS: "+" for GT-AG and "-" for CT-AC. It tells you "which strand the RNA that produced this read came from".

    This led me to think about another question: is TopHat able to report the strand of the read if it is completely contained within an exon, i.e., without N in the CIGAR string?

    Leave a comment:


  • dagarfield
    replied
    There are two places in a SAM file that, on the surface, *seem* to provide equivalent information -- the second column (0 vs 16, or something) and the XS:A field.

    I have a vague memory that the first tells you about mapping relative to the reference sequence. The second (XS:A) tells you something about the direction/strand of the *read itself*.

    I wish I could find the post I read that told me that. I first came across the distinction while trying to understand the input fields required for TopHat. You might give a try searching for "TopHat" and "XS field" together. Please post back if you figure it out.

    Best of luck,

    DG

    Leave a comment:


  • nilshomer
    replied
    Originally posted by charlie_sequencing View Post
    Does anyone know what XS:A field in samtools output mean by any chance?

    XS:A (A is the SAM attribute type) can take the values of "+" or "-". I thought "+" or "-" might be related to how the read is mapped to the ref (forward or reverse complement), but it turned out not the case, because forward or reverse complement read can take both values.

    Thanks!
    The optional tags are specific to the aligner that generated them. What aligner did you use? Take a look at the manual from that aligner.

    Leave a comment:


  • charlie_sequencing
    started a topic samtools XS:A optional field

    samtools XS:A optional field

    Does anyone know what XS:A field in samtools output mean by any chance?

    XS:A (A is the SAM attribute type) can take the values of "+" or "-". I thought "+" or "-" might be related to how the read is mapped to the ref (forward or reverse complement), but it turned out not the case, because forward or reverse complement read can take both values.

    Thanks!

Latest Articles

Collapse

  • seqadmin
    Investigating the Gut Microbiome Through Diet and Spatial Biology
    by seqadmin




    The human gut contains trillions of microorganisms that impact digestion, immune functions, and overall health1. Despite major breakthroughs, we’re only beginning to understand the full extent of the microbiome’s influence on health and disease. Advances in next-generation sequencing and spatial biology have opened new windows into this complex environment, yet many questions remain. This article highlights two recent studies exploring how diet influences microbial...
    02-24-2025, 06:31 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by seqadmin, 03-03-2025, 01:15 PM
0 responses
169 views
0 likes
Last Post seqadmin  
Started by seqadmin, 02-28-2025, 12:58 PM
0 responses
259 views
0 likes
Last Post seqadmin  
Started by seqadmin, 02-24-2025, 02:48 PM
0 responses
641 views
0 likes
Last Post seqadmin  
Started by seqadmin, 02-21-2025, 02:46 PM
0 responses
265 views
0 likes
Last Post seqadmin  
Working...
X