Differences

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

--- visual3d:documentation:pipeline:plugins:optotrak [2024/06/26 20:28] – created sgranger
+++ visual3d:documentation:pipeline:plugins:optotrak [2024/07/17 15:46] (current) – created sgranger
@@ Line 38: / Line 38: @@
 Launch Visual3D, select the command pipeline dialog, and add the "Import_Optotrak_Files" to the Pipeline
-{{optotrak1.gif}}\\
+{{:optotrak1.gif}}\\
@@ Line 45: / Line 45: @@
 **Visual3D expects the v1# file to have a similar name to the c# file. e.g. c#001.dat and v1#001.dat.**
-{{optotrak2.gif}}\\
+{{:optotrak2.gif}}\\
 Execute the pipeline
-{{optotrak3.gif}}\\
+{{:optotrak3.gif}}\\
 A dialog will appear prompting you for the C# file. By default Visual3D has a filter to select files that end in the extensions .dat. If your files have a different extension, select a different filter option in the dialog combo. Do not select the V1# file as well, or you will get one C3D file containing the C# and V1# data, and another C3D file containing the V1# data alone.
-{{optotrak4.gif}}\\
+{{:optotrak4.gif}}\\
@@ Line 68: / Line 68: @@
 For example, **ANALOG:SCALE** for scaling A/D data to volts.
-{{analogScaleFactor.gif}}\\
+{{:analogScaleFactor.gif}}\\
-{{analog12bit.gif}}\\
+{{:analog12bit.gif}}\\
-{{analog16bit.gif}}\\
+{{:analog16bit.gif}}\\
 The Scaling parameter stored in the C3D file for a Type 2 force platform would be:
-{{analogScale.gif}}\\
+{{:analogScale.gif}}\\