When one comes to work with 4D images, it is required that all the 3D images along the timeline must have the same space dimensions, otherwise such initialization makes mitk crash.
This would not happen with images from medical devices but it may happen with processed or synthetic images. Although the algorithms that create such processed 4D images should care about that, it may happen that one wants to join in a single 4D dataset, two frames of images of different resolution or dimension (vtkStructuredPoints f.i.). This is unlikely to happen, but at least it would be nice that mitk checks this and notices this error in runtime while calling Image::SetVolume functions and other related, instead of crashing. However, if the preconditions of those functions are clearly to be passed a valid image that matches completely with the initialized 4D image, at least warn the user in the documentation of those functions that he must be the one checking that the dimensions, scalars and other fields do match. Note that this problem only appears with images. Surfaces work in different way and they can be set along the timeline with no problems. Best regards Juan Antonio Moya Scientific developer Computational Imaging Lab, Pompeu Fabra University Networking Research Center on Bioengineering, Biomaterials and Nanomedicine (CIBER-BBN) Information & Communication Technologies Department - D. 313 Pompeu Fabra University, Pg. Circumval·lació 8 08003 Barcelona - Spain Phone +34 935 421350
<<image001.gif>>
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
