User Tools

Site Tools


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/05/28 18:34] wikisysopvisual3d:documentation:pipeline:pipeline_commands:manage_file_merge [2025/05/28 19:44] (current) wikisysop
Line 101: Line 101:
 ====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:
  
-{{visual3d:documentation:pipeline:pipeline_commands:manage_file_merge_dialog.png}}+{{ visual3d:documentation:pipeline:pipeline_commands:manage_file_merge_dialog.png}} 
 +  * **Root path to search:** The directory root to search for all of the Files. 
 +  * **Open CMZ Library After Processing:**  
 +  * **Automatically save default CMZ files:** How the CMZ file should be saved as. 
 +  * **Use Index Theia Files (.hmx):** If you would like to use a .hmx file to supersede Theia3D files information. 
 +  * **File Tags:** If/how file tags should be added onto the files by.
  
-- Brief description of components (Combo boxesacronymsetc.)+**Primary Files:** 
 +  * **Primary Data Folder:** Method by which Theia3D data is stored. 
 +  * **Primary Session Folder Mask:** Folder mask for Theia3d files (directory within top level directory to search for Theia3D files). 
 +  * **Primary File Mask:** File name mask for Theia3D files. Can include wildcards. 
 +  * **Primary File Mask for Model:** File name mask for model file. If blank it will select the first file as the model file. Can include wildcards. 
 +  * **Theia3D Subject Tags:** Subject tags for Theia3D files. 
 +  * **Theia Prefixes:** Subject prefixes for Theia3D files. 
 +  * **Theia Color:** The color of the Theia3D skeleton. 
 +  * **Sex:** The sex of the Theia3D file for model inertial properties. 
 +  * **Choose Kinetic Thorax:** Choose which type of thorax to model. 
 + 
 +  * **Merge Primary Files:** Merge primary files into other primary files (mutually exclusive). 
 +  * **Import Analog Files:** Merge primary files with analog filessuch as force plate data (mutually exclusive). 
 +  * **Merge Primary Files and Other Files:** Merge primary files with other datasuch as marker-based files (mutually exclusive). 
 +  * **Treat Session Files as Independent:** ... 
 + 
 +**Secondary Files:** 
 +  * **Secondary Data Folder:** Method by which secondary data is stored. 
 +  * **Static Data Folder:** Method by which static secondary data is stored. 
 +  * **Other Session Folder Mask:** Folder mask for merged files (directory within top level directory to search for merged files)
 +  * **Other File Mask:** File name mask for merged files. Can include wildcards. 
 +  * **Other Static File Mask:** File name mask for static merged files. Can include wildcards. 
 +  * **Other Model Template Mask:** File name mask for model files (if needed). Can include wildcards. 
 +  * **Other Subject Tags:** Subject tags for merged files. 
 +  * **Other Prefixes:** Subject prefixes for merged files. 
 +  * **Other Color:** The color of the secondary data files. 
 +  * **Analog Filter Cutoff:** The lowpass filter cutoff for the analog files. 
 +  * **Target Filter Cutoff:** The lowpass filter cutoff for the target files. 
 +  * **FP_Auto_Baseline:** Method by which forceplate data was collected. 
 + 
 +  * **Restrict Number of Session Files:** Restricts the number of session files used. 
 +  * **Visual3D Pipeline Pre-Merge:** Visual 3D pipeline to run before the merge occurs. 
 +  * **Visual3D Pipeline Post-Merge:** Visual 3D pipeline to run after the merge occurs.
  
 |[IMAGE] |[IMAGE]
Line 121: Line 159:
 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:
  
-  Study +|**1. Study**|Although the name of this directory level suggests that the data it contains is only used for one study, this is not necessary. As a top-level concept this is the largest, most general database that is stored in one location. This could be specific to a study, or it could be specific to a project, researcher, lab, or consortium. In these latter cases it is possible to define [[Other:Inspect3D:Documentation:Dialogs:Advanced_Query_Section|queries]] to extract the specific signals that are desired for an individual study.| 
-  Group +|**2. Group**|This level of the directory structure is optional, but it allows the researcher to divide c3d files according to desired parameters, e.g., Women Men, Old - Young. If this level is omitted from the structure then individual C3D files can be [[Visual3D:Documentation:Definitions:Tag|tagged]] with the necessary parameters to allow for their specific selection.| 
-  Session +|**3. Session**|This directory level can be conceived as a single day (or single effort) of data collection within the database. This is the most important level as this is where the [[Visual3D:Documentation:Definitions:File_Formats:CMZ_Format_|CMZ file]] and log files get stored. This is also the level of the directory where static models are stored for all subjects involved in the session.| 
-  Task +|**4. Task**|This level of the directory allows the researcher to divide c3d files according to the desired activity, e.g., walking, running, jumping, etc. As with group-level parameters, C3D files can be coded with these different tasks by using [[Visual3D:Documentation:Definitions:Tag|tags]].| 
-  Trial+|**5. Trial**|At this level of the directory structure we have individual trials. This means that we have the individual C3D files that are recorded by the motion capture system.|
  
-**If you are using Theia3D files**, and use TMBATCH, the default folder structure will have 6 levels.From root folder to deepest leaf they are:\\+**If you are using Theia3D files**, and use TMBATCH, the default folder structure will have 6 levels. From root folder to deepest leaf they are:\\
   - Study   - Study
   - Group   - Group
Line 135: Line 173:
   - pose_filt_0.c3d   - pose_filt_0.c3d
  
-|Study|Although the name of this directory level suggests that the data it contains is only used for one study, this is not necessary. As a top-level concept this is the largest, most general database that is stored in one location. This could be specific to a study, or it could be specific to a project, researcher, lab, or consortium. In these latter cases it is possible to define [[Other:Inspect3D:Documentation:Dialogs:Advanced_Query_Section|queries]] to extract the specific signals that are desired for an individual study.| +
-|Group|This level of the directory structure is optional, but it allows the researcher to divide c3d files according to desired parameters, e.g., Women - Men, Old - Young. If this level is omitted from the structure then individual C3D files can be [[Visual3D:Documentation:Definitions:Tag|tagged]] with the necessary parameters to allow for their specific selection.| +
-|Session|This directory level can be conceived as a single day (or single effort) of data collection within the database. This is the most important level as this is where the [[Visual3D:Documentation:Definitions:File_Formats:CMZ_Format_|CMZ file]] and log files get stored. This is also the level of the directory where static models are stored for all subjects involved in the session.| +
-|Task|This level of the directory allows the researcher to divide c3d files according to the desired activity, e.g., walking, running, jumping, etc. As with group-level parameters, C3D files can be coded with these different tasks by using [[Visual3D:Documentation:Definitions:Tag|tags]].| +
-|Trial|At this level of the directory structure we have individual trials. This means that we have the individual C3D files that are recorded by the motion capture system.|+
visual3d/documentation/pipeline/pipeline_commands/manage_file_merge.1748457272.txt.gz · Last modified: 2025/05/28 18:34 by wikisysop