US4DCyl: When you change the timestep, the histogram and the visualization remains the same.
Heart3D+t: no volume visualization shown at all (no matter which timestep or which histogram I select).
(Release installer, windows)
Description
Description
Revisions and Commits
Revisions and Commits
| rMITK MITK | |||
| Restricted Differential Revision | rMITKf68ef917dff3 Fix volume rendering for 4d images, adapt histogram and volume itself | ||
| Restricted Differential Revision | rMITKed883fa6af57 Refactorings from review | ||
| Restricted Differential Revision | rMITKfd647480c6ec Fix volume rendering for 4d images | ||
Related Objects
Related Objects
Event Timeline
Comment Actions
I think this is a task were everybody can have a look at and try do debug the relevant code to at least provide some more information in this task and to narrow down the problem.
Comment Actions
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.
Comment Actions
For the histogram part the reason is (swiftly looking into the code) that Neither the TransferFunctionWidgets nor the used histogramm classes support 4D images, the assume images to be static. But as the QmitkTransferFunctionWidget want the whole node, we cannot just use a TimePointSelector filter in the view. It seems like we need to extend the interface of the TransferFunctionWidgets (same for the QmitkTransferFunctionGeneratorWidget) in order to also set the current time step and handel it internally correctly.
Comment Actions
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.