- User Since
- Aug 1 2016, 12:10 PM (192 w, 1 d)
Fri, Apr 3
Ok, this can be a different task. I will fix the authors corresponding to the paper in this task.
This issue will be fixed in v0.3.2.
Thu, Apr 2
At the meeting on 30/03/2020 we agreed that the messages should be extended to warn the user of that scenario. Since the column containing the tasks is unknown when the parameter "by" is not specified, an automatic detection can only be realized with a lot of effort.
In the meeting on 30/03/2020 we agreed that this issue won't be fixed. Cases can appear more than once per algorithm in bootstrapping and thus the sanity check has to be turned off. Performance reasons were also mentioned.
In the meeting on 30/03/2020 we agreed that this issue won't be fixed. Parameters have to be described properly to raise awareness of this scenario to the user.
Wed, Apr 1
Tue, Mar 31
The given example is already available as a unit test.
Mon, Mar 30
Fri, Mar 27
Another workaround is to configure the environment variable for your executable in Visual Studio. To do so, first select Properties from MitkWorkbench context menu. In the Property Pages dialog, select Configuration Properties → Debugging. Copy the value of the variable 'Environment'. Paste it in the 'Environment' field of the respective executable.
Pushed new branch T27003-Integration.
Seems that the pixel type is not set properly:
Show details lists "Channel: Unnamed [scalar], PixelType: scalar" for the nrrd file and "Channel: Unnamed , PixelType: " for the DICOM file.
This issue still occurs. Following previous finding still holds true: Volume visualization works for the image if it is exported to nrrd first and then loaded as nrrd.
Thu, Mar 26
Wed, Mar 25
Tue, Mar 24
Mon, Mar 23
Thu, Mar 19
Make the task visible in the workboard column "Done".
Tue, Mar 17
Feb 13 2020
Can this be contributed to the master as is?