Biostar Beta. Not for public use.
How to know that your RNA-seq is stranded or not?
11
Entering edit mode
21 months ago
M K • 460
United States

Is there any way to detect if your rna-seq data is unstranded or stranded

RNA-Seq • 12k views
ADD COMMENTlink
21
Entering edit mode
15 months ago
Wayne • 320
Syracuse, NY, United States

In case anybody currently looking comes across this post...

The easy-to-use Salmon will check for you as described here. You can see what the resulting abbreviations correspond to with a nice illustration here.

ADD COMMENTlink
0
Entering edit mode

+1 on a taking the time to post a more modern solution. I wonder if there is a way to in biostar to highlight answers like this.

ADD REPLYlink
1
Entering edit mode

Upvoting it and/or selecting it as an accepted answer is the way to go. Commenting as you did is also helpful. Bioinformatics changes more rapidly hence we have to more proactive in marking up the most recent correct answer.

ADD REPLYlink
0
Entering edit mode

There are some great answers posted already, but just in case you want to learn more about strandness, you can also check this previous post: Read pair orientation : Illumina TruSeq Stranded mRNA library

ADD REPLYlink
5
Entering edit mode
15 months ago
Chris Fields ♦ 2.1k
University of Illinois Urbana-Champaign

A few RNA-Seq QC tools will detect whether a run is strand-specific. For example, the infer_experiment.py script in the following claims to do this (never used this myself, so can't vouch for it):

http://rseqc.sourceforge.net/

ADD COMMENTlink
0
Entering edit mode

even this seems to require a BAM file to operate, so at that point one could look at the file

ADD REPLYlink
0
Entering edit mode

Yep. Only other way I can think of is to check whether there is a strand-specific adaptor used, but this normally gets stripped off the sequence prior to the user getting their hands on it (at least our center does).

Actually, I don't recall whether the TruSeq strand-specific adaptor is the same sequence as their other non-strand-specific counterparts, but then again I've never had to worry about checking for this. Seq centers we've worked with are normally pretty explicit in telling us what protocols and adaptors they use.

ADD REPLYlink
0
Entering edit mode
18 months ago
Josh Herr 5.6k
University of Nebraska

If you have a reference you could map to it to find out. There might be another way, but nothing else comes to mind.

ADD COMMENTlink
0
Entering edit mode
16 months ago
Irsan ♦ 6.9k
Amsterdam
if you don't know what sample prep protocol was used you have to map your reads to a reference genome and look at the sam flags in the bam file. If it is stranded, flags 83, 99, 147 and 163 have the same abundance but in stranded, 2 of these 4 will disappear when you look at either sense or antisense genes only.
ADD COMMENTlink
0
Entering edit mode

It might be easier to map to the transcriptome than the genome. Then you know you are mapping to the sense side.

Remember that certain protocols map the first read to the sense strand and the second read to the antisense. Others do it the reverse (the first read is antisense).

Do you know the protocol that was used? You should be able to tell from that whether it is stranded. Joshua Levin has a paper from a couple years ago that compared a bunch of stranded protocols.

ADD REPLYlink
0
Entering edit mode

I'm trying to figure out if my data is stranded or not. Salmon shows that it is, tags in bam file are 99 and 147 but when I plot it in Genome Browser there is almost no difference in expression between the strands. How could that be?

ADD REPLYlink
0
Entering edit mode
15 months ago
Colombia/Universidad de Antioquia

Hi

This image could help. https://galaxyproject.org/tutorials/rb_rnaseq/stranded_result.png

In stranded example reads are clearly stratified between the two strands

Of course, you need to perform the alignments, get the BAM file and visualize it in any of the software available (SeqMonk, RNAseqViewer, IGB, etc)

ADD COMMENTlink

Login before adding your answer.

Similar Posts
Loading Similar Posts
Powered by the version 2.3