Wiki Documentation Site

User Tools

Site Tools

You are here: Main Page » visual3d » tutorials » theia » Theia3D Merge
visual3d:tutorials:theia:theia3d_merge

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:tutorials:theia:theia3d_merge [2024/07/03 17:46] – created sgrangervisual3d:tutorials:theia:theia3d_merge [2025/09/24 16:01] (current) – wikisysop
Line 1: Line 1:
-====== Theia3D_Merge ======+====== Theia3D Merge ====== 
 +** The [[#Manage_Theia3D_Merge|Manage_Theia3D_Merge]] command is no longer recommended since [[visual3d:documentation:pipeline:pipeline_commands:manage_file_merge]] was updated to be used for file types other than just from Theia3D.**
  
 This tutorial demonstrates the process of merging Theia3D's output [[Visual3D:Documentation:C3D_Signal_Types:C3D_Format|C3D]] files and other C3D files. The typical scenario is to merge Theia3D's motion capture output and analog signals such as force platform recordings. This tutorial demonstrates the process of merging Theia3D's output [[Visual3D:Documentation:C3D_Signal_Types:C3D_Format|C3D]] files and other C3D files. The typical scenario is to merge Theia3D's motion capture output and analog signals such as force platform recordings.
Line 10: Line 11:
 ==== Demo Files ==== ==== Demo Files ====
  
-Download the [[[https://drive.google.com/file/d/1KwwDEz4jKxVoACnUY1MpGajpZMsHozvH/view?usp=sharing|zip file]]] containing folder paths and files for this tutorial.+Download the [[https://drive.google.com/file/d/1KwwDEz4jKxVoACnUY1MpGajpZMsHozvH/view?usp=sharing|zip file]] containing folder paths and files for this tutorial.
  
 ==== Merging C3D files interactively ==== ==== Merging C3D files interactively ====
Line 16: Line 17:
 === Open Theia3D C3D File === === Open Theia3D C3D File ===
  
-If you use TMBATCH, select the default folder paths, which should be in the form.+If you use TMBATCH, select the default folder paths, which should be in the form. \\
 STUDY : GROUP : SESSION : ACTION : TRIAL : pose_filt_0.c3d STUDY : GROUP : SESSION : ACTION : TRIAL : pose_filt_0.c3d
 +
 The relative path for this example data is: The relative path for this example data is:
 ...\Visual3D_Tutorial\001_THEIA\WALK\001\pose_filt_0.c3d ...\Visual3D_Tutorial\001_THEIA\WALK\001\pose_filt_0.c3d
 +
 Open this file: Open this file:
 +
 Visual3D recognizes this as a Theia3D output file and will automatically create a model and assign the motion file. Visual3D recognizes this as a Theia3D output file and will automatically create a model and assign the motion file.
 The workspace status TAB will display the model and movement trial. The workspace status TAB will display the model and movement trial.
 Note that the standing trial was created virtually based on the c3d parameters in the movement trial Note that the standing trial was created virtually based on the c3d parameters in the movement trial
 The name of the static file is the name of the first movement file loaded with _Static applied to the name. The name of the static file is the name of the first movement file loaded with _Static applied to the name.
-{{Theia3D_Tutorial_1.jpg}}+ 
 +{{:Theia3D_Tutorial_1.jpg?500}}
  
 Switch to Model Builder mode. Switch to Model Builder mode.
 +
 The segments and landmarks have been created automatically. The segments and landmarks have been created automatically.
-{{Theia3D_Tutorial_2.jpg}}+ 
 +{{:Theia3D_Tutorial_2.jpg?500}}
  
 Edit the Right Thigh segment Edit the Right Thigh segment
-{{Theia3D_Tutorial_3.jpg}}+ 
 +{{:Theia3D_Tutorial_3.jpg?500}}
  
 Note that Theia3D stores [[Visual3D:Documentation:C3D_Signal_Types:ROTATION_DATA_TYPE|ROTATION signals]], not TARGETS. Note that Theia3D stores [[Visual3D:Documentation:C3D_Signal_Types:ROTATION_DATA_TYPE|ROTATION signals]], not TARGETS.
Line 39: Line 47:
 Unless there is a reason to modify the coordinate system, the default is to assign the ROTATION signal to the pose of the segment. Unless there is a reason to modify the coordinate system, the default is to assign the ROTATION signal to the pose of the segment.
 Switch to the Signals and Events TAB and animate the motion file. Switch to the Signals and Events TAB and animate the motion file.
 +
 Note the ROTATION folder is open in this image displaying the ROTATION signals exported by Theia3D. Note the ROTATION folder is open in this image displaying the ROTATION signals exported by Theia3D.
-{{Theia3D_Tutorial_4.jpg}}+ 
 +{{:Theia3D_Tutorial_4.jpg?500}}
  
 === Import Analog signals and Force Platform parameters from QTM C3D File === === Import Analog signals and Force Platform parameters from QTM C3D File ===
Line 47: Line 57:
  
 STUDY : GROUP : SESSION_QTM : ACTION : Trial#.c3d STUDY : GROUP : SESSION_QTM : ACTION : Trial#.c3d
 +
 The QTM filenames should be similar to the Theia3D TRIAL path name. For example, The QTM filenames should be similar to the Theia3D TRIAL path name. For example,
  
 The relative path for this example data is: The relative path for this example data is:
-\Visual3D_Tutorial\001_QTM\WALK\MoCapNwalk_001.c3d+ 
 +\Visual3D_Tutorial\001_QTM\WALK\MoCapNwalk_001.c3d\\
 Use the following command to import analog signals and force platform parameters from the QTM generated c3d file. Use the following command to import analog signals and force platform parameters from the QTM generated c3d file.
  
 [[Visual3D:Documentation:Pipeline:File_Commands:Import_Signals_From_C3D_File|Import_Signals_From_C3D_File]] [[Visual3D:Documentation:Pipeline:File_Commands:Import_Signals_From_C3D_File|Import_Signals_From_C3D_File]]
 For this example, we only need to specify a few of the possible parameters for this command and leave the remaining parameters to their default values For this example, we only need to specify a few of the possible parameters for this command and leave the remaining parameters to their default values
 +
 +<code>
 Import_Signals_From_C3D_File Import_Signals_From_C3D_File
 /ANALOG_RATIO=5 /ANALOG_RATIO=5
 /IMPORT_FORCE_PLATFORM_PARAMETERS=TRUE /IMPORT_FORCE_PLATFORM_PARAMETERS=TRUE
-**;**+; 
 +</code> 
 After executing this command the analog signals and force platform parameters have been added to the Theia3D file. After executing this command the analog signals and force platform parameters have been added to the Theia3D file.
-{{Theia3D_Tutorial_5.jpg}}+ 
 +{{:Theia3D_Tutorial_5.jpg?500}}
  
 === Exporting the merged C3D file (Optional) === === Exporting the merged C3D file (Optional) ===
  
 The resulting C3D file is still named pose_filt_0.c3d, which is a bit of a nuisance in Visual3D as the short filename for all files would be the same. The resulting C3D file is still named pose_filt_0.c3d, which is a bit of a nuisance in Visual3D as the short filename for all files would be the same.
 +
 From the **File** menu, open the **Export** subfolder and select **Export C3D File.** The //Export C3D File// dialog box will open.\\ From the **File** menu, open the **Export** subfolder and select **Export C3D File.** The //Export C3D File// dialog box will open.\\
-{{Tutorial2_8.jpg}}\\+{{:Tutorial2_8.jpg?500}}\\
  
 From the **File to Export** drop down Select //pose_filt_0.c3d.// From the **File to Export** drop down Select //pose_filt_0.c3d.//
Line 75: Line 93:
 From the //Export C3D File// dialog box Click **Export.**\\ From the //Export C3D File// dialog box Click **Export.**\\
 **Note:** Leave all other options at the default values. Many of these options are available to handle irregularities in the c3d file format, and should only be used when necessary. **Note:** Leave all other options at the default values. Many of these options are available to handle irregularities in the c3d file format, and should only be used when necessary.
 +
 Given the merged c3d file, you can save the file as a cmz file Given the merged c3d file, you can save the file as a cmz file
 or you can [[Visual3D:Documentation:Pipeline:File_Commands:Export_C3DFile|export the c3d file]] or you can [[Visual3D:Documentation:Pipeline:File_Commands:Export_C3DFile|export the c3d file]]
 +
 ==== Manage_Theia3D_Merge ==== ==== Manage_Theia3D_Merge ====
  
Line 82: Line 102:
 In order to automate the merge, it was necessary to make some assumptions about filenames and folder paths similar to the [[#Merging_C3D_files_interactively|previous example]]. In order to automate the merge, it was necessary to make some assumptions about filenames and folder paths similar to the [[#Merging_C3D_files_interactively|previous example]].
 If you use Theia's TMBATCH, select the default folder paths. This should be in the form. If you use Theia's TMBATCH, select the default folder paths. This should be in the form.
 +
 STUDY : GROUP : SESSION_THEIA : ACTION : TRIAL : pose_filt_0.c3d STUDY : GROUP : SESSION_THEIA : ACTION : TRIAL : pose_filt_0.c3d
 +
 The Other files should be stored in the following The Other files should be stored in the following
 +
 STUDY : GROUP : SESSION_OTHER : ACTION : Trial#.c3d STUDY : GROUP : SESSION_OTHER : ACTION : Trial#.c3d
-The OTHER filenames should be similar to the Theia3D TRIAL path name. For this tutorial the file paths begin at the session level, + 
-001_THEIA : WALK : TRIAL1 : pose_filt_0.c3d+The OTHER filenames should be similar to the Theia3D TRIAL path name. For this tutorial the file paths begin at the session level,\\ 
 +001_THEIA : WALK : TRIAL1 : pose_filt_0.c3d\\
 001_QTM : WALK : Trial1.c3d 001_QTM : WALK : Trial1.c3d
 ​ ​
- 
 While this example may include only one Theia3D file and one Other file, the command will act on all SESSIONS, ACTIONS and TRIALS in the filepath. While this example may include only one Theia3D file and one Other file, the command will act on all SESSIONS, ACTIONS and TRIALS in the filepath.
 A cmz file is created for each session and stored in the corresponding Theia3D session A cmz file is created for each session and stored in the corresponding Theia3D session
Line 95: Line 118:
  
 Having all files named pose_filt_0.c3d is a bit of a nuisance for Visual3D and the files are renamed by the command. Having all files named pose_filt_0.c3d is a bit of a nuisance for Visual3D and the files are renamed by the command.
-The new name is a concatenation of the name and TRIAL name. For this example+The new name is a concatenation of the name and TRIAL name. For this example\\
 WALK_TRIAL1.c3d WALK_TRIAL1.c3d
 +
 Having the sessions in parallel was implemented because Theia3D keeps evolving and there may be multiple versions of the Theia3D Session for the same original videos.  Having the sessions in parallel was implemented because Theia3D keeps evolving and there may be multiple versions of the Theia3D Session for the same original videos. 
 +
 For example: SESSION_V2 and SESSION_V3 For example: SESSION_V2 and SESSION_V3
 +
 Getting the Theia3D files into this folder structure is straightforward as it is the default from Theia. Getting the Theia3D files into this folder structure is straightforward as it is the default from Theia.
 +
 Note that the command requires the specification of the full root folder. Note that the command requires the specification of the full root folder.
 For this documentation I have represented all but the last folder in the hierarchy For this documentation I have represented all but the last folder in the hierarchy
-{{Theia3D_Tutorial_61.jpg}} 
  
 +{{:Theia3D_Tutorial_61.jpg?500}}
 +
 +<code>
 Manage_Theia3D_Merge Manage_Theia3D_Merge
 /ROOT_FOLDER=\\Mac\Home\Desktop\TestData\Merge\Wiki Example\Visual3D_Theia_Tutorial1\ /ROOT_FOLDER=\\Mac\Home\Desktop\TestData\Merge\Wiki Example\Visual3D_Theia_Tutorial1\
Line 140: Line 169:
 ! /VISUAL3D_PIPELINE_POST_MERGE= ! /VISUAL3D_PIPELINE_POST_MERGE=
 ! /VISUAL3D_PIPELINE_PREMERGE= ! /VISUAL3D_PIPELINE_PREMERGE=
-**;**+; 
 +</code> 
 The Visual3D workspace is as follows: Note the name of the files WALK_001.c3d and WALK_001_STATIC.c3c The Visual3D workspace is as follows: Note the name of the files WALK_001.c3d and WALK_001_STATIC.c3c
  
-{{Theia3D_Tutorial_7.jpg}}+{{:Theia3D_Tutorial_7.jpg?500}}
  
 The data and animation should look the same as the previous example The data and animation should look the same as the previous example
  
-{{Theia3D_Tutorial_5.jpg}}+{{:Theia3D_Tutorial_5.jpg?500}}
  
 === Merge Targets and Analog Signals === === Merge Targets and Analog Signals ===
Line 154: Line 185:
 To distinguish the marker and markerless data, subject prefixes were added. To distinguish the marker and markerless data, subject prefixes were added.
 The result will have two models associated with the movement trials. The result will have two models associated with the movement trials.
-{{Theia3D_Tutorial_62.jpg}} 
  
 +{{:Theia3D_Tutorial_62.jpg?500}}
 +
 +<code>
 Manage_Theia3D_Merge Manage_Theia3D_Merge
 /ROOT_FOLDER=\\Mac\Home\Desktop\TestData\Merge\Wiki Example\Visual3D_Theia_Tutorial1\ /ROOT_FOLDER=\\Mac\Home\Desktop\TestData\Merge\Wiki Example\Visual3D_Theia_Tutorial1\
Line 192: Line 225:
 ! /VISUAL3D_PIPELINE_POST_MERGE= ! /VISUAL3D_PIPELINE_POST_MERGE=
 ! /VISUAL3D_PIPELINE_PREMERGE= ! /VISUAL3D_PIPELINE_PREMERGE=
-**;**+; 
 +</code> 
 After executing this command the workspace will have one motion file associated with two model files After executing this command the workspace will have one motion file associated with two model files
-{{Theia3D_Tutorial_9.jpg}}+ 
 +{{:Theia3D_Tutorial_9.jpg?500}}
  
 One model file is for the marker data One model file is for the marker data
 Note the prefix M: on the marker names Note the prefix M: on the marker names
-{{Theia3D_Tutorial_10.jpg}}+ 
 +{{:Theia3D_Tutorial_10.jpg?500}}
  
 One model file is for the Theia3D data One model file is for the Theia3D data
 Note the prefix ML: on the rotation names Note the prefix ML: on the rotation names
-{{Theia3D_Tutorial_11.jpg}}+ 
 +{{:Theia3D_Tutorial_11.jpg?500}}
  
 The resulting animation will display both models. The resulting animation will display both models.
-{{Theia3D_Tutorial_12.jpg}}+ 
 +{{:Theia3D_Tutorial_12.jpg?500}}
  
  
  
visual3d/tutorials/theia/theia3d_merge.1720028791.txt.gz · Last modified: by sgranger