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
Sometimes ORFtrack generates empty lines in the output GFF file and thus stop with an error when parsing the output GFF to build the summary.
To reproduce the behavior juste use the defaut options with the attached files (with txt extension to be uploadable on github). gff.txt fasta.txt
The text was updated successfully, but these errors were encountered:
Plus if you run the same command but with the co_ovp 0.05 option, it generates a additional line containning only ' |"gag_cds" ' which should be at the end of the previous line.
Hi Paul,
I have pushed a temporary patch on the main branch to fix that issue. I've just add a strip() method on the gffline string that is generated for each orf to prevent the presence of an extra '\n' causing empty lines and parsing error during the summary process. I qualifiy this patch as "temporary" because I don't know yet where this extra '`n' comes from...
Sometimes ORFtrack generates empty lines in the output GFF file and thus stop with an error when parsing the output GFF to build the summary.
To reproduce the behavior juste use the defaut options with the attached files (with txt extension to be uploadable on github).
gff.txt
fasta.txt
The text was updated successfully, but these errors were encountered: