@fedorov Thank you for your quick reply and verification for my assumption (I hoped, that I might have overlooked some broader interpretablility...)

" increase monotonically by 1" could be interpreted as "no holes allowed". We should clarify if this is the case.

from @neher : clscreenshot sounds like something that might be useful, but i never used it

So far only CLGlobalImageFeatures is claimed to be needed.

Fabian has reported than nnUNet(v2) python codebase can run to Windows.

Valid. Will be /is regarded in the refactoring.

Code test and patched for 2D image support.

I am not sure what happens when 2D 3 channel is loaded for segmentation. Never tested the behaviour of the SegWithPreviewTool API. From my side, I need to update the wrapper to accommodate for 3 channel images. Of course, it's a straightforward change but at the moment, 3-channel won't work.

In T29650#248947, @gaoh wrote:

@k656s has an example dataset. I am still at the release version before (I think 2022.10?) but I will update to the current release. Could this already help?

Yes, it could. I thought something like this was already introduced. @kislinsk, or?

what is the problem here/where do you lose the other channels? shouldn't it work out of the box already?

@k656s has an example dataset. I am still at the release version before (I think 2022.10?) but I will update to the current release. Could this already help?
If not, I would vote for the task list view reinit after loading opiton.

@gaoh do you have example data to reproduce this situation. That would help to replicate it and search for the best solution.
Which version of MITK was it?

there is a DerivePointerAlignment option which basically unifies it on a file by file basis, in case there is no agreement. But I agree to Ralf with using the "left" style and put it next to the type

That is a first shorted list. Other apps and plugins are already ruled out (e.g. due to Vigra dependency). We no shuold assess which of those can really stay in the main mitk repo.

It's a feature.

One way of documenting the applied fitting pipeline in agreement with the lexicon is to export an XML file which describes the pipeline as suggested int the lexicon publication ("A community-endorsed open-source lexicon for contrast-agent based perfusion MRI (CAPLEX): A consensus guidelines report from the ISMRM Open Science Initiative for Perfusion Imaging (OSIPI)".)
In this task it is first collected if all relevant information of the fitting configuration can be extracted in order to build such an XML file.

Didn't find any "critical" style issues. It is a single commit, right? rMITKc8283d2c7c3f: Smaller Bugfixes
You may want to search and replace "[Bb]oarder" with "[Bb]order", though, as I guess you intended to refer to "Rand" instead of "Untermieter". :)

@gaoh gave green light in Slack to delete the branch during a housekeeping effort.

Deleted branch from rMITK MITK: feature/T27189-RestApiForDataStorage.

Deleted branch from rMITK MITK: bugfix/T28544-difference-RT-data-loading.

I reeopened because I would like to llok into the feature branch at least and see what might be of interest:

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

@floca wants to resolve these crashes differently. Handing over...

Request for Discussion:

• Notify tools about selected label changes or label property changes like color?
• Show preview as active or inactive label (with or without border)?

grow cut (as all preview tools) does not generate any undo point right now. What you witness is the undo of your seed painting up front.

I am not sure I would put it a member function. This can be done without the need of accessing any internals.

We should discuss if it is still worth it to get it back online after all this time and with the new tools.

We should discuss if we realy try to get region growing back online with all the other tools ...

I pushed my local branch to remote for others to continue working on it. The related differential {D594} has been updated and will remain open.

Pushed new branch to rMITK MITK: feature/T26959-Show-outline-of-labelsetimage.

Not sure if we need a CMake option for it, as long as it works in all scenarios. :)

Checked to add

It was discussed and agreed upon, that it does not make sense to adapt this behavior in the Data Manager. If we want a clean implementation of the "set focus on planar figure"-feature, it should belong in the corresponding view (i.e. Measurement) instead of the Data Manager.
As this is not currently a specifically requested feature, this task will be closed.

@a178n will close this task and create a new dedicated task.

It was discussed that the old reader information is not of any value and shouldn't be written into the files.

if I not mistaken this is something different, because scene serialization uses as different mechanism (it always stores all props of data and nodes; no matter what). Property persistence service is only relevant for reading or writing data to "directly" to files.

In T29504#246386, @kalali wrote:

This is not solved with {D795}, right? I can still see slicer->GetRenderer() in line 926, so the render window is still retrieved from the slice navigation controller, which requires the getter to be available in the slice navigation controller.

This is not solved with {D795}, right? I can still see slicer->GetRenderer() in line 926, so the render window is still retrieved from the slice navigation controller, which requires the getter to be available in the slice navigation controller.

Wait, maybe we are talking about the same thing. In mitkSegmentationTaskListIO.cpp:181-184 the written properties are used in case everything is read from a scene file. Then, the original input location is read as search path for relative data that isn't contained within the scene file. Which I know is not a perfect situation in the first place but better than nothing in particular for users using the save button to checkpoint their progress.

You're right. I already suspected it to be different things but better safe than sorry. :D

In T29521#246322, @kislinsk wrote:

Input location is used by the SegmentationTaskList and SegmentationTaskListIO.

Input location is used by the SegmentationTaskList and SegmentationTaskListIO.

After looking at the checklist again, I don't think there is a need to change anything. The checklist specifically only speaks of selecting the line-node once. When following the checklist instructions, everything should work as described.