-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gt gff3 error #25
Comments
lifted.gff3 is the output of UCSC liftOver tool. Some of the annotations in this file may be incorrect. flo tries to eliminate them and output a clean set to lifted_cleaned.gff3. This last step is failing. In this last step, flo can only process 2-level relationships (transcripts, and its child exon and cds). We thus recommend removing gene annotations before running flo (it's documented in the README file). Alternatively, you can try to remove incorrect annotations yourself from lifted.gff3. |
Hi,
Thanks in advance for your help. |
Yes, that's the expected behavior, i.e., line 64 should be absent from the output. |
Thank you for your reply. I'll remove all lines with "gene" in the third column. |
Can you share a subset of your GFF so I can try to reproduce the issue? |
Sorry for my late reply. I am using this gff file: link I used awk to remove space in the second column and remove gene annotation. Thank you very much for your help. |
Sorry. Never mind. I just realized the GFF file that I was using does not have the correct seqid. I'll used a different GFF file. |
Hi,
I ran flo, and got this error:
warning: line 1 in file "-" does not begin with "##gff-version" or "##gvf-version", create "##gff-version 3" line automatically
gt gff3: error: Parent "maker-Contig53-exonerate_est2genome-gene-0.0" on line 1 in file "-" was not defined (via "ID=")
rake aborted!
Command failed with status (1): [/data/apps/flo/gff_recover.rb run/Medicago...]
/data/apps/flo/Rakefile:60:in
block (2 levels) in <top (required)>' /data/apps/flo/Rakefile:40:in
each'/data/apps/flo/Rakefile:40:in `block in <top (required)>'
Tasks: TOP => default
(See full trace by running task with --trace)
However, I can see the following output: lifted.gff3 and an unlifted.gff3 (both are non-empty). There is also an empty lifted_cleaned.gff. Can you please tell me what's going on?
Happy to send the .gff3 files if needed.
Thanks!
The text was updated successfully, but these errors were encountered: