You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After running Isoseq/Pigeon pipeline, all of my transcripts are annotated as non_coding in the _classification.txt output (as well as the filtered classification output). This happens even for protein-coding genes...
To Reproduce
Following the CLI example per the docs, using Gencode v39. Relevant code (after demuxing) below:
Expected behavior
I should get many coding transcripts and annotated ORFs! I am not sure what step is causing the issue. Let me know and I'd be happy to provide some files to reproduce, but not sure where to start...
The text was updated successfully, but these errors were encountered:
Hi, just pinging this issue and adding a bit more context -- it looks like in the previous iterations where I've run this pipeline, SQANTI3 produced the output gtf file with CDS information (corrected.gtf.cds.gff), but the same isn't happening with pigeon classify. Any ideas? Do I have to use SQANTI3 directly to get CDS information?
Hi @kmattioli thx for using pigeon! SQANTI3 (the academic version pigeon is based off) including GENEMARK for ORF prediction which is not included in pigeon, therefore, when running pigeon, all transcripts will be marked as noncoding since this information is not given.
Operating system
Package name
Conda environment
Describe the bug
After running Isoseq/Pigeon pipeline, all of my transcripts are annotated as
non_coding
in the_classification.txt
output (as well as the filtered classification output). This happens even for protein-coding genes...To Reproduce
Following the CLI example per the docs, using Gencode v39. Relevant code (after demuxing) below:
Expected behavior
I should get many coding transcripts and annotated ORFs! I am not sure what step is causing the issue. Let me know and I'd be happy to provide some files to reproduce, but not sure where to start...
The text was updated successfully, but these errors were encountered: