Differences

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

--- inspect3d:documentation:knowledge_discovery:pipeline [2024/06/19 12:45] – sgranger
+++ inspect3d:documentation:knowledge_discovery:pipeline [2024/07/12 13:26] (current) – removed sgranger
@@ Line 1: / Line 1: @@
-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.