visual3d:documentation:modeling:landmarks:static_pointer_landmarks_and_segments
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:modeling:landmarks:static_pointer_landmarks_and_segments [2024/06/17 18:17] – created sgranger | visual3d:documentation:modeling:landmarks:static_pointer_landmarks_and_segments [2024/07/17 15:45] (current) – created sgranger | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Static Pointer Landmarks and Segments ==== | + | ====== Static Pointer Landmarks and Segments ====== |
+ | |||
+ | === Static Pointer Landmarks and Segments | ||
The Landmark defining the location of the Tip of a Static Pointer is done in three steps. | The Landmark defining the location of the Tip of a Static Pointer is done in three steps. | ||
- | [[NdiTempTipDefinition.gif]]\\ | + | {{:NdiTempTipDefinition.gif}}\\ |
The first step is to use the data in the Pointer INI File to create a Landmark at the tip of the pointer relative to 3 tracking markers. It is possible to use this Landmark for determining the anatomical landmarks but it is useful to use all 6 tracking markers that are available. Visual3D uses Optimal Tracking for locating a segment in space, and it has been demonstrated in the literature that using 6 markers connected to a rigid body produces more accurate results that three markers. Additionally, | The first step is to use the data in the Pointer INI File to create a Landmark at the tip of the pointer relative to 3 tracking markers. It is possible to use this Landmark for determining the anatomical landmarks but it is useful to use all 6 tracking markers that are available. Visual3D uses Optimal Tracking for locating a segment in space, and it has been demonstrated in the literature that using 6 markers connected to a rigid body produces more accurate results that three markers. Additionally, | ||
- | [[NdiWandSegment.gif]]\\ | + | {{:NdiWandSegment.gif}}\\ |
The Wand Segment is defined using the three markers associated with the temporary landmark, and tracked using all 6 tracking markers. | The Wand Segment is defined using the three markers associated with the temporary landmark, and tracked using all 6 tracking markers. | ||
- | [[NdiTipDefinition.gif]]\\ | + | {{:NdiTipDefinition.gif}}\\ |
Line 20: | Line 22: | ||
**Note:** The Segment and Landmarks are created automatically when the Pointer INI file is interpreted. The information is presented here only for completeness. | **Note:** The Segment and Landmarks are created automatically when the Pointer INI file is interpreted. The information is presented here only for completeness. | ||
- | ==== Static Pointer Event Labels | + | === Static Pointer Event Labels === |
Event Labels can not be computed automatically for Static Pointer because there is no trigger (e.g. the compression of the spring of the Davis Pointer) to base the Event identification on. | Event Labels can not be computed automatically for Static Pointer because there is no trigger (e.g. the compression of the spring of the Davis Pointer) to base the Event identification on. | ||
Line 27: | Line 29: | ||
Typically, the user must create the Event Labels manually by looking at the travel of the Tip Landmark and setting an Event (labeled as a ?) at each location that the tip of the wand isn't moving in space. This process is not particularly time consuming and need only be done once; Exporting the Movement Trial that includes the Event Labels. | Typically, the user must create the Event Labels manually by looking at the travel of the Tip Landmark and setting an Event (labeled as a ?) at each location that the tip of the wand isn't moving in space. This process is not particularly time consuming and need only be done once; Exporting the Movement Trial that includes the Event Labels. | ||
- | |||
- | |||
visual3d/documentation/modeling/landmarks/static_pointer_landmarks_and_segments.1718648225.txt.gz · Last modified: 2024/06/17 18:17 by sgranger