Header Leaderboard Ad

Collapse

Why does Cufflinks assign a strand to some RNA sequences but not others?

Collapse

Announcement

Collapse

SEQanswers June Challenge Has Begun!

The competition has begun! We're giving away a $50 Amazon gift card to the member who answers the most questions on our site during the month. We want to encourage our community members to share their knowledge and help each other out by answering questions related to sequencing technologies, genomics, and bioinformatics. The competition is open to all members of the site, and the winner will be announced at the beginning of July. Best of luck!

For a list of the official rules, visit (https://www.seqanswers.com/forum/sit...wledge-and-win)
See more
See less
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Why does Cufflinks assign a strand to some RNA sequences but not others?

    I am analyzing RNASeq data using a Tuxedo pipeline. For the most part, the RNA sequences seem to align with known genes in the correct orientations.

    A number of putatively new genes have been discovered, however. In the output GTF file, though, some of these new genes are not assigned to either the sense or the antisense strand, i.e. column 7 contains a "." instead of + or - sign.

    Does anyone know why this might be the case? This seems to happen for the new genes but not the already known genes.

    In the Cufflinks part of the analysis, I used the --GTF-guide option with a GFF3 file of exon locations that I downloaded from Flybase. I also used
    --upper-quartile-norm --min-intron-length 5

  • #2
    Originally posted by gwilymh View Post
    I am analyzing RNASeq data using a Tuxedo pipeline. For the most part, the RNA sequences seem to align with known genes in the correct orientations.

    A number of putatively new genes have been discovered, however. In the output GTF file, though, some of these new genes are not assigned to either the sense or the antisense strand, i.e. column 7 contains a "." instead of + or - sign.

    Does anyone know why this might be the case? This seems to happen for the new genes but not the already known genes.

    In the Cufflinks part of the analysis, I used the --GTF-guide option with a GFF3 file of exon locations that I downloaded from Flybase. I also used
    --upper-quartile-norm --min-intron-length 5
    A couple of questions:

    Was the RNA-Seq library prepared using a strand-specific prep method?

    If it was prepared using a strand-specific method where the proper parameters passed to TopHat and Cufflinks?

    If an RNA-Seq library is prepared using a method which does not preserve strand information (e.g. TruSeq RNA Prep Kit v2) then Cufflinks is unable to determine simply from the alignment which strand the original RNA was transcribed from. If the read overlaps a known, annotated gene (i.g. you are providing a GFF file to TopHat/Cufflinks) it will assume the read originated from the known gene for which the strand is already known. Cufflinks creates a novel gene model from a group of aligned reads it can not know a priori which strand the RNA is transcribed from. In some cases, if there enough reads mapping across intron/exon junctions Cufflinks will impute the strand information based on the canonical directionality of the splice junction(s).

    Comment

    Latest Articles

    Collapse

    ad_right_rmr

    Collapse

    News

    Collapse

    Topics Statistics Last Post
    Started by seqadmin, Yesterday, 07:14 AM
    0 responses
    4 views
    0 likes
    Last Post seqadmin  
    Started by seqadmin, 06-06-2023, 01:08 PM
    0 responses
    6 views
    0 likes
    Last Post seqadmin  
    Started by seqadmin, 06-01-2023, 08:56 PM
    0 responses
    125 views
    0 likes
    Last Post seqadmin  
    Started by seqadmin, 06-01-2023, 07:33 AM
    0 responses
    262 views
    0 likes
    Last Post seqadmin  
    Working...
    X