strandedness - RNASeq library preparation
1
0
Entering edit mode
8.5 years ago

1.

       1 ---> 
=========================
               <--- 2

2.

       2 ---> 
=========================
               <--- 1

Q1. I came across above representations here on seqanswers. What do these two scenarios tell us about paired end library preparation. Is the 2nd one corresponding to "reversely" stranded scenario - like in the case of Agilent SureSelect RNA-Seq capture protocol? This is for me to have a clear understanding in my head.

Q2. Are there any transformations (reverse complementing) that Aligners do to these original reads sequences when they create a SAM/BAM file? I understand there are certain binary flags that are meant to say whether the reads are paired end, what strand the read is on, if the read is first or second in the paired end case,etc. Is there also a flag to say whether the sequence is reverse complement or it's original - is the strand information corrected accordingly? How do aligners take a decision on when to transform?

Thank you, for clearing away my confusion.

RNA-Seq strand • 3.8k views
ADD COMMENT
1
Entering edit mode
8.5 years ago

There are two different issues here that need not be confused.

  1. Alignment: each alignment contains information on attributes such as which file did the read come from (file 1 or file 2), which strand does the read align to, and if the read is paired etc.
  2. Library prep protocol + sequencing instrumentation. Depending on the combination of these two in a strand specific protocol one of the files file 1 or file 2 will contain data in the same orientation (or reverse orientation) relative to the mRNA. Note that this orientation is relative to the mRNA not the strand the mRNA comes from.

Here are a few relevant posts:

ADD COMMENT
0
Entering edit mode

Thanks, Istvan! Very useful links.

ADD REPLY

Login before adding your answer.

Traffic: 1771 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6