- User Since
- Aug 1 2016, 12:10 PM (254 w, 4 d)
Thu, Jun 17
As discussed with @s434n, I will discard my diff D466 for now, because it caused some unwanted interactions with the LayoutAnnotationRenderer. The quick fix of D506 solves the problem that in Geldosimetry and OverlayManager the colorbarAnnotation is not displayed in the right center (placed too heigh and is cutoff in the render window).
Wed, Jun 2
I am indeed still reading since I still have tasks to do (I will not leave beforehand just as promised :-)). I think you are referring to T28383 / D477 ... maybe it didn’t fully do the trick.
Apr 27 2021
The task as such is resolved. Another task with open questions from D279 is created with T28466
Apr 22 2021
Could be solved by @kislinsk suggestion to change rendering mode to LOOKUPTABLE_COLOR to not envoke the levelwindow to overwrite the range
Apr 15 2021
Apr 14 2021
Unassign myself because we removed the clipping plane from the release and have not discussed yet how to further proceed.
The first user feedback of the patch above was positive, the users liked the behavior.
However, the patch did not work correctly in terms of modifying the points afterwards (users were warned before).
Apr 11 2021
Mar 31 2021
First patch to change following behavior (for user testing only):
- The linesegments are added with each mouseclick of the users without the cost function but by connecting start and endpoint
- If the user double-clicks on the image, the last point is connected with the first adding an additional segment.
Mar 25 2021
Mar 19 2021
Mar 18 2021
On a first glance, the interpolation seems to affect the result.
- Create the segmentation with interpolation -> save it -> reload segmentation -> erosion = no crash
- Create the segmentation with interpolation -> erosion = crash
The issue can indeed be solved by a mitk::RenderingManager::GetInstance()->RequestUpdateAll(); in QmitkLabelsetWidget function OnVisibleButtonClicked() but there seems to be something wrong with the lock logic when "Lock All" "Unlock All" is clicked
Mar 17 2021
Mar 2 2021
Since you also mentioned different editors: Not sure if this is also related but one of the terminal outputs of the testers was:
Mar 1 2021
With the modelfit inspector it most often crashed, if the user clicked on a datanode in the datastorage
Feb 18 2021
Feb 10 2021
Feb 4 2021
Probably it would just help to replace the MITK Error by a warning? This is also done when there is no point set at all.
I couldn't reproduce this bug in the latest Release installer on Windows. However, there is no volume visualization shown at all (no matter which timestep or which histogram I select).
If the crash does not occur anymore on Ubuntu etc. we can resolve the crash bug.
Most likely something for the next release IMO, but please decide @kislinsk :)
Feb 2 2021
Since the default colormaps are overwritten by the levelwindow I added a Boolean property to give the user a possibility to prevent the custom colormap from being overwritten
Jan 29 2021
Sorry this was already mentioned in T27507. But I think we never discussed / decided what the purpose of picking on 4D tools should be. But not necessarily important for the release though.
Watershed tool also has very weird rendering flickers, whenever there is more than one image visible in the 2D view. Whenever the rendering bug is solved, the segmentation tools should be checked again.
IMO not severe for the upcoming release since Otsu is not often used and it is not a show stopper...
Since you are already working on the histogram anyways, can you check the following:
Jan 27 2021
probably related to T28206
However, checking "Show Subchart" always invokes an update and then you can see it
Jan 4 2021
The scene is created successfully if following (deprecated) properties are disabled in mitkDICOMImageBlockDescriptor.cpp:
Dec 16 2020
as name property, the name of the RT node is provided correctly.
I created a working example with Pic3D for comparison.
Looking at both caaaaa.xml files, the only difference I notice is that the corrupted one is encoded with UTF-8 but otherwise it looks similar (as far as I see).
<?xml version="1.0" encoding="UTF-8"?>
<Version Writer="C:\Development\MITK-dev\src\Modules\SceneSerialization\src\mitkSceneIO.cpp" Revision="$Revision: 17055 $" FileVersion="1"/>
sorry just saw the message. I put it in the shared folder.
Dec 15 2020
As Ralf pointed out, it is actually not related to the GenericProperty as such but it seems that the scene does not even contain any nrrd files after saving and that is why it breaks
Dec 14 2020
GenericProperty associated to key 'MITK.IO.reader.DICOM.PixelSpacingInterpretation'
GenericProperty associated to key 'MITK.IO.reader.DICOM.ReaderImplementationLevel'
GenericProperty associated to key 'dicomseriesreader.PixelSpacingInterpretation'
GenericProperty associated to key 'dicomseriesreader.ReaderImplementationLevel' still need to be changed
Since solution 1 worked well for me and seems to be more generic, I would vote for 1.
Dec 10 2020
I tried it with my current develop (not the latest due to ongoing QT issues - wip) and it resolves the last warning (predescibed dose) but not the others. According to the D449 this is the one you changed, so as expected I suppose :) As soon as I get the latest develop up and running I will check the diff further.
Dec 8 2020
Might be related to T25305
Nov 25 2020
Nov 24 2020
apparently a vtkLoopUpTable is set automatically so the property as such cannot be used to handle custom vtkLookUpTables
Oct 22 2020
In T26382 the recent developments are summarized.