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
display current "auto-run" modules in one place #3653
Comments
I think I’m too new to understand this terminology of “auto-run” modules. Does anyone else know what this means? |
@lassoan are “auto-run” modules ones that start observations of scene nodes? Do you know an example of one of these that was being referred to? |
I think this is related to https://www.kitware.com/slicer-cli-autorun/ |
Ah I see. Do people still use this type of workflow? I tried searching for “AutoRun” in the documentation at https://slicer.readthedocs.io/en/latest/ but couldn’t find anything. |
Aurorun is quite useful when a CLI is fast enough that it can update its output within a few seconds. Then you can find good parameter values much more quickly because you just adjust the slider (no need to click Apply). I also enable Aurorun when I don't want the output to reset the slice views (disabling showing of output image is a useful side-effect). The really big promise of auto-run was that you could set up entire processing workflows from a combination of CLI modules. But probably it was too complicated for users and CLI modules could not do everything, so this feature has not been ended up being used much. |
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The text was updated successfully, but these errors were encountered: