-
Notifications
You must be signed in to change notification settings - Fork 76
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
Skip invalid lines when converting out of OBO #1039
Comments
Hmm.. I think this is outside of the scope of ROBOT.. If you want this to happen you have to go through https://github.com/owlcs/owlapi/issues/ or join the |
This exact issue is a problem with the currently released ChEBI OBO file: ebi-chebi/ChEBI#4273 |
Rethinking this now: I could implement a "repair --obo-format" option that deals with the most frequent violations like multiple labels and multiple comments etc.. I would be open to this but it would have to be now! |
Sorry, I now realise I discuss this here: #995 and that this (broken rows) is not possible at all right now without a major OWLAPI update. This needs to be either added as an OWL API ticket, or oboformat.. https://github.com/owlcollab/oboformat/issues I will close this now, as what ROBOT can do about this can be covered by #995 |
The Cellosaurus ontology contains many invalid lines, e.g. the following line has improperly escaped curly braces in the molecule's name:
If you run
robot convert -I https://ftp.expasy.org/databases/cellosaurus/cellosaurus.obo -o ~/Desktop/cellosaurus.json -vvv
and look very carefully for the relevant error (for now, you have to search the output fororg.semanticweb.owlapi.oboformat.OBOFormatOWLAPIParser
- #1038 would be helpful for this), you find that:This ontology doesn't do its curation in an open source way so it's difficult to communicate and help solve this issue. Further, I downloaded the file and started making fixes one at a time, but I have to re-run
robot convert
on every step. It would be nice if there were a setting that allowed for invalid lines to be skipped on OBO parsing.CC @AmosBairoch @lubianat
Update: this is the same underlying issue as ebi-chebi/ChEBI#4273
The text was updated successfully, but these errors were encountered: