visual3d:documentation:pipeline:file_commands:importing_aurora_files
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:file_commands:importing_aurora_files [2024/06/26 20:25] – created sgranger | visual3d:documentation:pipeline:file_commands:importing_aurora_files [2025/03/03 18:44] (current) – wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | |||
+ | < | ||
+ | Merge_Aurora_Files | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! /UNITS=cm | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
Given Aurora files in which each signal is stored independently in an ASCII file with the following format. | Given Aurora files in which each signal is stored independently in an ASCII file with the following format. | ||
Line 31: | Line 41: | ||
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}}\\ |
Line 48: | Line 58: | ||
Open the text file that was just created. Select File -> Open. Select the viewer for .txt files. Select " | Open the text file that was just created. Select File -> Open. Select the viewer for .txt files. Select " | ||
- | {{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}}\\ |
Line 64: | Line 74: | ||
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}}\\ |
Line 81: | Line 91: | ||
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 " | Type " | ||
- | {{MergeAuroraFiles11.gif}} | + | {{:MergeAuroraFiles11.gif}} |
visual3d/documentation/pipeline/file_commands/importing_aurora_files.1719433535.txt.gz · Last modified: 2024/06/26 20:25 by sgranger