SEQanswers

Go Back   SEQanswers > Applications Forums > RNA Sequencing



Similar Threads
Thread Thread Starter Forum Replies Last Post
Cuffmerge duplicate/invalid 'transcript' dawn1313 Bioinformatics 0 07-18-2016 05:07 PM
Cuffmerge Exon vs Transcript output from Cufflinks Problem. tonup69 Bioinformatics 0 02-18-2016 08:58 AM
Cuffmerge drops gene_ids and transcript features? mary12 RNA Sequencing 0 02-24-2015 12:03 PM
Need advice: want to create a gtf file of transcript sequences JonB RNA Sequencing 0 08-29-2013 12:27 PM
Cuffmerge output: merged.gtf and transcript.gtf always vary ? Chirag RNA Sequencing 6 01-15-2013 07:20 AM

Reply
 
Thread Tools
Old 07-28-2017, 01:33 AM   #1
JoannaF
Junior Member
 
Location: France

Join Date: Jul 2017
Posts: 1
Default Cuffmerge create a de novo transcript for an existing one and output both

Hi, I want to analyse RNA-seq data files. The pipeline used is HISAT2 > Stringtie (.gtf files) > cuffmerge (merged.gtf file). But I have an issue with the merged.gtf file produced by cuffmerge. I have two lines with the same coordinates (chromosome, start, end), width, strand, etc, except the transcript_id and the oId which are not the same. In the "contained_in" column, there is <na> for one exon and TCONS_00000003 for the other exon. Here there is an exemple of this issue but there are a lot of lines like that for others exons in this file :

HTML Code:
seqnames   start     end width strand    source type score phase     gene_id  transcript_id exon_number     gene_name                  oId          nearest_ref class_code tss_id   contained_in p_id
chr1 3252757 3253236   480      + Cufflinks exon    NA    NA XLOC_000003 TCONS_00000004           1       Gm18956 ENSMUST00000192857.1 ENSMUST00000192857.1          =   TSS3 TCONS_00000003 <NA>
4     chr1 3252757 3253236   480      + Cufflinks exon    NA    NA XLOC_000003 TCONS_00000003           1       Gm18956             CUFF.3.2 ENSMUST00000192857.1          =   TSS3           <NA> <NA>
It seems that cuffmerge thinks that these two exons are not the same exon because the first comes from a transcript de novo (transcript_id : "CUFF.3.2") and the other comes from a known transcript (transcript_id : "ENSMUST00000192857.1").

The only message I have when I run cuffmerge is : [bam_header_read] EOF marker is absent. The input is probably truncated. [bam_header_read] invalid BAM binary header (this is not a BAM file).

Do you have a solution for this issue ?

Thank you for your answers !

Last edited by JoannaF; 07-28-2017 at 01:50 AM.
JoannaF 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 03:47 AM.


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