Detecting antisense RNA in unstranded RNA-Seq data
1
0
Entering edit mode
5.5 years ago
newbio17 ▴ 360

I've gone over a couple of previous questions discussing a similar subject and they seem to all imply that it simply is not feasible to do with unstranded RNA-Seq data.

We know that for RNA-Seq, RNA is reverse transcribed into cDNA and that antisense RNA is complementary to its mRNA on the sense strand. If we were interested in detecting antisense RNA for a given gene, can't we just look for a complementary sequence of the gene (e.g. first 20 sequences)?

I understand this could be a problem since we don't know whether the matching sequence from the RNA-Seq reads is actually coming from the antisense strand, but how likely is it to detect, for example, a sequence of length 20, on the sense strand by chance?

Are there any additional things that should be taken into consideration?

Thank you.

RNA-Seq antisense RNA • 2.1k views
ADD COMMENT
1
Entering edit mode

De novo discovery of antisense transcripts using unstranded sequencing data can be challenging. One trivial approach is to construct a list of annotated antisense transcripts whose splice sites do not overlap with the corresponding sense transcripts that code for proteins. You can use reads that are mapped to these junctions as a proxy to approximate antisense expression. You can perhaps expand such approach with splice site discovery to identify unannotated antisense. YMMV.

ADD REPLY
1
Entering edit mode
5.5 years ago
caggtaagtat ★ 1.9k

In unstranded RNA-Seq data, you generate reads, which represent the sense and anitsense of the sequenced RNA fragment, making it very difficult or even impossible to determine reads coming from sequencing of antisense RNA.

One approach could be maybe, if you look at gapped reads, in case there are splice sites in the sense and antisense transcript.

ADD COMMENT

Login before adding your answer.

Traffic: 2350 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