Skip to content
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

Open
slicerbot opened this issue Mar 13, 2020 · 5 comments
Open

display current "auto-run" modules in one place #3653

slicerbot opened this issue Mar 13, 2020 · 5 comments
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@lassoan lassoan added this to the Backlog milestone Mar 16, 2020
@lassoan lassoan removed the backlog label Mar 16, 2020
@jamesobutler
Copy link
Contributor

Per Ron's request: Display in current "auto-run" modules in one place, Ron suggested the Data Probe

I think I’m too new to understand this terminology of “auto-run” modules. Does anyone else know what this means?

@jamesobutler
Copy link
Contributor

@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?

@jcfr
Copy link
Member

jcfr commented Nov 15, 2022

[...] terminology of “auto-run” modules. Does anyone else know what this means?

I think this is related to https://www.kitware.com/slicer-cli-autorun/

@jamesobutler
Copy link
Contributor

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.

@lassoan
Copy link
Contributor

lassoan commented Nov 15, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants