visual3d:documentation:pipeline:plugins:optotrak
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:plugins:optotrak [2024/06/19 14:02] – created sgranger | visual3d:documentation:pipeline:plugins:optotrak [2024/07/17 15:46] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Optotrak ====== | ||
| + | |||
| \\ | \\ | ||
| - | ===== Import_Optotrak_Files | + | ==== Import_Optotrak_Files ==== |
| This plugin imports the motion capture data (C# file) and one of the 2 types of analog data (O1#, V1#) files. | This plugin imports the motion capture data (C# file) and one of the 2 types of analog data (O1#, V1#) files. | ||
| Line 19: | Line 21: | ||
| |**/ | |**/ | ||
| - | ===== Importing from C# and V1# Files ===== | + | ==== Importing from C# and V1# Files ==== |
| Importing c# and v1# optotrak files. The c# files contain the motion capture data. The v1# files contain synchronized ANALOG data in which the data are stored in units of **VOLTS.** The following Pipeline Command prompts the user for the c# file; the associated v1# files is loaded automatically and should not be selected by the user. | Importing c# and v1# optotrak files. The c# files contain the motion capture data. The v1# files contain synchronized ANALOG data in which the data are stored in units of **VOLTS.** The following Pipeline Command prompts the user for the c# file; the associated v1# files is loaded automatically and should not be selected by the user. | ||
| Line 36: | Line 38: | ||
| Launch Visual3D, select the command pipeline dialog, and add the " | Launch Visual3D, select the command pipeline dialog, and add the " | ||
| - | {{optotrak1.gif}}\\ | + | {{:optotrak1.gif}}\\ |
| Line 43: | Line 45: | ||
| **Visual3D expects the v1# file to have a similar name to the c# file. e.g. c#001.dat and v1# | **Visual3D expects the v1# file to have a similar name to the c# file. e.g. c#001.dat and v1# | ||
| - | {{optotrak2.gif}}\\ | + | {{:optotrak2.gif}}\\ |
| Execute the pipeline | 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. | 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}}\\ |
| The resulting c3d file will be loaded into the Visual3D Workspace automatically. The .dat files can be backed up because from this point forward, only the c3d files will be needed. | The resulting c3d file will be loaded into the Visual3D Workspace automatically. The .dat files can be backed up because from this point forward, only the c3d files will be needed. | ||
| - | ===== The default scale factors for the ANALOG Data ===== | + | ==== The default scale factors for the ANALOG Data ==== |
| For NDI's ODAU there are two ways of storing the ANALOG data. The O1# files store the data in computer units; a scale factor must be specified that scales the data to units of volts. The V1# files store the data in volts and the scale factors should therefore be 1. | For NDI's ODAU there are two ways of storing the ANALOG data. The O1# files store the data in computer units; a scale factor must be specified that scales the data to units of volts. The V1# files store the data in volts and the scale factors should therefore be 1. | ||
| Line 66: | Line 68: | ||
| For example, **ANALOG: | For example, **ANALOG: | ||
| - | {{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: | The Scaling parameter stored in the C3D file for a Type 2 force platform would be: | ||
| - | {{analogScale.gif}}\\ | + | {{:analogScale.gif}}\\ |
| Line 92: | Line 94: | ||
| * for the O1# files to 0.000305175. | * for the O1# files to 0.000305175. | ||
| - | ===== Frequently Asked Questions | + | ==== Frequently Asked Questions ==== |
| - | ==== File extensions | + | === File extensions === |
| Importing OptoTrak files only allows me to import files with the extension *.dat. I have different file extensions for every subject, such as *.f01, *.f02, etc. | Importing OptoTrak files only allows me to import files with the extension *.dat. I have different file extensions for every subject, such as *.f01, *.f02, etc. | ||
| Line 102: | Line 104: | ||
| Note that if your file extensions are different between subjects, but the prefix to the files names is the same (e.g. trial1.f01, trial1.f02) you will need to make sure that data from different subjects is saved to different folders because the import command strips off the extension and replaces it with .c3d. | Note that if your file extensions are different between subjects, but the prefix to the files names is the same (e.g. trial1.f01, trial1.f02) you will need to make sure that data from different subjects is saved to different folders because the import command strips off the extension and replaces it with .c3d. | ||
| - | ==== File Size ==== | + | === File Size === |
| I can import my shorter optotrak files (collected for 10s at 100Hz for Optotrak). However, the larger trials (collected for 50s at 100Hz for Optotrak) the program either crashes or comes up with an error. Is there a limit on the file size? | I can import my shorter optotrak files (collected for 10s at 100Hz for Optotrak). However, the larger trials (collected for 50s at 100Hz for Optotrak) the program either crashes or comes up with an error. Is there a limit on the file size? | ||
| Line 115: | Line 117: | ||
| **POINT: | **POINT: | ||
| - | ==== Changing the default TARGET names. | + | === Changing the default TARGET names. === |
| The C# and V# files created by Northern Digital software do not contain names for the signals stored. Data that are collecting in NDI's Toolbench software use a .ndo file (an ASCII file in a standard .ini format) to store information. | The C# and V# files created by Northern Digital software do not contain names for the signals stored. Data that are collecting in NDI's Toolbench software use a .ndo file (an ASCII file in a standard .ini format) to store information. | ||
visual3d/documentation/pipeline/plugins/optotrak.1718805776.txt.gz · Last modified: 2024/06/19 14:02 by sgranger