-
Notifications
You must be signed in to change notification settings - Fork 15
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
added docs for --input_axes #131
Conversation
also reordered the sections a bit, with the new section Input Settings. fixes #117
I had a feeling that was missing from the docs. Awesome! Do you think we should also specify that that is the C-order of the axes, as represented in memory? |
@@ -63,7 +63,10 @@ CPU and RAM resources can be controlled with environment variables or a config f | |||
**Optional input settings:** | |||
|
|||
- `--readonly` Open the project in read-only mode; necessary for using a single project from multiple processes. | |||
- `--input_axes` specify meaning of your axes. In some cases ilastik's default guess for the axes is not correct. In such cases, supply the axes explicitly (e.g. `--input_axes=zcyx` for a 3D dataset with channels and the axes in the "zcyx" order). | |||
- `--input_axes` specify meaning of your axes. In some cases ilastik's default guess for the axes is not correct. | |||
In such cases, supply the axes explicitly (e.g. `--input_axes=zcyx` for a 3D dataset with channels and the axes in the "zcyx" order). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should mention that for stack inputs, --input-axes
refers to the axis order of each slice in the stack?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added!
--input_axes
parameter was undocumented.also reordered the sections a bit, with the new section Input Settings.
fixes #117