MITK Workbench XL
MITK Workbench - extra
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 22 2023
Nov 21 2023
I don't see a good way to handle this differently. Discerning if a slice has become obsolete would be very hard, especially since it's in 3D and the slice could be intersected by a segmented slice of a different orientation. The position node remaining does not seem like a problem to me, so I would vote to close as Invalid or Wontfix.
Nov 20 2023
Nov 17 2023
Nov 16 2023
Nov 15 2023
Can reproduce. I agree with your explanation. When group 1 is empty, it can't actually be selected. There's the dotted line, but group 2 is still in focus (which is stated in the popup dialog). I guess after group 2 is deleted the "focus" is not set correctly.
I guess we could either ensure that the next available label is automatically selected, since usually there is always a label selected, or the "Delete group" should be respective to the dotted-line selection of a group.
I'm not sure if this contradicts previous discussions we had about the topic, but I would actually prefer the second option. Generally, it feels weird that one is able to kind of select a group and interact with its context menu, but the buttons above still refer to the group of the focused label. For example, it is impossible to add a label to an empty group with the buttons (except for the first one).
Nov 14 2023
Nov 13 2023
Nov 8 2023
Nov 7 2023
Nov 2 2023
Oct 31 2023
Oct 30 2023
Oct 26 2023
Oct 20 2023
Oct 19 2023
Oct 18 2023
Oct 12 2023
I looked shortly into this, but couldn't find an easy way to solve it. The problem is that for the desired behavior, one needs to capture not only events of the utility widget itself, but also of all its child widgets.
Oct 11 2023
Sep 7 2023
- Boolean Operations
- chosen: high effort
- Can be used so that the other functions can do everything
- Work only on one image, select two labels
- Contour to Image & Surface to Image
- chosen: low effort seems more senseful. The functionality can be achieved via other tools (e.g. boolean)
- Image Masking
- chosen: low effort
- Morphological Operations
- as proposed
- Pick an image & pick a label
- Include options like in picking tool, i.e. generate a new layer when doing an operation, lock labels (to make sure other labels are not overwritten e.g. for a dilution)
- Add a new tool: Transfer Label could be used to transfer a label from one image to another (if the same image is selected twice, it's just a rename)
Aug 31 2023
Aug 29 2023
I tested this again with the current version of MITK (develop branch) and can see no problems. Interpolation works without problems on my laptop (Windows 10, 32GB RAM)
Aug 24 2023
Aug 9 2023
We want to have:
- a slick minimum Workbench version
- a fuller / bigger version. Exact contents and name still need to be compiled (e.g. Perfusion, Fitting, ...)
Aug 1 2023
Jul 26 2023
With the addition of the polygon tool, this is now possible.
Jul 25 2023
Jul 17 2023
Jul 14 2023
I think the handling of multiple labels depends on each action and needs to be handled separately.
- Boolean Operations: I see a few options here
- low effort: only allow for segmentations with one label. If there is more than one label, show a message that this is not possible
- higher effort: completely rework the selection. Let the user select two specific labels (from the same or different segmentations) and work on these, either replacing the first label or adding a new label (or instance) to that segmentation
- Contour to Image & Surface to Image:
- low effort: leave it as is, still works at the moment
- higher effort: introduce the option to add the newly created segmentation as a new label / instance to an existing segmentation
- Image Masking:
- low effort: leave it as is, still works at the moment (using all labels of a segmentation)
- higher effort: introduce the option to select which labels/instances should be considered for masking
- Morphological Operations: Currently don't crash, but always use label 1
- I think the most senseful solution would be to let the user select a specific label for the operation to work on. Multiple at the same time probably only get in each other's way and make it unnecessarily complicated.