Identification of major isoform per gene from RNA-Seq
1
1
Entering edit mode
9.0 years ago
Leszek 4.2k

I would like to find out whether there are any changes in major isoform (most expressed) per gene in my time course experiment. I can get this information by parsing FPKM values from cufflinks.

Do you know of any more sophisticated tool/method capable of identifying major isoform changes between conditions?

EDIT: I've ended up writing my own script. Details in here.

EDIT2: fpkm2major.py can be downloaded from my github

cufflinks RNA-Seq • 4.0k views
ADD COMMENT
0
Entering edit mode

Could you please share your scripts!

ADD REPLY
0
Entering edit mode

Just to add on to this, you can try Kallisto -> Sleuth now to analyse at the transcript level, which was unavailable when this post started.

ADD REPLY
0
Entering edit mode
9.0 years ago

I'd use CummerBund to extract your CuffDiff results into R, and get your gene FPKM and isoform FPKM tables. From that you'll need to map Gene ID's to Transcript ID's and filter each to find your dominant isoform. Beware that due to the nature of isoform switching, you may find that different isoforms are dominent in different conditions. I don't really see what you'll achieve by looking at only the "major isoforms".

ADD COMMENT
0
Entering edit mode

Isoform switching is exactly what I would like to analyse. If there is no tool for that, I'll write something myself. Thanks!

ADD REPLY
0
Entering edit mode

Ah, I've done some work on that, but it's tricky to say the least. I used EBSeq with fractional counts, I'd suggest that'd be a good stating point. You can get fractional counts out of Tuxedo, using cummerbund, the function is hard to find - check out the repCountMatrix() function.

ADD REPLY
0
Entering edit mode

Thanks for advice. I've ended up writing my own script (fpkm2major.py) available also in my github

ADD REPLY

Login before adding your answer.

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