-
Notifications
You must be signed in to change notification settings - Fork 41
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
Wiki: syntax of commands #286
Comments
Good catch! I removed the equals signs from the Commands page. This way the syntax matches what
|
As an aside, I'm not very happy with the current Commands page. It was originally a spec document for what the commands should be when they were to be implemented... Now it's not 100% up to date w.r.t. the implementation. Maybe it would make sense to either delete it completely, or to generate it from the |
You could generate it from the help messages but what helps me a lot are at least some minimal additional comments about an optimal usage of those commands or rather of the functionalities behind them -- much like in "Achieving good results". On the other hand, of course that means that you will still have to update the page by hand. Anyway, I would not delete it completely -- I have referred to that page quite often and I am not always in our virtual machine, so if the page were deleted I would have to log in first in order to take a quick look, that would be less practical. |
Thanks for your thoughts. I think it would be best to keep the Commands page, but make it more like a Unix man page. So an overview of the available CLI commands and their parameters, but with some guidance on how best to use them. I think a lot of that guidance should be placed in the Please note that wiki pages are editable by anyone, so if you see a mistake or an omission and are confident that you know how to fix it, you can just do it without asking. |
Maybe for less expert Linux users:
In "Commands" commands are given like this:
annif eval [--limit=MAX] [--threshold=THRESHOLD] [ ...]
but in "Achieving good results" there is an example
annif eval tfidf-en --limit 5 --threshold 0.2 path/to/corpus/validate/
(--limit=n vs. --limit n).
Maybe only use the syntax with '=' and remark that the syntax with blank is equivalent or the other way round?
The text was updated successfully, but these errors were encountered: