- User Since
- Aug 1 2016, 12:10 PM (205 w, 9 h)
Which configuration did you used to build it? Was it a clean build?
Fri, Jul 3
Cannot reproduce the problem with the current develop. Just checked with all example projects. All worked fine T1 and T2 was visible?!?
@nolden: Do you have a clue?
Thu, Jul 2
Wed, Jul 1
As D329 is now landed. I think this is an low hanging fruit to check if the problem still exists ;)
Tue, Jun 30
Seems to be fixed already in the current develop branch
Covered by T27492 by accident ;)
Mon, Jun 29
New Image Statistics (preview)
The image statistics (modules ImageStatistics and ImageStatisticsUI as well as the QmitkImageStatisticsView provided by the plugin org.mitk.gui.qt.measurementtoolbox) have been heavily refactored on the backend and the frontend side. The rework is not yet finished as the current state just ensures that we have no regression but does only to a little extend tap into the potential of the new infrastructure.
The following paragraphs briefly summarize what’s new.
I would propose the following policy:
- All tools per default work only on the respective time step of the reference data and the segmentation, that are indicated by the currently selected time point (SliceNavigator). So this is general and independent from the fact if it is a 3D or a 4D segmentation. This is the same behavior like the interactive tools and does not break user expectations.
- It is up to the specific tool (must be discussed there) if for 4D reference images others then the current time step of the reference data step should be used. Per se, I would say no.
- It is up to the specific (3D) tool to allow the altering of more then the current segmentation time step (if the segmentation is 4D). If one wants such a feature I would add e.g. a check box to the tool like "confirm for all time steps".
Sat, Jun 27
Histogram has a simelar problem, but to fix that the Histogramwidget also needs a rework). Such a rework should be done in conjunction with the rework of T27284