You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a use case is defined with a config file. If users would like to create multiple tasks (eg: segmentation of brain MS lesions, segmentation of brain tumors, etc.) it would be nice for the user to be able to generate multiple config files and then select the desired one from the Slicer module.
This would probably require changing the module name in the CMake file, python filename (and script), and .ui file (unless there is a way to do this directly in the extension wizard) -
The text was updated successfully, but these errors were encountered:
This is now supported. The configuration files are saved in the output folder. Therefore, a user is able to continue working on multiple projects by simply selecting one of the project's output folder and the correct configurations will be applied to the extension. In addition, this output folder can be shared between members of a same team for collaboration and/or revision.
I have made some videos describing the new configuration GUI, here is the link!
Suggestion from @laurentletg
Currently, a use case is defined with a config file. If users would like to create multiple tasks (eg: segmentation of brain MS lesions, segmentation of brain tumors, etc.) it would be nice for the user to be able to generate multiple config files and then select the desired one from the Slicer module.
This would probably require changing the module name in the CMake file, python filename (and script), and .ui file (unless there is a way to do this directly in the extension wizard) -
The text was updated successfully, but these errors were encountered: