Closed KristinaGagalova closed 3 years ago
I know what the issue is: Imy input files do not have the "u" flag. How exactly do you generate the gtf files to use in cuffcompare/cuffmerge?
Hi Kristina, Typically we encourage users to use cuffmerge to generate the final GTF that is going into Evolinc. If you have multiple GTFs, then you can use the "merge_multiple_gtfs" shell script in our accessory scripts. Are you analyzing RNA-seq data or are you running this from a genome annotation prediction pipeline?
Hi Andrew, I am running the pipeline on my genome annotation (reference) using RNA-seq data that I included as evidence. This is the way I figure out (let me know if there is something wrong with that):
This looks good Kristina. Let me know if you still have issues after running this pipeline. FYI, the sister workflow, RMTA, can help resolve many of the common issues getting prerequisites in the right format.
Regarding the AOT/SOT transcripts, we pull them out for a few reasons 1) lack of strandedness support in the RNA-seq data itself, 2) how often antisense transcripts perfectly overlap (in the antisense direction) with the exons of their overlapping protein-coding gene (which often indicates poor strand prediction by the assembly algorithm), and 3) our inability to distinguish sequence conservation of the lncRNA from its overlapping gene.
That doesn't mean that those "lncRNAs" are uninformative or not real - they may be, I just typically have less confidence in them (unless they are coming from IsoSeq or ONT sequencing).
Thank you for the help and the feedback! I have successfully run Evolinc and included the annotation in my pipeline. I am a happy user of the software
Hi, I was able to run Evolinc with the test data but now I am getting an error when using it on braker genome annotations. This is the error message
Looks like it's not able to extract the transcript sequences and run transdecoder correctly? This is the format og my gtf file
Is there anything wrong with that? Thank you in advance