Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • N00bSeq
    Member
    • Mar 2014
    • 12

    Cuffcompare fails to properly match reference to itself

    I have stumbled upon something that I consider really strange.

    I ran cuffcompare (2.2.0) on the Ensembl mouse reference annotation from igenomes (NCBI37, May 14 22:13), using both the same genes.gtf as reference and query (nevermind why; just for some troubleshooting).

    Code:
    cuffcompare -r igenomes/Mus_musculus/Ensembl/NCBIM37/Annotation/Genes/genes.gtf igenomes/Mus_musculus/Ensembl/NCBIM37/Annotation/Genes/genes.gtf
    What I observed was this:

    Code:
    awk '{print $3}' Ensembl_Ensembl.genes.gtf.refmap | sort | uniq -c
      93459 =
        180 c
          1 class_code
    Now, why are there 180 transcripts in the reference that do not completely match themselves in the same reference?

    I find this really strange. And since I have been getting some strange results in other parts of my analysis (regarding fpkm distributions of "=" and "c" transcripts), I would really like to know the reason that the above situation occurs.

    I decided to take a closer look at some of the "c" transcripts of the "Ensembl-Ensembl" comparison. Gm8292 is one of the problamatic genes. This gene has two different transcripts registered in the genes.gtf file:

    Code:
    grep "Gm8292" genes.gtf
    
    1       pseudogene      exon    55392211        55392351        .       +       .       exon_number "1"; gene_biotype "pseudogene"; gene_id "ENSMUSG00000089944"; gene_name "Gm8292"; transcript_id "ENSMUST00000135190"; transcript_name "Gm8292-201"; tss_id "TSS72358";
    1       transcribed_processed_pseudogene        exon    55392245        55392640        .       +       .       exon_number "1"; gene_biotype "pseudogene"; gene_id "ENSMUSG00000089944"; gene_name "Gm8292"; transcript_id "ENSMUST00000162574"; transcript_name "Gm8292-001"; tss_id "TSS50335";
    1       pseudogene      exon    55392353        55392727        .       +       .       exon_number "2"; gene_biotype "pseudogene"; gene_id "ENSMUSG00000089944"; gene_name "Gm8292"; transcript_id "ENSMUST00000135190"; transcript_name "Gm8292-201"; tss_id "TSS72358";
    The corresponding cuffcompare annotation in the refmap file for this gene:

    Code:
    grep "Gm8292" Ensembl_Ensembl.genes.gtf.refmap
    
    Gm8292  ENSMUST00000135190      =       Gm8292|ENSMUST00000135190
    Gm8292  ENSMUST00000135190      c       Gm8292|ENSMUST00000162574
    So it appears that ENSMUST00000135190 completely matches one of the two annotated transcripts for this gene ("="), while the other (ENSMUST00000162574) is only considered a partial match, even though it obviusly is present in the genes.gtf file.

    (One might note that this particular problematic transcript is a transcribed processed pseudogene, but there are also regular protein coding transcripts among the 180 "c" matches.)

    Maybe I have misunderstood something fundamentally about how cuffcompare works. One explanation could simply be that every isoform except for the "largest" isoform of a given gene is considered a partial match to that larger isoform. But if that was the case, shouldn't there be more than 180 such alternative isoforms in the mouse genome instead? This makes me think that this is a bug in cuffcompare.

    Can anyone shed any light on this? Has anyone seen anything similar? Any theories about what might be going on here?

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