-
Notifications
You must be signed in to change notification settings - Fork 74
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
Consider making the --output argument more universal (particularly robot export & query) #1222
Comments
@allenbaron I've also been tripped up sometimes by |
@balhoff Oh man. I had no idea. That is definitely more efficient for running multiple queries. I knew you could do multiple updates because it's described in the documentation but I hadn't seen anything about multiple I wonder if the documentation page should be updated to reflect this ability? I'm looking again and can't seem to find anything about it. |
I reread the first part of the |
Learned that this may be unnecessary... probably better to update robot_query() so it's psuedo-vectorized. See ontodev/robot#1222
Would it be possible to add
--output
/-o
as an argument to robot export as an alias for the--export
argument. Most of the other robot commands (report, extract, etc.) use--output
so I invariably try it for robot export and forget that it is not there until I get the error (and then have to look it up).A similar thing happens when I use robot query with the
--query
argument. I often specify the output path with the-o
argument but it is only an accepted input in connection with the--update
argument. It is unusual to me that the--query
argument takes two strings, the path to the query and the path for the output.It seems maybe originally the
-o
option was meant to apply only for ontology output files? The use of-o
in robot report does break that pattern though. I imagine it would be possible to implement these changes without altering the current behavior of the functions. robot query would probably be the hardest to fix.I would offer a fix myself but don't have the bandwidth at this time (and basically no experience with java). This does not need to be high priority since it is primarily an inconvenience.
Thanks!
The text was updated successfully, but these errors were encountered: