Wiki Documentation Site

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » signal_commands » Computing Custom Digitizing Pointer Configuration
visual3d:documentation:pipeline:signal_commands:computing_custom_digitizing_pointer_configuration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:pipeline:signal_commands:computing_custom_digitizing_pointer_configuration [2024/06/19 12:52] – sgrangervisual3d:documentation:pipeline:signal_commands:computing_custom_digitizing_pointer_configuration [2024/07/17 15:46] (current) – created sgranger
Line 1: Line 1:
-{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{users can construct their own digitizing pointer. the following steps demonstrate how to compute the location of the pointer tip relative to the markers attached to the rod.+====== Computing Custom Digitizing Pointer Configuration ======
  
-this is especially useful for users that want to construct a pointer using an electromagnetic or inertial sensor, because it isn't obvious how to measure physically the location of the tip from the electromagnetic sensor housing.+Users can construct their own digitizing pointer. The following steps demonstrate how to compute the location of the pointer tip relative to the markers attached to the rod.
  
-the following file was collected by streaming data from a polhemus liberty system into visual3d.+This is especially useful for users that want to construct a pointer using an electromagnetic or inertial sensor, because it isn't obvious how to measure physically the location of the tip from the electromagnetic sensor housing.
  
-https://www.has-motion.com/download/examples/llibertydigitizingpointer.c3d+The following file was collected by streaming data from a Polhemus Liberty system into Visual3D.
  
-==== step1. open the file in visual3d ====+https://www.has-motion.com/download/examples/LlibertyDigitizingPointer.c3d
  
-libertypointerconfig1.jpg\\+=== Step1. Open the file in Visual3D ===
  
 +{{:LibertyPointerConfig1.jpg}}\\
  
-note that visual3d displays the 6 degree of freedom information from the liberty sensor as 3 targets. this file contains two liberty sensors, which translates to 6 targets (3 for each sensor). 
  
-sensor 1 is attached to a pointer, so the movement of the pointer is defined by markers s1_1, s1_2, s1_3.+Note that Visual3D displays the 6 degree of freedom information from the Liberty sensor as 3 TARGETS. This file contains two Liberty sensors, which translates to 6 targets (3 for each sensor).
  
-in this file the pointer tip has been placed on the ground, and keeping the tip in contact with the ground, the pointer is rotated about that point.+Sensor 1 is attached to a pointer, so the movement of the pointer is defined by markers S1_1, S1_2, S1_3.
  
-the location of the tip is a stationary point, which means that we can compute its location as a functional joint.+In this file the pointer tip has been placed on the ground, and keeping the tip in contact with the ground, the pointer is rotated about that point.
  
-==== step 2. create a hybrid model using the same movement trial ====+The location of the tip is a stationary point, which means that we can compute its location as a functional joint.
  
-a dialog will appear indicating that the file is already open in the workspace. select the option to add a suffix to the filename.+=== Step 2. Create a hybrid model using the same movement trial ===
  
-libertypointerconfig2.jpg\\+A dialog will appear indicating that the file is already open in the workspace. Select the option to add a suffix to the filename.
  
 +{{:LibertyPointerConfig2.jpg}}\\
  
-another dialog will appear stating that the markers are not stationary. 
  
-libertypointerconfig3.jpg\\+Another dialog will appear stating that the markers are not stationary.
  
 +{{:LibertyPointerConfig3.jpg}}\\
  
-remember that we have loaded a movement trial, so in order for the average location of the markers to have any meaning, we must select only 1 frame of this trial. 
  
-==== step 3. assign the movement trial to the model file ====+Remember that we have loaded a movement trial, so in order for the average location of the markers to have any meaning, we must select only 1 frame of this trial.
  
-libertypointerconfig4.jpg\\+=== Step 3. Assign the movement trial to the model file ===
  
 +{{:LibertyPointerConfig4.jpg}}\\
  
-==== step 4. assign the frames for the static trial ====+ 
 +=== Step 4. Assign the frames for the static trial ===
  
 under the model menu select the option to "modify frame range for static calibration" and specify only one frame of data. under the model menu select the option to "modify frame range for static calibration" and specify only one frame of data.
  
-libertypointerconfig5.jpg\\+{{:LibertyPointerConfig5.jpg}}\\
  
  
-a warning will appear saying that the model has no mass and default value of 1 will be used. this default value is fine because we are not computing kinetics from this data.+A warning will appear saying that the model has no Mass and default value of 1 will be used. This default value is fine because we are not computing kinetics from this data.
  
-==== step 5. create a functional joint definition for the tip (f_tip) ====+=== Step 5. Create a functional joint definition for the tip (F_TIP) ===
  
-libertypointerconfig6.jpg\\+{{:LibertyPointerConfig6.jpg}}\\
  
  
-note that there isn't a default definition for this landmark, so you should type f_tip into the combo box as shown.+Note that there isn't a default definition for this landmark, so you should type F_TIP into the combo box as shown.
  
-select the create button.+Select the Create button.
  
-libertypointerconfig7.jpg\\+{{:LibertyPointerConfig7.jpg}}\\
  
  
-enter the information above. the landmark will be created relative to the 3 targets (eg. liberty sensor 1) and the movement will be computed relative to the lab.+Enter the information above. The landmark will be created relative to the 3 targets (eg. liberty sensor 1) and the movement will be computed relative to the LAB.
  
-==== step 6. compute the functional joint ====+=== Step 6. Compute the functional joint ===
  
-libertypointerconfig8.jpg\\+{{:LibertyPointerConfig8.jpg}}\\
  
  
-select the model builder postprocessing item on the toolbar.+Select the Model Builder PostProcessing item on the Toolbar.
  
-libertypointerconfig9.jpg\\+{{:LibertyPointerConfig9.jpg}}\\
  
  
-switch to the functional joints tab and select the button "add motion files from workspace".+Switch to the Functional Joints tab and select the button "add motion files from Workspace".
  
-select the motion file. at this point you should be able to animate the motion file.+Select the motion file. At this point you should be able to animate the motion file.
  
-specify the range of frames to be used for the functional joint calculation by selecting the buttons "set start event to current frame" and "set end event to current frame". current frame refers to the frame of data shown in the animation viewer.+Specify the range of frames to be used for the functional joint calculation by selecting the buttons "Set START Event to Current Frame" and "Set END Event to Current Frame". Current Frame refers to the frame of data shown in the animation viewer.
  
-libertypointerconfig10.jpg\\+{{:LibertyPointerConfig10.jpg}}\\
  
  
-select "compute selected landmarks"+Select "Compute SELECTED Landmarks"
  
-libertypointerconfig11.jpg\\+{{:LibertyPointerConfig11.jpg}}\\
  
  
-a landmark should appear in the animation viewer, and an instance of the functional joint should appear as a landmark+A landmark should appear in the animation viewer, and an instance of the functional joint should appear as a Landmark
  
-libertypointerconfig12.jpg\\+{{:LibertyPointerConfig12.jpg}}\\
  
  
-edit the landmark. note that the location of the tip is relative to the 3 markers.+edit the landmark. Note that the location of the tip is relative to the 3 markers.
  
-libertypointerconfig13.jpg\\+{{:LibertyPointerConfig13.jpg}}\\
  
  
-visual3d has selected the order of the 3 markers automatically based on a set of internal rules. there is no need to modify the default selection.+Visual3D has selected the order of the 3 markers automatically based on a set of internal rules. There is no need to modify the default selection.
  
-==== step 7. specify the pointer configuration ====+=== Step 7. Specify the pointer configuration ===
  
-switch to the digitizing landmarks tab+Switch to the Digitizing Landmarks Tab
  
-select the button "create/modify digitizing wand"+Select the button "Create/Modify Digitizing Wand"
  
-libertypointerconfig14.jpg\\+{{:LibertyPointerConfig14.jpg}}\\
  
  
-populate the dialog as shown.+Populate the dialog as shown.
  
-libertypointerconfig15.jpg\\+{{:LibertyPointerConfig15.jpg}}\\
  
  
-the order of the markers and the offsets are extracted from f_tip landmark definition above.+The order of the markers and the offsets are extracted from F_TIP landmark definition above.
  
-note especially that the offset locations are the negative of the f_tip landmark locations. this is because visual3d has a subtly different mechanism for specifying landmarks relative to markers, and landmarks relative to segments. the digitizing pointer is treated as a segment.+Note especially that the offset locations are the negative of the F_TIP landmark locations. This is because Visual3D has a subtly different mechanism for specifying landmarks relative to markers, and landmarks relative to segments. The digitizing pointer is treated as a segment.
  
-select the option "save to config file".+Select the option "Save to config file".
  
 \\ \\
  
  
-**this config file can then be loaded for subsequent trials.**+**This config file can then be loaded for subsequent trials.** 
  
  
-}}}}}}}}}}}}}}}}}}}}}}}}}}}}}} 
visual3d/documentation/pipeline/signal_commands/computing_custom_digitizing_pointer_configuration.1718801577.txt.gz · Last modified: by sgranger