Predicate that evaluates if the given DataNode's data object has the same geometry (in terms of spacing, origin, orientation) as the reference geometry. More...
#include <mitkNodePredicateGeometry.h>
Public Member Functions inherited from Protected Member Functions | |
| NodePredicateGeometry (const BaseGeometry *refGeometry) | |
| Constructor that checks the reference geometry against the first data timepoint. More... | |
| NodePredicateGeometry (const BaseGeometry *refGeometry, TimePointType relevantTimePoint) | |
| Constructor that checks the reference geometry against a specific timepoint. More... | |
| NodePredicateGeometry (const TimeGeometry *refGeometry) | |
| Constructor that checks against the whole time geometry. More... | |
Protected Attributes | |
| BaseGeometry::ConstPointer | m_RefGeometry |
| TimeGeometry::ConstPointer | m_RefTimeGeometry |
| TimePointType | m_TimePoint |
| bool | m_UseTimePoint |
| Indicates if m_TimePoint should be regarded or always the first timestep should be used. More... | |
| mitk::ScalarType | m_CheckCoordinatePrecision |
| Precision that should be used for the equal coordinate checks. More... | |
| mitk::ScalarType | m_CheckDirectionPrecision |
| Precision that should be used for the equal direction checks. More... | |
Detailed Description
Predicate that evaluates if the given DataNode's data object has the same geometry (in terms of spacing, origin, orientation) as the reference geometry.
One can either check the whole time geometry of the data node by defining a reference time geometry or check against one given reference base geometry. If the predicate should check against a base geometry, you can specify the timepoint of the data's time geometry that should be checked. If no timepoint is defined the predicate will evaluate the data geometry in the first timestep. Evaluates to "false" for unsupported or undefined data objects/geometries.
One can specify the tolerance/precision of the check via SetCheckPrecision(), SetCheckCoordinatePrecision() or SetCheckDirectionPrecision().
- Remarks
- The default tolerance for coordinate checks is defined by NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_COORDINATE_PRECISION. The default tolerance for direction checks is defined by NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_DIRECTION_PRECISION. Both are not as strict as mitk::eps. The reason is that, for the typical use of the node predicate, mitk::eps would be too pedantic, as we encounter often rounding differences/errors in real world data sets. For more details, see the documentation of the aforementioned constants. We have introduced two different precision values because differences are less impactful for coordinates than for direction values. Therefore we can relax coordinate checks more than direction checks.
Definition at line 52 of file mitkNodePredicateGeometry.h.
Constructor & Destructor Documentation
◆ ~NodePredicateGeometry()
|
override |
Standard Destructor.
◆ NodePredicateGeometry() [1/3]
|
protected |
Constructor that checks the reference geometry against the first data timepoint.
- Parameters
-
refGeometry The reference base geometry to compare against.
◆ NodePredicateGeometry() [2/3]
|
protected |
Constructor that checks the reference geometry against a specific timepoint.
- Parameters
-
refGeometry The reference base geometry to compare against. relevantTimePoint The timepoint of the data's time geometry to evaluate.
◆ NodePredicateGeometry() [3/3]
|
protected |
Constructor that checks against the whole time geometry.
- Parameters
-
refGeometry The reference time geometry to compare against.
Member Function Documentation
◆ CheckNode()
|
overridevirtual |
Checks if the node's data geometry matches the reference geometry.
- Parameters
-
node The DataNode to check.
- Returns
- True if the geometry matches within the configured precision.
Implements mitk::NodePredicateBase.
◆ GetCheckCoordinatePrecision()
|
virtual |
◆ GetCheckDirectionPrecision()
|
virtual |
◆ mitkClassMacro()
| mitk::NodePredicateGeometry::mitkClassMacro | ( | NodePredicateGeometry | , |
| NodePredicateBase | |||
| ) |
◆ mitkNewMacro1Param() [1/2]
| mitk::NodePredicateGeometry::mitkNewMacro1Param | ( | NodePredicateGeometry | , |
| const BaseGeometry * | |||
| ) |
◆ mitkNewMacro1Param() [2/2]
| mitk::NodePredicateGeometry::mitkNewMacro1Param | ( | NodePredicateGeometry | , |
| const TimeGeometry * | |||
| ) |
◆ mitkNewMacro2Param()
| mitk::NodePredicateGeometry::mitkNewMacro2Param | ( | NodePredicateGeometry | , |
| const BaseGeometry * | , | ||
| TimePointType | |||
| ) |
◆ SetCheckCoordinatePrecision()
|
virtual |
◆ SetCheckDirectionPrecision()
|
virtual |
◆ SetCheckPrecision()
| void mitk::NodePredicateGeometry::SetCheckPrecision | ( | mitk::ScalarType | precision | ) |
Sets both CheckCoordinatePrecision and CheckDirectionPrecision to the passed value.
- Parameters
-
precision The precision value to use for both coordinate and direction checks.
Member Data Documentation
◆ m_CheckCoordinatePrecision
|
protected |
Precision that should be used for the equal coordinate checks.
Definition at line 109 of file mitkNodePredicateGeometry.h.
◆ m_CheckDirectionPrecision
|
protected |
Precision that should be used for the equal direction checks.
Definition at line 111 of file mitkNodePredicateGeometry.h.
◆ m_RefGeometry
|
protected |
Definition at line 103 of file mitkNodePredicateGeometry.h.
◆ m_RefTimeGeometry
|
protected |
Definition at line 104 of file mitkNodePredicateGeometry.h.
◆ m_TimePoint
|
protected |
Definition at line 105 of file mitkNodePredicateGeometry.h.
◆ m_UseTimePoint
|
protected |
Indicates if m_TimePoint should be regarded or always the first timestep should be used.
Definition at line 107 of file mitkNodePredicateGeometry.h.
The documentation for this class was generated from the following file:
