Nov 25 2019
Sep 16 2019
Sep 13 2019
Pushed new branch T19683-ShowOnlySelectedNodesSecondLevel.
Sep 6 2019
Yes, unfortunately the current solution only works for first level.
Aug 16 2019
It has been resolved in branch T26630-AccessAugmParams
Aug 2 2019
If you ask for all the nodes from data storage then you get also child nodes in random order. In the previous implementation, visibility of all child nodes of widgets are set to True when the widgets node is reached. Nonetheless, child nodes visibility were afterwards set to False in the outer loop.
Now the loop is only done on nodes in the first level that contain data, therefore crosshair nodes stay always visible.
In Ubuntu 18.04 data storage is accessed in random order therefore the visibility of crosshair was set randomly. Fixed in branch: T19683-ShowOnlySelectedNodesCrosshairVisibility-RandomAccess.
Pushed new branch T19683-ShowOnlySelectedNodesCrosshairVisibility-RandomAccess.
Jun 3 2019
Through merge conflicts.. The baserenderer argument was added in the master.
Which 2 actions?
May 29 2019
I merged it, we only pushed the branch
May 13 2019
I couldn't reproduce it. @kleina Can you? (maybe it occurred only due to missing reinit?)
May 10 2019
Pushed new branch T25871-fix-unsigned-int-comparison-warning.
Pushed new branch T19683-ShowOnlySelectedNodesCrosshairVisibilty-baseRenderer.
We reverted the changes according to your concerns. Instead of creating a new ImageStatisticsObject in the GetStatisticsForTimeStep method, we now check whether the time step exists before calling the method. That fixed the problem. Statistics are now only shown for the time steps that have a segmentation associated with.
May 2 2019
There seems to be another exception thrown when willing the table view. The statistics table is not filled. The idea is now not to change the GetStatisticsForTimeStep functionality but handle the exception in the level above (like we started before with the try-catch)
Apr 26 2019
Pushed new branch T19683-ShowOnlySelectedNodesCrosshairVisibility.
Solution: GetStatisticsForTimeStep method now returns an empty StatisticsObject if no mask is provided for this time step. Thus, histogram and table are empty for those time steps.
Discussion: 1. 4D image + 3D segmentation
- 4D image (5 time steps) + 4D segmentation (1 time step)
@hentsch Is the one time step segmentation applied to all time steps? What is the expected behavior?
Pushed new branch T26029-4DImageAnd4DSegmentation.
Apr 12 2019
Pushed new branch T26276-SegmentationMultipleTimePoints.
Statistics are calculated for those time steps where a mask is provided, for the others not. When the view asks for the statistics an exception is thrown if the statistics don't exist.
Oct 2 2018
Sep 28 2018
Sep 3 2018
Pushed new branch T25364-DRRSimulation.