Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:definitions:cmo_library [2024/07/12 13:59] – created sgranger
+++ visual3d:documentation:definitions:cmo_library [2024/11/15 15:37] (current) – wikisysop
@@ Line 1: / Line 1: @@
-====== CMO_Library_ ======
+====== CMO Library  ======
 CMO Libraries are used to handle large data sets. Common use cases include creating a normal database for comparisons or processing data across multiple subjects.
@@ Line 9: / Line 9: @@
 If you place all the .CMZ files under one folder/tree and set the 'CMO Library Path' to the root folder of the files, you can "Browse" the .cmo/.cmz files inside of Visual3D. It's a way of quickly opening the indices (.cmx) for the files and being able to quickly access signals/data to process them across many .CMZ files.
-You set the active files to EACH_CMO_WORKSPACE, or ALL_CMO_GLOBALS depending what data you want to examine/process/export.
+You set the [["Visual3D:documentation:definitions:Active_Files|active files]] to EACH_CMO_WORKSPACE, or ALL_CMO_GLOBALS depending what data you want to examine/process/export.
 You can run any pipeline to calculate/analyze across all of the .CMZ files in a directory/library using the CMO_LIBRARY without having to open each one, which is a faster than processing each one individually.
@@ Line 30: / Line 30: @@
 **NOTE:** The CMO Library will load any CMO files in sub-folders
-{{SetCMOLibraryPath.png}}
+{{:SetCMOLibraryPath.png}}
 **2.** Catalog the CMO files by going to **CMO Library -> Maintenance -> Catalog CMO Files**\\
@@ Line 36: / Line 36: @@
 **NOTE:** By cataloging the CMO files, Visual3D updates each CMX file to ensure it reflects the processed data in the CMO file. The CMX file is also updated each time a CMO file is saved. If the CMX files have not been moved or deleted, this process does not need to be done more than once. (Especially since this process can takes a long time)
-{{Maintenance_CatalogCMOFiles.png}}
+{{:Maintenance_CatalogCMOFiles.png}}
 **3.** Browse the CMO Library by going to **CMO Library -> Browse CMO Library**\\
@@ Line 44: / Line 44: @@
-{{BrowseCMOLibrary.png}}
+{{:BrowseCMOLibrary.png}}
 The CMO Library will now be loaded into the workspace. The files will be highlighted in a purple color (in a regular CMO file, the files are highlighted in blue, grey, & pink).\\
@@ Line 54: / Line 54: @@
-{{LoadedCMOLibrary.png}}
+{{:LoadedCMOLibrary.png}}
 === Selecting the Active File ===
-**The Active File selection in the CMO Library is one of the most important features in Visual3D.**
+**The [[:Visual3D:Documentation:Definitions:Active_Files|Active File]] selection in the CMO Library is one of the most important features in Visual3D.**
 Although any command can be run on the CMO Library, for the following example, the affect of running the METRIC_MEAN command on each of the active files will be explained.
@@ Line 68: / Line 68: @@
 After loading the CMO Library with multiple subject's CMO files, the average knee flexion is being calculated. Selecting different Active Files will have different effects on how the CMO Library processes future commands:
-{{CMOLibrary_SelectActiveFile.png}}
+{{:CMOLibrary_SelectActiveFile.png}}
-**1. Individual C3D file -**\\
+**1. Individual C3D file**\\
-If METRIC_MEAN is run on a specific C3D file, the result value will be the average knee flexion for that trial. If Generate Global Mean and STDDev is checked, the average value for the specified trial will be created in the GLOBAL workspace.
+If METRIC_MEAN is run on a specific C3D file, the result value will be the average knee flexion for that trial. If Generate Global Mean and STDDev is checked, the average value for the specified trial will be created in the GLOBAL workspace.\\
-**2. EACH_CMO_WORKSPACE -**\\
+**2. EACH_CMO_WORKSPACE**\\
-If METRIC_MEAN is run on EACH_CMO_WORKSPACE, the average of each individual trial will be calculated. If Generate Global Mean and STDDev is checked, the average value for each CMO file for each of the trials will be averaged and stored in the GLOBAL workspace.
-**3. TAGs -**\\
+If METRIC_MEAN is run on EACH_CMO_WORKSPACE, the average of each individual trial will be calculated. If Generate Global Mean and STDDev is checked, the average value for each CMO file for each of the trials will be averaged and stored in the GLOBAL workspace.\\
-If METRIC_MEAN is calculated on a group of file tags, the average of each individual trial will be calculated. If Generate Global Mean and STDDev is checked, the average value for each of the tagged trials will be averaged and stored in the GLOBAL workspace.
+**3. TAGs**\\
-**4. GLOBAL -**\\
-The average values calculated while using the CMO Library will be stored here. These metrics should represent the average across multiple CMO files.
+If METRIC_MEAN is calculated on a group of file tags, the average of each individual trial will be calculated. If Generate Global Mean and STDDev is checked, the average value for each of the tagged trials will be averaged and stored in the GLOBAL workspace.\\
-**5. ALL_CMO_GLOBALS -**\\
+**4. GLOBAL**\\
+The average values calculated while using the CMO Library will be stored here. These metrics should represent the average across multiple CMO files.\\
+**5. ALL_CMO_GLOBALS**\\