SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
cuffmerge/cuffcompare: result contains no p_id martin_313 Bioinformatics 1 01-12-2012 03:23 AM
Cufflinks p_id explanation fongchun Bioinformatics 1 06-27-2011 09:57 AM
Is it normal for cufflinks produce different results in multiple run superligang Bioinformatics 3 03-03-2011 01:40 AM
Cufflinks no p_ID but has TSS_ID RockChalkJayhawk Bioinformatics 6 12-08-2010 07:33 AM
cuffcompare fails to produce gtf and tracking chrisbala Bioinformatics 1 08-12-2010 07:11 AM

Reply
 
Thread Tools
Old 05-06-2010, 01:55 AM   #1
dariober
Senior Member
 
Location: Cambridge, UK

Join Date: May 2010
Posts: 311
Default cufflinks / cuffcompare does not produce p_id

Hello,

My first post here...!

I'm trying to use cuffcompare to produce a combined GTF file (stdout.combined.gtf) to feed to cuffdiff for further analysis. Cuffcompare should produce such GTF with added attributes tss_id and p_id. However, while my stdout.combined.gtf does have tss_ids it has no p_ids (even if the input file has CDS attributes). How is it?
I guess I can put the p_ids myself, but I'd like to understand what I'm doing wrong.

As a test, I ran cuffcompare using the pig GTF from ensembl against itself (following a trick from Cole Trapnell I found in another post) and indeed I couldn't 'see' any p_id in the output. See script below to reproduce this test.
Why I don't get p_ids?! Am I missing something very obvious?

I'm using version cufflinks-0.8.2.Linux_x86_64

Thanks in advance for any help!
Dario

Here's the little code:
# -----------------[ Cut here ]---------------------

## Download and unzip pig GTF
wget ftp://ftp.ensembl.org/pub/current_gt...ofa9.57.gtf.gz
gunzip Sus_scrofa.Sscrofa9.57.gtf.gz

## Run cuffcompare
/exports/work/vet_roslin_nextgen/dario/cufflink/current/cuffcompare -r Sus_scrofa.Sscrofa9.57.gtf Sus_scrofa.Sscrofa9.57.gtf Sus_scrofa.Sscrofa9.57.gtf

## No p_ids!!
grep p_id stdout.combined.gtf
==> no hits

# ----------------------[ Cut here ]-----------------
dariober is offline   Reply With Quote
Old 05-06-2010, 08:04 AM   #2
Cole Trapnell
Senior Member
 
Location: Boston, MA

Join Date: Nov 2008
Posts: 212
Default

The trick I posted apparently doesn't always work - we know about this bug and will address it in an upcoming release
Cole Trapnell is offline   Reply With Quote
Old 05-06-2010, 08:27 AM   #3
dariober
Senior Member
 
Location: Cambridge, UK

Join Date: May 2010
Posts: 311
Default

Quote:
Originally Posted by Cole Trapnell View Post
The trick I posted apparently doesn't always work - we know about this bug and will address it in an upcoming release
Hi Cole et al.,

Thanks for taking time to reply.
Is the bug due to some anomalies in the GTF file? If so, would it be possible to post a few lines from a GTF that works? A final question if you can answer... even if this bug occurs, are the other results from cuffdiff reliable? (I'm not interested in running the reference GTF against itself, that was just for testing purposes).

Dario
dariober is offline   Reply With Quote
Old 05-06-2010, 08:32 AM   #4
Cole Trapnell
Senior Member
 
Location: Boston, MA

Join Date: Nov 2008
Posts: 212
Default

We think they're reliable

The bug I mentioned is just in cuffcompare's ability to attach p_id attributes automatically. If the p_id attributes are missing, Cuffdiff will simply not perform a CDS-level differential analysis. It will look for changes in splicing and TSS preference (and of course gene and isoform-level expression), but it won't look for changes in coding output.
Cole Trapnell is offline   Reply With Quote
Old 07-22-2010, 01:32 PM   #5
rocksd
Member
 
Location: Houston, TX

Join Date: Jul 2010
Posts: 14
Default

Quote:
Originally Posted by Cole Trapnell View Post
We think they're reliable

The bug I mentioned is just in cuffcompare's ability to attach p_id attributes automatically. If the p_id attributes are missing, Cuffdiff will simply not perform a CDS-level differential analysis. It will look for changes in splicing and TSS preference (and of course gene and isoform-level expression), but it won't look for changes in coding output.
Cole,

Did you fix this bug?
I am running a Cuffdiff on two pig samples and ended up with Segment error. I then checked the combined_transcript.gtf file generated in Cuffcompare but did not find the p_id. By the way, I am using the cufflinks .8.4 version released 16/7/2010

Thanks a million!

jhuang
rocksd 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 06:46 AM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO