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
From what I understand, the goal of this package is to create a slicer module to easily segment pathologies/anatomies on medical images (CT, MRI and more ?).
However, when I look at the code, it seems to rely heavily on multiple configuration files (.yml) that are not completely intuitive and its hard to know to what extent these configuration files are customizable:
Do we want to allow the user to create/add buttons or short cuts only by modifying the configuration files ? If so, how to do it ? What are the limitations ?
Do we want to provide the user with determined configuration files that correspond to different workflows ? (e.g. MRI lesion segmentation and classification, MRI rootlets segmentation, CT edema segmentation...)
Why do we have that many configuration files ? Can't we regroup ?
I personally think that these questions need to have a precise answer to clarify the direction of the project. I'm no expert with slicer but currently all the possibilities feel really overwhelming.
The text was updated successfully, but these errors were encountered:
From what I understand, the goal of this package is to create a slicer module to easily segment pathologies/anatomies on medical images (CT, MRI and more ?).
However, when I look at the code, it seems to rely heavily on multiple configuration files (.yml) that are not completely intuitive and its hard to know to what extent these configuration files are customizable:
So what I don't get is this:
I personally think that these questions need to have a precise answer to clarify the direction of the project. I'm no expert with slicer but currently all the possibilities feel really overwhelming.
The text was updated successfully, but these errors were encountered: