Differences

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

--- inspect3d:documentation:knowledge_discovery:pipeline [2024/07/03 17:34] – created sgranger
+++ inspect3d:documentation:knowledge_discovery:pipeline [2024/07/12 13:26] (current) – removed sgranger
@@ Line 1: / Line 1: @@
-====== Pipeline ======
-Inspect3D can be used to run pipelines and update the CMZ files in your CMO Library by:
-  - Creating BAD events or tags to indicate traces that were excluded in Inspect3D
-  - Updating force assignments based on excluded traces
-  - Creating events or tags to indicate traces that are included in Inspect3D
-  - Removing BAD events or tags that were created in the CMZ file by Inspect3D
-==== Specify the Pipeline ====
-=== Excluded Data ===
-There are three methods for adding an event in order to exclude signals:
-  * Only exclude individual traces
-    * This means an event Bad_LAnkleAngle_X will be created during the bad cycle and the group definition of AnkleAngle_X will now exclude any sequences containing Bad_LAnkleAngle_X
-  * Exclude all traces for this side when any data is excluded
-  * Exclude all traces when data is excluded (regardless of side)
-    * Creates a general event "BAD" and all currently loaded group definitions will now exclude any sequences containing BAD
-It is also possible to add tags in order to exclude specific trials:
-  * An trial that contains excluded data will be tagged with the specified tag name
-Finally, it is possible to update force assignments during specified cycles:
-  * For any groups that contain the specified text (ex. Force,GRF) delete force assignments during those cycles
-=== Included Data ===
-Besides tagging data to be excluded, it is also possible to create a tag or event for all data that is included (i.e. not excluded).
-=== Remove Exclusions ===
-If you have created events or tags to exclude data, it is always possible to remove these events or tags from your CMZ file.