Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • dariober
    Senior Member
    • May 2010
    • 311

    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 ]-----------------
  • Cole Trapnell
    Senior Member
    • Nov 2008
    • 213

    #2
    The trick I posted apparently doesn't always work - we know about this bug and will address it in an upcoming release

    Comment

    • dariober
      Senior Member
      • May 2010
      • 311

      #3
      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

      Comment

      • Cole Trapnell
        Senior Member
        • Nov 2008
        • 213

        #4
        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.

        Comment

        • rocksd
          Member
          • Jul 2010
          • 14

          #5
          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

          Comment

          Latest Articles

          Collapse

          • GATTACAT
            Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by GATTACAT
            Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
            07-01-2026, 11:43 AM
          • SEQadmin2
            Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by SEQadmin2


            I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

            Here are nine questions we think about, in roughly the order they matter, before...
            06-18-2026, 07:11 AM

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, Today, 11:05 AM
          0 responses
          7 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 07-02-2026, 11:08 AM
          0 responses
          28 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          27 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          26 views
          0 reactions
          Last Post SEQadmin2  
          Working...