Yes, TimeSlicedGeometry holds the Geometry3D's for each time step. Each MITK data object has one, if it is derived from mitk::BaseData (which are all data classes I know of). It is created in the constructor. By default, TimeSlicedGeometry is initialized with one (empty) geomtry hold in time step zero, which is then initialized in the data class constructor.
If you do not use 4D data, you should not need TimeSlicedGeometry, as all member functions default to time step zero, which is just the 3D geometry of the object. But if your Mapper should support 4D data, you can use it to check if the time step you want to render is valid. You are right, documentation lacks a bit... Please consider that MITK is not a commercial product, and most of the developement on MITK is done by PhD students. But we constantly working on improving this. Good to hear that your renderer works! If you think it can be useful to the MITK community and you are willing to share your code, we are always interested in integrating enhancing developements into our toolkit. Best, Tobi ------------------------------------------------------------ Tobias Schwarz DKFZ German Cancer Research Center (Deutsches Krebsforschungszentrum) Member of the Helmholtz Association Division of Medical & Biological Informatics E130 Im Neuenheimer Feld 280 D-69120 Heidelberg Phone: 49-(0)6221-42-2353 Fax: 49-(0)6221-42-2345 E-Mail: [email protected]<mailto:[email protected]> Web: http://www.dkfz.de/en/mbi/<https://dkfzowa0.dkfz-heidelberg.de/owa/redir.aspx?C=6ebb39f6c3b94e03a77eca6c5e2e87a9&URL=http%3a%2f%2fwww.dkfz.de%2fen%2fmbi%2f> Confidentiality Note: This message is intended only for the use of the named recipient(s) and may obtain confidential and/or privileged information. If you are not the intended recipient, please contact the sender and delete the message. Any unauthorized use of the information contained in this message is prohibited. ________________________________ Von: Lodron, Gerald [[email protected]] Gesendet: Freitag, 10. September 2010 12:07 An: Schwarz Tobias Betreff: AW: [mitk-users] Help on understanding mitk::Geometries Thanks, Does the TimeSlicedGeometry only holds time coordinates or does it holds Geometry3D's for each time step? My first renderer already renders :-), i am only not sure if i render it correctly for each possible geometry but currently it works so let us hope... The class dokumentation here is very rare... Best regards -----Ursprüngliche Nachricht----- Von: Schwarz Tobias [mailto:[email protected]] Gesendet: Freitag, 10. September 2010 11:58 An: Lodron, Gerald; '[email protected]' Betreff: AW: [mitk-users] Help on understanding mitk::Geometries Dear Gerald, here is a short overview over the different geometries. There are so many different geometries because many different things are displayed :) TimeSlicedGeometry: Kind of a global geometry. Mostly of interest if you use 4D data. It holds the time in milliseconds and the associated time steps of each 3D object in the time series. Geometry3D: Each object has one. It holds the origin, position, scale, and rotation of an object, and also its bounding box. Can convert between world and index (pixel) coordinates. It has two underlying geometries: a VTK transform (4x4 matrix) for display via VTK, and an ITK transform (itkScalableAffineTransform) for MITK and ITK calculations in filters. These two are always the same, normally. Note that also 2D objects have a Geometry3D to describe their position in world coordinates. SlicedGeometry3D: Describes how an object consisting of slices (i.e. image) is structured, i.e. how the slices are arranged to each other. Only used for images as far as I know. Holds all geometry2D's of the object. Geometry2D: Used for projecting 3D coordinates on a 2D plane (e.g. image slice). For images, normally used as its subclass, PlaneGeometry. PlaneGeometry: Describes a 2D rectangular plane. DisplayGeometry: The geometry of the screen display of a widget. Holds the position and size of the widget in monitor coordinates. Used e.g. for picking mouse event positions. AbstractTransformGeometry: Just for completeness: This class is used for curved 2D planes defined by a vtkAbstactTransform. There are also some subclasses of it to describe special curved 2D geometries. Hope this help you a little, Best, Tobi ------------------------------------------------------------ Tobias Schwarz DKFZ German Cancer Research Center (Deutsches Krebsforschungszentrum) Member of the Helmholtz Association Division of Medical & Biological Informatics E130 Im Neuenheimer Feld 280 D-69120 Heidelberg Phone: 49-(0)6221-42-2353 Fax: 49-(0)6221-42-2345 E-Mail: [email protected]<mailto:[email protected]> Web: http://www.dkfz.de/en/mbi/<https://dkfzowa0.dkfz-heidelberg.de/owa/redir.aspx?C=6ebb39f6c3b94e03a77eca6c5e2e87a9&URL=http%3a%2f%2fwww.dkfz.de%2fen%2fmbi%2f<http://www.dkfz.de/en/mbi/%3Chttps://dkfzowa0.dkfz-heidelberg.de/owa/redir.aspx?C=6ebb39f6c3b94e03a77eca6c5e2e87a9&URL=http%3a%2f%2fwww.dkfz.de%2fen%2fmbi%2f>> Confidentiality Note: This message is intended only for the use of the named recipient(s) and may obtain confidential and/or privileged information. If you are not the intended recipient, please contact the sender and delete the message. Any unauthorized use of the information contained in this message is prohibited. ________________________________ Von: Lodron, Gerald [[email protected]] Gesendet: Donnerstag, 9. September 2010 07:57 An: '[email protected]' Betreff: [mitk-users] Help on understanding mitk::Geometries Hi I try to implement my own mapper (currently only 2D) and have problems understanding the geometry design. I now that they must have something to do with the current cut plane in the 2d views but why are there so many geometries? Examples: GetDisplayGeometry, GetCurrentWorldGeometry2D, GetTimeSlicedGeometry etc. There is also a GetVtkTransform finction in the data node. Can anyone explain me what they exactly do and what functions are needed to make a mapper? best regards Gerald Lodron Human-Centered Image Processing Machine Vision Applications DIGITAL - Institute of Information and Communication Technologies JOANNEUM RESEARCH Forschungsgesellschaft mbH Steyrergasse 17, 8010 Graz, AUSTRIA phone: +43-316-876-1751 fax: +43-316-876-1751 web: http://www.joanneum.at/digital e-mail: [email protected]<mailto:[email protected]> ------------------------------------------------------------------------------ Automate Storage Tiering Simply Optimize IT performance and efficiency through flexible, powerful, automated storage tiering capabilities. View this brief to learn how you can reduce costs and improve performance. http://p.sf.net/sfu/dell-sfdev2dev _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
