![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Bug? duplicated genes in cufflinks output genes.expr | silin284 | Bioinformatics | 3 | 05-18-2014 12:19 AM |
Cufflinks, differentially expressed genes | statsteam | Bioinformatics | 5 | 11-15-2013 12:28 PM |
Cufflinks merging more than one transcript on bacterial genomes | Noa | Bioinformatics | 2 | 01-24-2012 01:33 PM |
Cufflinks merging more than one transcript on bacterial genomes | Noa | RNA Sequencing | 0 | 01-24-2012 06:41 AM |
Cufflinks extending/merging exons | kbushley | Bioinformatics | 2 | 10-18-2011 10:39 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Junior Member
Location: Toronto Join Date: May 2010
Posts: 6
|
![]()
Hi everyone,
I'm running Cufflinks (v 0.9.3) on one of my datasets (human, 50 bp PE, around ~600-700 million reads), and tried to assemble transcripts without prior annotation. For the most part, the program works very well. However, when genes adjacent to one another (intergenic distance on the order of a small/medium-sized intron) are the same strand, Cufflinks merge multiple genes into one transcript. I've attached a picture of this example, where DVL2 & PHF23 are both part of the same Cufftranscript. Would anyone have any recommendations to fix this or reduce the chances of it happening? Since the intergenic distance is short, tweaking the "max-intron-length" flag in Cufflinks probably won't help here. Thanks! |
![]() |
![]() |
![]() |
#2 |
Member
Location: Berkeley, cA Join Date: Feb 2010
Posts: 40
|
![]()
This problem is most likely being caused by polymerase run off on the 3' end of the PHF23 gene.
It is possible, in principle, to identify two distinct genes from such data if the coverage is substantially different. However at this time the Cufflinks assembler does not explicitly take such information into account (it does in phasing alternative transcripts). A new forthcoming feature in Cufflinks to be released in the next version is a "reference guided assembly" where you can inform the assembler based on existing annotation. In this case, the resulting assembly would contain the two known genes thus preventing your problem. The nice thing is that the reference guided assembler will still allow for the discovery of new transcripts. Coming soon. |
![]() |
![]() |
![]() |
#3 |
Junior Member
Location: Toronto Join Date: May 2010
Posts: 6
|
![]()
Thanks! It definitely looks like polymerase run-off, so it'll be great to use the new Cufflinks feature for using reference assemblies to separate these merged genes.
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|