SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics

Similar Threads
Thread Thread Starter Forum Replies Last Post
Cufflinks / Cuffdiff problem Morten Bioinformatics 42 07-13-2013 11:51 PM
Why edgeR ouput some p values larger than 1 idyll_ty RNA Sequencing 1 02-01-2013 04:14 PM
Running problem with cuffdiff john_nl Bioinformatics 2 02-16-2012 12:21 PM
Bowtie ouput in Tophat unidodo Bioinformatics 2 03-30-2011 01:13 PM
Problem with Cuffdiff honey RNA Sequencing 3 01-04-2011 10:02 PM

Reply
 
Thread Tools
Old 06-16-2010, 03:09 PM   #1
ytmnd85
Member
 
Location: Nebraska

Join Date: Apr 2009
Posts: 10
Default Cuffdiff - ouput problem

I am attempting to use cuffdiff to do a comparison analysis of various yeast transcriptome samples. I have processed the reads via Tophat and compiled transcripts via Cufflinks. I would like to use Cuffdiff to generate a comparison between samples so that I can start compiling which genes are differentially expressed. I have attempted to run Cuffdiff several times, but I keep getting the same "segmentation fault" error. Here is an example of my input:

$ cuffdiff ../ethanol/transcripts.gtf ~/RNA_Seq/Yeast/reads_for_comp/tophat_output/ethanol/accepted_hits_e.sam ~/RNA_Seq/Yeast/reads_for_comp/tophat_output/glucose/accepted_hits_g.sam

I quickly get the following output:

Segmentation fault (core dumped)

Does anyone have any experience with this type of error arising from Cuffdiff, and any suggestions as to how I can correct this?

Thanks in advance for your help.
ytmnd85 is offline   Reply With Quote
Old 06-28-2010, 04:36 AM   #2
blackgore
Member
 
Location: UK

Join Date: Sep 2009
Posts: 19
Default

I don't have a solution, but I do have the same problem..though not always.

I used tophat and cufflinks with no problems on a total of 7 different samples. running cuffdiff on two particular samples threw the segmentation fault back at me, but worked fine for other samples. Other than the source organism (it worked for mammal, failed for insect), there was no difference in the way that these samples were prepared or analysed up to that point.
blackgore is offline   Reply With Quote
Old 02-25-2011, 06:15 AM   #3
nicolallias
Member
 
Location: France

Join Date: Jan 2010
Posts: 23
Default cuffdiff v0.9.3 seg. fault

Hello everyone,
I've found another way (maybe linked with your problem) to get the "Segmentation fault":
Code:
cuffdiff  -o ./ input.gtf input1.bam input2.bam
works fine, but
Code:
cuffdiff  -o ./another_directory input.gtf input1.bam input2.bam
causes the "Segmentation fault"

The "another_directory is visible and I've the rigth to write in... But I can't reproduce it on any directories (sometimes it works) :-?
I'm using the current version, v0.9.3
Anyone has the same problem ?

Last edited by nicolallias; 02-25-2011 at 06:28 AM.
nicolallias is offline   Reply With Quote
Old 02-25-2011, 08:24 AM   #4
pasta
Member
 
Location: Alps

Join Date: Jan 2011
Posts: 27
Default

Cuffdiff is a great tool but I stopped using it -> too many bugs
pasta is offline   Reply With Quote
Old 03-21-2011, 03:44 PM   #5
Aurelien Mazurie
Member
 
Location: Bozeman, MT

Join Date: Feb 2011
Posts: 15
Default

Quote:
Originally Posted by pasta View Post
Cuffdiff is a great tool but I stopped using it -> too many bugs
Do you know of a good alternative?
Aurelien Mazurie is offline   Reply With Quote
Old 05-16-2011, 05:38 PM   #6
fongchun
Member
 
Location: Vancouver, BC

Join Date: May 2011
Posts: 55
Default

Quote:
Originally Posted by nicolallias View Post
Hello everyone,
I've found another way (maybe linked with your problem) to get the "Segmentation fault":
Code:
cuffdiff  -o ./ input.gtf input1.bam input2.bam
works fine, but
Code:
cuffdiff  -o ./another_directory input.gtf input1.bam input2.bam
causes the "Segmentation fault"

The "another_directory is visible and I've the rigth to write in... But I can't reproduce it on any directories (sometimes it works) :-?
I'm using the current version, v0.9.3
Anyone has the same problem ?
This is actually exactly the same problem I was facing until I read your post. It appears that specifying an outdir other than the current directory caused a segmentation fault. So strange.
fongchun is offline   Reply With Quote
Old 06-09-2011, 02:32 PM   #7
flobpf
Member
 
Location: USA

Join Date: Apr 2010
Posts: 75
Thumbs up Dont specify output directory

Quote:
Originally Posted by fongchun View Post
This is actually exactly the same problem I was facing until I read your post. It appears that specifying an outdir other than the current directory caused a segmentation fault. So strange.
I had the segmentation fault despite specifying the same outdir as the current directory. However, if you DO NOT specify the output directory, the segmentation fault goes away. Cuffdiff is working for me now. Strange.
flobpf is offline   Reply With Quote
Old 06-10-2011, 12:31 AM   #8
vineeth_s
Junior Member
 
Location: Germany

Join Date: Jun 2011
Posts: 9
Default

Quote:
Originally Posted by Aurelien Mazurie View Post
Do you know of a good alternative?
Two alternatives exist:

1. Use HTSeq followed by DESeq : you must note though that there is a significant difference between how cufflinks/cuffdiff and HTSeq/DESeq look at mapping for quantification, there is an enlightening discussion here cufflinks/cuffdiff - HTSeq/DESeq debate

2. There is RSEQTools from the Gerstein lab, this I have not used personally, but the sequencing center attached to where I work base their RNA-Seq analysis pipeline on RSEQTools.

Vineeth
vineeth_s is offline   Reply With Quote
Old 06-10-2011, 12:38 AM   #9
vineeth_s
Junior Member
 
Location: Germany

Join Date: Jun 2011
Posts: 9
Default Addendum

Quote:
Originally Posted by vineeth_s View Post
Two alternatives exist:

there is an enlightening discussion here cufflinks/cuffdiff - HTSeq/DESeq debate
As that thread has quite many extraneous posts, follow the conversation between Lior Pachter (lpachter) and Simon Anders
vineeth_s is offline   Reply With Quote
Old 06-24-2011, 09:41 AM   #10
fongchun
Member
 
Location: Vancouver, BC

Join Date: May 2011
Posts: 55
Default

Quote:
Originally Posted by flobpf View Post
I had the segmentation fault despite specifying the same outdir as the current directory. However, if you DO NOT specify the output directory, the segmentation fault goes away. Cuffdiff is working for me now. Strange.
You are right. I specified -o ./cuffdiff_output and it gave me a segmentation fault halfway into the execution. It seems that the only surefire way of not crashing is to NOT specify any output directory.
fongchun is offline   Reply With Quote
Old 06-25-2011, 08:39 AM   #12
DZhang
Senior Member
 
Location: East Coast, US

Join Date: Jun 2010
Posts: 177
Default

Hi All,

Besides poisson200's suggestion, please make sure you are using the latest version to see if it helps. I know this package is under active development.

To me personally, different programs generate different numbers (F/R PKM), which must be unified down the road. It is not good for the science.

Douglas
www.contigexpress.com
DZhang is offline   Reply With Quote
Old 12-02-2011, 09:10 AM   #13
selen
Junior Member
 
Location: Ohio

Join Date: Dec 2010
Posts: 9
Thumbs up

Quote:
Originally Posted by flobpf View Post
I had the segmentation fault despite specifying the same outdir as the current directory. However, if you DO NOT specify the output directory, the segmentation fault goes away. Cuffdiff is working for me now. Strange.
I'm glad you all figured it out. I had the same problem and now it works with "-o ./" setting..Thanks!!!!
selen is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 02:47 AM.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.