Differences

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

--- visual3d:documentation:pipeline:file_commands:importing_aurora_files [2024/06/19 12:50] – sgranger
+++ visual3d:documentation:pipeline:file_commands:importing_aurora_files [2025/03/03 18:44] (current) – wikisysop
@@ Line 1: / Line 1: @@
-{{{{{{{{{{{{{{{{{{{{{{given aurora files in which each signal is stored independently in an ascii file with the following format.
+====== Importing Aurora Files ======
-collection data : port 01 ( traxtal tech s/n: 343bbc0e type: 01000000 rev: 000 ) [august 17, 2002 02:16am]
+<code>
+Merge_Aurora_Files
+! /INPUT_FILE_NAMES=
+! /OUTPUT_FILE_NAME=
+! /FRAME_RATE=1000
+! /UNITS=cm
+! /SET_PROMPT=Open Aurora files
+;
+</code>
+Given Aurora files in which each signal is stored independently in an ASCII file with the following format.
+Collection Data : Port 01 ( Traxtal Tech S/N: 343BBC0E Type: 01000000 Rev: 000 ) [August 17, 2002 02:16AM]
 \\
-|frame,  |q0,    |qx,     |qy,    |qz,     |x,    |y,    |z,      |
+|Frame,  |Q0,    |Qx,     |Qy,    |Qz,     |x,    |y,    |z,      |
 |1369560,|0.2980,|-0.6755,|0.2496,|-0.6264,|97.82,|56.54,|-102.57,|
 |1369592,|0.2980,|-0.6755,|0.2496,|-0.6264,|97.82,|56.54,|-102.57,|
@@ Line 13: / Line 25: @@
-the variables are described in the ndi aurora manual. q0, qx, qy, qz represent the orientation expressed as a quaternion x, y, z represents the position of the object in the measurement volume error represents an error measure.
+The variables are described in the NDI Aurora Manual. Q0, Qx, Qy, Qz represent the orientation expressed as a Quaternion X, Y, Z represents the position of the object in the Measurement Volume Error represents an error measure.
-importing a set of signals (e.g. a set of files) into visual3d as a single file requires first that the files be merged into a single file. for convenience, we combine the files into a standard [[https://www.c-motion.com/support/visual3d.php?topic=v3d_asciiformat#topic-1088|visual3d ascii file format]]. the following command is available in the pipeline.
+Importing a set of signals (e.g. a set of files) into Visual3D as a single file requires first that the files be merged into a single file. For convenience, we combine the files into a standard [[https://www.c-motion.com/support/Visual3D.php?topic=V3D_ASCIIFormat#topic-1088|Visual3D ASCII file format]]. The following command is available in the Pipeline.
-**merge_aurora_files**\\
+**Merge_Aurora_Files**\\
-/input_file_names=\\
+/INPUT_FILE_NAMES=\\
-/output_file_name=\\
+/OUTPUT_FILE_NAME=\\
-/frame_rate=1000\\
+/FRAME_RATE=1000\\
 **;**
-aurora files do not contain a frame rate, so the user can enter a frame rate using this command. if the input and output files are left blank, visual3d will prompt the user for the input files (select all of the signals), then prompts the user for the output file.
+Aurora files do not contain a frame rate, so the user can enter a frame rate using this command. If the input and output files are left blank, Visual3D will prompt the user for the input files (select all of the signals), then prompts the user for the output file.
-the following example files are available [[https://www.has-motion.com/download/examples/aurora.zip|here]].
+The following Example files are available [[https://www.has-motion.com/download/examples/aurora.zip|here]].
-launch visual3d, open the pipeline, and add the merge_aurora_files command to the pipeline.
+Launch Visual3D, open the Pipeline, and add the Merge_Aurora_Files command to the pipeline.
-mergeaurorafiles1.gif\\
+{{:MergeAuroraFiles1.gif}}\\
-execute the pipeline
+Execute the Pipeline
-mergeaurorafiles2.gif\\
+{{:MergeAuroraFiles2.gif}}\\
-select the four signals (as stored in four separate files).
+Select the four signals (as stored in four separate files).
-mergeaurorafiles3.gif\\
+{{:MergeAuroraFiles3.gif}}\\
-select (or specify) the output file that will contain all four (in this case) signals.
+Select (or specify) the output file that will contain all four (in this case) signals.
-open the text file that was just created. select file -> open. select the viewer for .txt files. select "aurora.txt".
+Open the text file that was just created. Select File -> Open. Select the viewer for .txt files. Select "aurora.txt".
-mergeaurorafiles4.gif\\
+{{:MergeAuroraFiles4.gif}}\\
-the file will be loaded into memory. the aurora file contains position and rotation data for a rigid body. it will appear in visual3d as linkmodel_based items containing the origin (3 components) and quaternion (4 components).
+The file will be loaded into memory. The Aurora file contains position and rotation data for a rigid body. It will appear in Visual3D as LINKMODEL_BASED items containing the ORIGIN (3 components) and QUATERNION (4 components).
-mergeaurorafiles5.gif\\
+{{:MergeAuroraFiles5.gif}}\\
-visual3d typically works with motion capture markers, so to maximize your ability to work with this data, you can create a set of 3 targets per rigid body using the following command.
+Visual3D typically works with motion capture markers, so to maximize your ability to work with this data, you can create a set of 3 targets per rigid body using the following command.
-**create_targets_for_linkmodelbased_rotations**\\
+**Create_Targets_For_LinkModelBased_Rotations**\\
-**/signal_folders=port_01+port_02+port_03+port_04**\\
+**/SIGNAL_FOLDERS=Port_01+Port_02+Port_03+Port_04**\\
 **;**
-targets for each rigid body should appear in the data tree.
+Targets for each rigid body should appear in the data tree.
+{{:MergeAuroraFiles6.jpg}}\\
-mergeaurorafiles6.jpg\\
+It is possible to save this data to a C3D formatted file, but the LINK MODEL data (e.g. the ORIGINAL Translation and Quaternion will be lost, so it is recommended that you save this data to a cmo file.
-it is possible to save this data to a c3d formatted file, but the link model data (e.g. the original translation and quaternion will be lost, so it is recommended that you save this data to a cmo file.
+{{:MergeAuroraFiles7.gif}}\\
-mergeaurorafiles7.gif\\
+If you need a static trial for modeling the data, you can save the first frame of data to a c3d file.
-if you need a static trial for modeling the data, you can save the first frame of data to a c3d file.
+{{:MergeAuroraFiles8.gif}}\\
-mergeaurorafiles8.gif\\
+===== Creating Visual3D Segments from Aurora Data =====
-====== creating visual3d segments from aurora data ======
+Create a hybrid model using a c3d file containing one frame of data from the Aurora text file.
-create a hybrid model using a c3d file containing one frame of data from the aurora text file.
+{{:MergeAuroraFiles9.gif}}\\
-mergeaurorafiles9.gif\\
+Assign the motion file to the model file
-assign the motion file to the model file
+{{:MergeAuroraFiles10.gif}}\\
-mergeaurorafiles10.gif\\
+Type "Segment1" into the combo box and select the **Create** button.
-type "segment1" into the combo box and select the **create** button.
+{{:MergeAuroraFiles11.gif}}
-mergeaurorafiles11.gif
-}}}}}}}}}}}}}}}}}}}}}}