Page MenuHomePhabricator

MitkFlowBench Naming Issue
Closed, WontfixPublic

Description

Withing MITKFlowbench there is a variable to define the Output Dir:

--flow.output ...

The name of the Outputfile is the name of the Segmentation file.

image.png (109ร—264 px, 4 KB)

And there is the Problem:
When selecting a "normal" Name e.g. "segmentation" on "Accept segmentation" the file is correctly stored.
When selecting a name with e.g. spaces (default suggested segmentation name), MITK tries to store the file for example here:

Writing image: D:\Projekte\MITK_dev\bin\MITK-build\bin\Private^000001_BPL_Abdomen_Winfried (Adult) \ Abdomen BPL  5.0  B40f-labels.dcm

And Now the GUI just tells me "Segmentation stored!" but there is no segmentation in the folder. The reason should be the naming of the file...

Event Timeline

so maybe a Regex is needed, or just a default file name..

It is the "\" in the node name.

Either we generate own names or we have to sanitize the node names before using them as file names (to avoid illegal characters).
What does make more sense in a typical usage scenario? Both is possible.

In case of kaapana, the name is currently irrelevant: directly in the next operator, the dcm files are send to the PACs anyway and then the file is deleted.
What would make sense, regading the naming in the PACs and when downloading files, would be to give it the name of the Instance UID.

In T28311#220415, @gaoh wrote:

would be to give it the name of the Instance UID.

Understood, but thats not that easy yet, as the Instance UID is currently generated by DCMQI in the writing process. But that is something we should alter somewhen anyways, as we already need this UID within MITK.
So I guess we take one of the other choices as mitigation strategy.

kislinsk triaged this task as Normal priority.Feb 18 2021, 9:36 PM
kislinsk added a project: Auto-closed.
kislinsk added a subscriber: kislinsk.

Hi there! ๐Ÿ™‚

This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. ๐Ÿš‘

Best wishes,
The MITK devs