Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • fongchun
    Member
    • May 2011
    • 55

    Cufflinks p_id explanation

    Hi,

    I've been using cufflinks/tophats to work with 28 RNASeq libraries (some of which below to group A, and some to group B) and so far I've the following workflow:
    1. Ran tophat on each library with refseq gene model annotations
    2. Ran cufflinks on each library with refseq to Reference Based Assembly
    3. Ran cuffmerge on all the libraries with refseq
    4. Running cuffdiff between two groups merged.gtf from cuffmerge


    When I look at the merged.gtf file produced from cuffmerge, I see the attribute p_id added to some of the lines. According to the cufflinks website, p_id means:

    The ID of the coding sequence this transcript contains. This attribute is attached by Cuffcompare to the .combined.gtf records only when it is run with a reference annotation that include CDS records. Further, differential CDS analysis is only performed when all isoforms of a gene have p_id attributes, because neither Cufflinks nor Cuffcompare attempt to assign an open reading frame to transcripts.
    I've been struggling to understand exactly what this even means. They must be referring to the CDS features in my refseq.gtf file? Cuffdiff is supposed to output a cds_exp.diff file which according to the website:

    Coding sequence differential FPKM. Tests differences in the summed FPKM of transcripts sharing each p_id independent of tss_id
    When I look at the merged.gtf file, I have yet to see transcript share the same p_id. Only exons of the same transcript share the same p_id. Am I missing something here? What does the p_id attribute even truly mean? Is my pipeline wrong here or something?

    Thanks,

    Fong
  • fongchun
    Member
    • May 2011
    • 55

    #2
    Does anyone have an answer to this question? Or some more reference as to where I can find this information?

    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, Yesterday, 11:08 AM
    0 responses
    6 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-30-2026, 05:37 AM
    0 responses
    11 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-26-2026, 11:10 AM
    0 responses
    19 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-17-2026, 06:09 AM
    0 responses
    53 views
    0 reactions
    Last Post SEQadmin2  
    Working...