HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » pipeline_commands » Manage_File_Merge
visual3d:documentation:pipeline:pipeline_commands:manage_file_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:documentation:pipeline:pipeline_commands:manage_file_merge [2025/07/25 15:18] – wikisysopvisual3d:documentation:pipeline:pipeline_commands:manage_file_merge [2025/09/10 17:00] (current) – wikisysop
Line 1: Line 1:
-=====Manage_File_Merge=====+======Manage_File_Merge======
  
-====Overview====+=====Overview=====
 The **Manage File Merge** command is designed to merge multiple files that recorded data from the same motion capture trial. This command merges data types from each .c3d file into one trial in the Visual3D workspace. This command was originally called **Manage_Theia3D_Merge**, but since has been updated to be used for file types other than from Theia3D.  The **Manage File Merge** command is designed to merge multiple files that recorded data from the same motion capture trial. This command merges data types from each .c3d file into one trial in the Visual3D workspace. This command was originally called **Manage_Theia3D_Merge**, but since has been updated to be used for file types other than from Theia3D. 
  
Line 10: Line 10:
 This command requires data files to be stored in a particular folder structure to match .c3d files appropriately. Please carefully review the [[visual3d:documentation:pipeline:pipeline_commands:manage_file_merge#Notes| Notes]] section of this page for more details. This command requires data files to be stored in a particular folder structure to match .c3d files appropriately. Please carefully review the [[visual3d:documentation:pipeline:pipeline_commands:manage_file_merge#Notes| Notes]] section of this page for more details.
  
-====Pipeline Command====+=====Pipeline Command=====
 Below is the full pipeline command and parameters for Manage_File_Merge Below is the full pipeline command and parameters for Manage_File_Merge
 <code> <code>
Line 56: Line 56:
  
  
-====Command Parameters====+=====Command Parameters=====
 The following table shows the command parameters and descriptions: The following table shows the command parameters and descriptions:
  
Line 99: Line 99:
 |**! /VISUAL3D_PIPELINE_PREMERGE=**|Visual 3D pipeline to run before the merge occurs.| |**! /VISUAL3D_PIPELINE_PREMERGE=**|Visual 3D pipeline to run before the merge occurs.|
  
-====Dialog====+=====Dialog=====
 The command can be edited in a text editor or in a dialog form. To edit in the dialog pop up form either click on the **Edit** button in the pipeline workshop or double-click on the pipeline command. The dialog is shown below. The command can be edited in a text editor or in a dialog form. To edit in the dialog pop up form either click on the **Edit** button in the pipeline workshop or double-click on the pipeline command. The dialog is shown below.
 There are a variety of inputs that can be used to generate CMZs from Theia3D files: There are a variety of inputs that can be used to generate CMZs from Theia3D files:
Line 146: Line 146:
 |[IMAGE] |[IMAGE]
 | |
-====Examples==== +=====Examples===== 
-===Merge Theia with QTM Analog Data===+====Merge Theia with QTM Analog Data====
  
 This following is an example of using the Manage_File_Merge command to merge markerless motion capture files from Theia with force plate analog signals from QTM. This following is an example of using the Manage_File_Merge command to merge markerless motion capture files from Theia with force plate analog signals from QTM.
  
-== Folder Structure ==+If using a version of Visual3D v2025.07.2 or newer, the Virtual Lab will not be automatically configured. In Manage_File_Merge the VIRTUAL_LAB parameter needs to be assigned a segment. In order to create a Virtual Laboratory segment see here, [[visual3d:documentation:modeling:virtual_lab:creating_a_virtual_laboratory|Virtual Laboratory]].
  
-The folder structure of the QTM and Theia files that were capture in this sample data is:+===Folder Structure=== 
 + 
 +The [[visual3d:documentation:pipeline:pipeline_commands:manage_file_merge#folder_structure1|folder structure]] of the QTM and Theia files that were capture in this sample data is:
  
 {{:visual3d:documentation:pipeline:pipeline_commands:mergeexample1folder.png?800}} {{:visual3d:documentation:pipeline:pipeline_commands:mergeexample1folder.png?800}}
  
-== Pipeline Command == +===Pipeline Command=== 
-{{ :visual3d:documentation:pipeline:pipeline_commands:mergeexample1dlg.png?600}}+{{ :visual3d:documentation:pipeline:pipeline_commands:mergeexample1dlg.png?700}}
 The following pipeline was run to merge QTM Analog signals and Theia files: The following pipeline was run to merge QTM Analog signals and Theia files:
 <code> <code>
Line 203: Line 205:
 </code> </code>
  
-===Merge Multiple QTM Files===+===Output=== 
 +A Visual3D CMZ Workspace is created containing the model from the Theia3D rotation signals, and analog channels from the QTM force platforms.  
 +{{:visual3d:documentation:pipeline:pipeline_commands:mergeexample1result.png?700}} 
 + 
 +====Merge Markerless and Marker-based Files==== 
 + 
 +This following is an example of using the Manage_File_Merge command to merge markerless motion capture files from Theia with marker-based motion capture files from QTM. 
 + 
 +===Folder Structure=== 
 + 
 +The [[visual3d:documentation:pipeline:pipeline_commands:manage_file_merge#folder_structure1|folder structure]] of the QTM and Theia files that were capture in this sample data is: 
 + 
 +{{:visual3d:documentation:pipeline:pipeline_commands:mergeexample1folder.png?800}} 
 + 
 +===Pipeline Command=== 
 +{{ :visual3d:documentation:pipeline:pipeline_commands:mergeexample2dlg.png?700}} 
 +The following pipeline was run to merge QTM markerbased and Theia markerless files: 
 +<code> 
 +Manage_File_Merge 
 +/ROOT_FOLDER=C:\Users\sydne\OneDrive\Documents\Merge_Tutorial_Study\ML_Players\ 
 +! /HMX_INDEX_MASK= 
 +! /USE_HMX_INDEX=FALSE 
 +! /ACTION= 
 +! /TAGS=ACTION 
 +! /IMPORT_ANALOG_FILES=FALSE 
 +! /MERGE_PRIMARY_FILES=FALSE 
 +/MERGE_PRIMARY_AND_OTHER_FILES=TRUE 
 +! /MERGE_EVENT_LABELS=FALSE 
 +/PRIMARY_SESSION_FOLDER=*001_THEIA 
 +! /PRIMARY_FILE_MASK=*.c3d 
 +! /PRIMARY_FILE_MAS_FOR_MODEL= 
 +/THEIA3D_PREFIX=ML: 
 +/THEIA3D_SUBJECT_TAG=ML 
 +/PRIMARY_COLOR=Black 
 +! /PRIMARY_SEX=UNKNOWN 
 +! /CREATE_MODEL_FOR_EACH_C3D_FILE=FALSE 
 +/OTHER_SESSION_FOLDER=*001_QTM 
 +/OTHER_FILE_MASK=*.c3d 
 +/OTHER_MODEL_MASK=*.c3d 
 +/OTHER_MODEL_TEMPLATE_MASK=*.mdh 
 +/OTHER_PREFIX=M: 
 +/OTHER_SUBJECT_TAG=M 
 +/OTHER_COLOR=Black 
 +! /NUMBER_OF_SESSION_FILES_ALLOWED= 
 +! /SAVE_DEFAULT_CMZ_FILES=TRUE 
 +! /DEFAULT_CMZ_NAME=<SESSION> 
 +! /OPEN_CMZ_LIBRARY=FALSE 
 +! /VIRTUAL_LAB= 
 +/INPUT_DATA_FOLDER_PRIMARY=TRIAL 
 +/INPUT_DATA_FOLDER_SECONDARY=ACTION 
 +/INPUT_STATIC_DATA_FOLDER=SESSION 
 +! /KINETIC_THORAX=RTA 
 +! /ANALOG_FILTER_CUTOFF=12 
 +! /TARGET_FILTER_CUTOFF=12 
 +/FP_AUTO_BASELINE=Treadmill_Foreaft 
 +! /VISUAL3D_PIPELINE_POST_MERGE= 
 +! /VISUAL3D_PIPELINE_PREMERGE= 
 +; 
 +</code> 
 + 
 +**NOTE:** It is necessary to include M: and ML: for the marker-based and markerless prefixes, or the merge will not work! 
 + 
 + 
 +===Output=== 
 +A Visual3D CMZ Workspace is created containing both the markerless and marker-based solutions. 
 +  
 +{{:visual3d:documentation:pipeline:pipeline_commands:mergeexample2result.png?700}}
  
  
  
-=====Notes===== +======Notes====== 
-==== Folder Structure ====+=====Folder Structure=====
 There is an assumed basic directory structure for this command's input data that aligns with some useful concepts from the experiments that produced the data. This directory structure organizes the [[Visual3D:Documentation:Definitions:File_Formats:CMZ_Format_|CMZ files]] and [[Visual3D:Documentation:C3D_Signal_Types:C3D_Format|C3D files]] that contain the information relevant for analysis. This structure has 5 levels, from root folder to deepest leaf they are: There is an assumed basic directory structure for this command's input data that aligns with some useful concepts from the experiments that produced the data. This directory structure organizes the [[Visual3D:Documentation:Definitions:File_Formats:CMZ_Format_|CMZ files]] and [[Visual3D:Documentation:C3D_Signal_Types:C3D_Format|C3D files]] that contain the information relevant for analysis. This structure has 5 levels, from root folder to deepest leaf they are:
  
visual3d/documentation/pipeline/pipeline_commands/manage_file_merge.1753456706.txt.gz · Last modified: 2025/07/25 15:18 by wikisysop