Medical Imaging Interaction Toolkit
2024.06.99-e4ca64e0
Medical Imaging Interaction Toolkit
|
The Datamanager is the central component to manage medical data like images, segmentation masks, registrations, surfaces, point sets, annotations, measurements, etc..
After loading data into the Datamanager the data is shown in the four-view window, the so-called Standard Display. The user can now start working on the data by interacting with the data inside the Standard Display, by using the MITK-plugins such as Segmentation or Basic Image Processing or by using the context menu inside the data manager.
There are several ways of loading data into the Datamanager as so-called data nodes:
A lot of file-formats can be loaded into MITK, for example:
The user can also load a series of 2D images (e.g. image001.png, image002.png ...) to a MITK 3D volume. To do this, just drag and drop one of those 2D data files into the Datamanager by holding the ALT key. Note: What really happens is that the data nodes are stored inside a "Data storage" and the Datamanager is just a visual representation of the data inside the "Data storage". That's why the documentation sometimes uses the term "Data storage" instead of "Datamanager".
There are several ways of saving data from the Datamanager:
After loading data into the Datamanager the data appears as data nodes in a sorted list inside the Datamanager. The user can change the order of the data nodes manually by dragging one or multiple data nodes and dropping them at any position inside the Datamanager. Data nodes can also be sorted hierarchically as a parent-child-relation. For example after using the Segmentation-Plugin to create a segmentation on DataNode, the result is created as ChildNode, which is a child of DataNode (see Parent-Child-Relation screenshot).
A parent-child-relation can be changed by dragging a child of a data node and dropping it onto another data node. For this the Property Allow changing of parent nodes needs to be enabled (see Preferences).
By default all loaded data nodes are visible in the Standard Display. The visibility is indicated by the checkbox in front of the data node name in the Datamanager. If a data node is visible, the checkbox is filled - an empty checkbox indicates a hidden data node (see Parent-Child-Relation screenshot). Hint: The data nodes are rendered on top of each other, such that the topmost visible data node is always displayed on top of other data nodes. By hiding the topmost visible data node the next data node becomes the topmost visible data node and the hidden data node is not rendered anymore. Note: "Visible" does not mean that the node is correctly displayed inside the render windows. The user might have to re-initialize a data node to have it correctly displayed.
Some MITK-plugins contain widgets to control the data nodes that are used for plugin-specific data processing. These widgets can be configured such that they listen to the current selection of the Datamanager. Having such a plugin active each selection change of data nodes inside the data manager will change the respective selection of the plugin. The data node selection widgets can have specific node predicates, which means that only specific data nodes can be controlled by the widgets. It might happen that a selected data node will not be represented in such a selection widget or that the selection widget will be emptied.
There are two ways of changing the name of a data node inside the Datamanager:
In both cases the new name can be accepted by hitting Enter or by clicking somewhere else.
The Datamanager provides a context menu for each data node that can be opened by right-clicking on a data node. An example of the context-menu can be seen in the Context menu screenshot. The context menu allows to quickly perform common actions on data nodes. These actions differ according to the data type. Some of these actions are described here. For more actions see the respective modules and plugins (e.g. QmitkCreatePolygonModelAction
inside the org_mitk_gui_qt_segmentation
-plugin.
"includeInBoundingBox"
to false "visible"
. "includeInBoundingBox"
to false "visible"
. As the description of the actions showed, it is possible to open / use the context menu with a single data node or with a set of selected data nodes. If the data types of multiple selected data nodes differ, the actions might not appear / work as expected. Also some actions are not available for a set of selected data nodes.
The MITK Workbench provides a preference page for specific plugins. The preference page provided for the Datamanager can be seen in the Preference page screenshot. The user can open the preference page by
It allows to set the following preferences for the Datamanager, which define the behavior of the Datamanager:
"helper object"
to true will be displayed in the Datamanager. If disabled, data nodes that have set "helper object"
to true will not be visible in the Datamanager.
The MITK Workbench provides hotkeys for specific plugins. The hotkeys provided for the Datamanager can be seen in the Hotkeys screenshot. They allow to expedite common operations in relation to data nodes or the Datamanager. The user can customize the hotkeys by accessing the preference page:
"includeInBoundingBox"
to false "visible"
"includeInBoundingBox"
to false "visible"