Question: How to back-trace the transcript sequence generated from Stringtie --merge, gffcompare and gffread?
gravatar for Animesh
20 months ago by
Tromsø, Norway
Animesh0 wrote:

I have 40 assembled file (1.gtf, 2.gtf, 3.gtf, .... , 40.gtf) of different tissue/sample of an organism, which was obtained by following new-tuxedo protocol. The Stringtie --merge will merge transcript from all samples (stringtie_merged.gtf) and provide a string_tie_unique_id corresponding to different transcript/exon. Then on running gffcompare, help me to examine how the transcripts (string_tie_unique_id) compare with the reference annotation. But during this process, the information about transcript (string_tie_unique_id) and its respective source .gtf file is lost. So what should i do to backtrace all transcript of string_tie_unique_id, by following this protocol?


Skipping Stringtie --merge, and running gffcompare on all 40 assembled file (1.gtf, 2.gtf, 3.gtf, .... , 40.gtf) generates assemble file (merged.combined.gtf) as well as other file such as .loci, .tracking etc,. These files help me track down all the transcripts of merged.combined.gtf, from which gtf file they have came. Is it okey to use this?

As i have to extract transcript sequence through 'gffread' using merged.gtf file and apply several filtering steps, also have to back-trace the remaining transcript sequence to the original sample .gtf file, i.e., from which tissue the remaining/filtered transcript sequence have came from.

ADD COMMENTlink written 20 months ago by Animesh0
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1653 users visited in the last hour