For command-specific error messages, see the command’s doc page.
If you run into any other errors or exceptions not listed, or have any issues with the existing errors, please head over to our GitHub Issues for assistance!
The command line option provided only accepts
false as input.
Chained commands take the output of the last command as the input of the next. Because of this,
--input should only be used with the first command in the chain. This excludes merge and unmerge, which allow multiple inputs.
When specifying the
--format for converting), make sure the file has a valid extension. See convert for a current list of ontology formats.
Many commands involve creating IRIs from provided string representations of the CURIE or full IRI. If the provided field is not a string in valid CURIE or IRI format, the actual IRI cannot be created.
When using CURIEs, make sure the prefix is defined, or add it with
Prefixes (added with
--prefix) should be strings in the following format:
"foo: http://foo/bar#". See Prefixes for more details on adding prefixes.
Reason, materialize, and reduce all expect
--reasoner options. All three commands support
elk. Only the reason command supports
emr. Click on the command for more details
A valid command must be provided, running just
robot will not perform any action.
Some commands require certain options to be present. See the documentation for the specific command.
Each command requires a set of options, although it is more common to get a
MISSING INPUT ERROR. See the command-specific documentation for more details.
This error message may appear for one of two common reasons:
A command or option (the argument) was typed incorrectly, or it not exist.
Multiple arguments have been provided to an option that only accepts one argument. For example, the
--term option for extract only accepts one argument. The following would not work:
$ robot extract --input foo.owl --term foo:0000001 foo:0000002 UNKNOWN ARG ERROR unknown command or option: foo:0000002
Instead, use this (or a
robot extract --input foo.owl --term foo:0000001 --term foo:0000002
Currently, ROBOT can only annotate subClassOf axioms.
See GitHub issue #67 for more details.
For commands that take input terms, ROBOT will check the ontology to ensure those terms exist before proceeding. If the terms do not exist, then there are no tasks to complete so an error message is returned.
If at least one term exists in the ontology, the task can still proceed, but the results may not be as expected. If you run into problems, run these types of commands with the
--verbose flag, as warnings will be issued when the ontology does not contain a term.