Wed, May 17
Oct 29 2022
Deleted branch from rMPT MITK-ProjectTemplate: release/T29138-v2022.10.
Pushed new branch to rMPT MITK-ProjectTemplate: release/T29138-v2022.10.
Aug 15 2022
Jun 7 2022
Deleted branch from rMITK MITK: bugfix/T28274-volumerendering-multiple-timesteps.
Apr 29 2022
Deleted branch from rMPT MITK-ProjectTemplate: release/T29138-v2022.04.
Deleted branch from rMITK MITK: release/T29138-v2022.04.
for now we solved it by adding the support in the mapping helper as outlined above. Some sophisticated like services we did not so far.
Apr 27 2022
Thank you for spotting that. It is not expected behavior. But I would keep as is (known issue). 1) I think it is acceptable and 2) to handle this properly and not hacky, would be very intrusive and take 1 day. I would prefer to do it when the AutoTool classes will be merged and refined anyways, then it is an quite easy catch.
@kislinsk What do you think?
I was able to reproduce the problem on the snapshot from two days ago. This new version fixes the problem for me, although the behavior is the same as @kalali described it. The newly created segmentation is a complete copy of the current one (including layers, labels, and masked regions of the labels), except for the changed region that was just segmented. I'm not sure if this is the expected behavior, but if it is everything seems to work fine.
I cannot reproduce the crash with the related branch!
Pushed new branch to rMITK MITK: bugfix/T29143-Crash_when_storing_auto_tool_preview_in_new_seg.
Apr 26 2022
damn I know the reason. At least I have made a telling exception. 😅
I updated the Checklist "Volume Visualization_EN.docx" accordingly.
Pushed new branch to rMPT MITK-ProjectTemplate: release/T29138-v2022.04.
Pushed new branch to rMITK MITK: release/T29138-v2022.04.
Apr 25 2022
@a178n Maybe we need to add the hint that an additional tool icon is available for nnUNet for non-windows user?
We found a solution to make the highlighting consistent with the active label state.
Apr 24 2022
This task is resolved in the current release branch.
Apr 21 2022
I updated the image and removed the numbers (like Stefan proposed in his comment).
We updated the checklists.
I added a fix for this by using the same approach as in the segmentation view.
However, the reason for this class is unclear to me: It is only used for the data manager context menu and allows to quickly create a new, empty segmentation child node. It's basically the same as clicking the button in the segmentation view so for me it doesn't add anything and could be removed.