corrected.genePred -genePredExt -allErrors -ignoreGroupsWithoutExons' returned non-zero exit status 255.
Xingliang888 opened this issue · 6 comments
Hi.
I degbug the squanti3 for one whole week, trying to run this program, but many many bugs are emerging sequentially, it seems I can never dissolve them.
I am trying from the samplest one,
python /SQANTI3/SQANTI3/sqanti3_qc.py --fasta 1.output.fastq --force_id_ignore /ref/ensembl/GTF/Mus_musculus.GRCm39.105.gtf =/ref/minimap_mm10/Mus_musculus.GRCm39.dna.toplevel.fa --cpus 30 -d 1.squanti --skipORF
or
python /SQANTI3/SQANTI3/sqanti3_qc.py 1.eb.all.transcripts.gtf --force_id_ignore /ref/ensembl/GTF/Mus_musculus.GRCm39.105.gtf /ref/minimap_mm10/Mus_musculus.GRCm39.dna.toplevel.fa --cpus 30 --report both -d 1.squanti --skipORF
but met the error:
Command '/SQANTI3/SQANTI3/utilities/gtfToGenePred /nanopore/squanti/1.squanti/1.eb.all.transcripts_corrected.gtf transcripts_corrected.genePred -genePredExt -allErrors -ignoreGroupsWithoutExons' returned non-zero exit status 255.
Anyone has ever met this new problem? Thank you
Hi @Xingliang888,
Thanks for using SQANTI3! Did you try running SQANTI3 with the example files of the tutorial to check if this is a sqanti issue? (https://github.com/ConesaLab/SQANTI3/wiki/Running-SQANTI3-Quality-Control )
The error you copied looks like it's a formatting error in your input GTF.
Best wishes,
Carolina.
Hi, Carolina,
Good morning,
I nearly gave up it. Thank you for your response.
The example runs well. But my files did not.
My input GTF are from stringtie, which is including the novel transcripts. The GTF file formats are shown in attached.
Should I do something about the GTF files?
Thank you.
Xingliang
Probably your GTF has a strand error, as reported before in other issues (#56 ). You need to filter your GTF so column 7 only contains "+" or "-".
Best,
Carolina.
Probably your GTF has a strand error, as reported before in other issues (#56 ). You need to filter your GTF so column 7 only contains "+" or "-".
Best, Carolina.
Yes, exactly. The problem has been fixed by remove "." lines. Thank you.
Awesome! Thanks!