- User Since
- Oct 13 2017, 9:09 AM (311 w, 6 h)
Mar 10 2023
Jul 20 2022
The feature/T27923-execute-python-code-in-mitk branch should be outdated as the last commit was in 2020. Everything from this work should be integrated in this commit where I pushed all the work from my bachelor thesis on the python-dev branch and based on this, implemented some more features.
The main problems of getting green builds were on the Ubuntu clients where some errors occurred during the build that we were not able to reproduce locally.
Jun 14 2022
Mar 29 2022
Regarding the comment of closing the contour with a double click: I also realized this during my work on the new add tool and I think the way I fixed it was to modify the OnFinish() function in the mitkLiveWireTool2D to check whether the click was performed on the first point which was also how it was done before the closure contour was added to the LiveWire tool.
Here is the code of my new add tool branch where I changed it:
Mar 8 2022
Feb 16 2022
Feb 14 2022
No I am not actively working on this issue. I proposed a change but as written in the comments, this broke some rendering test.
We did not investigate closer why this happened. So I reverted the change and currently the initial task is still not fixed.
Feb 4 2022
Feb 2 2022
Feb 1 2022
Jan 17 2022
Nov 30 2021
Nov 24 2021
I implemented a fix which includes your suggestion to extend the interfaces of the TranferFunctionWidget and QmitkTransferFunctionGeneratorWidget @floca. This resolves the issue that the histogram is not updated. Additionally, to also update the volume that is shown in the 3D render window, I extended the mitkVolumeMapperVtkSmart3D to also work with the correct timesteps. Before this change, only a volume for timestep 0 was created. With this fix, the workbench also does not crash with the Heart3D+t dataset.
Nov 22 2021
I tried to reproduce this bug and for US4DCyl the behaviour was the same when I tested it (histogram remains the same for all timesteps). For Heart3D+t sometimes nothing is displayed at all (as described here) but also sometimes the workbench crashes as described in T24754. However, I could not find any pattern when which behaviour occurs. I tested it with the current release installer on Windows and on the current develop branch in Debug mode. I can try to narrow it down a bit.
Nov 18 2021
Nov 16 2021
Nov 15 2021
Nov 4 2021
I also looked into this task yesterday and the issue is that for custom background values, the "AccessByItk_n" function is used, which only works for 2D and 3D images. A potential fix would be to use the "AccessFixedDimensionByItk_n" function for the 4D case, then the Workbench does not crash anymore. So in the QmitkImageMaskingWidget.cpp one could replace
Nov 2 2021
After a first look on this problem, I found out that the issue occurs because of the different dimensions between the image and the segmentation. The image is in 2D and the segmentation mask that is created is in 3D.
This can be seen when taking a normal 2D image or when working with Pic2DplusT.nrrd and creating a static segmentation mask. However, when working with Pic2DplusT and creating a dynamic segmentation mask, the Workbench does not crash (because it is 3 dimensional with time again).
Oct 20 2021
Oct 18 2021
Sep 30 2021
This function is also available in the preferences (Ctrl+P). There, just select "Draw as transparent overlay" (see image below).
Apr 28 2021
Deleted branch from rMITK MITK: bugfix/T28437-RegionGrowing3DSeedPoint0.
Apr 23 2021
Apr 15 2021
Jan 27 2021
Nov 17 2020
Deleted branch feature/T27564-integrate-deeplearning-segmentation-V2.
Deleted branch feature/T27564-integrate-deeplearning-segmentation-evaluation.
Deleted branch feature/T27564-integrate-deeplearning-segmentation.
Deleted branch feature/T27500-use-PythonCApi-in-python-service-V2.
Deleted branch feature/T27500-use-PythonCApi-in-python-service.
Nov 5 2020
Nov 4 2020
Pushed new branch feature/T27923-python-dev.
Nov 3 2020
Pushed new branch feature/T27923-execute-python-code-in-mitk.
Aug 10 2020
Pushed new branch feature/T27564-integrate-deeplearning-segmentation-evaluation.
Jul 31 2020
Pushed new branch feature/T27500-use-PythonCApi-in-python-service-V2.
Jul 30 2020
Jul 29 2020
Seems like I figured it out. What I had to do was to change SWIG_TypeQuery("_p_mitk__Image") to SWIG_TypeQuery("_p_itk__SmartPointerT_mitk__Image_t") and change the type of image to mitk::Image::Pointer *image. When passing Pic3D now and printing the number of dimensions, 3 is printed as one would expect. I will further investigate how to interact with other libraries like SimpleITK.
I tried an approach like @floca suggested with the SWIG wrapping that is already available in MITK. Here is my code to transfer a MITK image from C++ to Python:
Jul 28 2020
If you use Python 3.7/3.8, you need to install SWIG version 4.0.2. This solves the problem. Currently, SWIG version 3.0.2. is installed in the Superbuild.
Jul 24 2020
Jul 21 2020
Pushed new branch feature/T27564-integrate-deeplearning-segmentation-V2.
Jul 16 2020
Pushed new branch feature/T27564-integrate-deeplearning-segmentation.
Jul 15 2020
Jul 8 2020
@kalali I can confirm that there is no option to use autocrop when using the ITK NrrdImageIO reader. However, when you load an image with the ITK reader (I used MultiLabel/Pic3DAsMultilabelImage.nrrd as well) and you convert it to a segmentation
(Right click ->Convert to segmentation) and then autocrop the new segmentation node, the name also changes to "No Name". So it might be a general problem when autocropping.
As the bug couldn't be reproduced, it can be closed.
Jul 6 2020
Jul 2 2020
I couldn't reproduce it myself and to be honest, I don't know which picture I took when the bug occured. @thomass Do you still know more about this bug? I think we encountered it when we were testing with the Checklists.
Jun 29 2020
Pushed new branch feature/T27500-use-PythonCApi-in-python-service.