Differences

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

--- sift:application:update_cmzs_dialog [2024/09/12 18:49] – wikisysop
+++ sift:application:update_cmzs_dialog [2024/11/15 16:49] (current) – [Remove Exclusions] wikisysop
@@ Line 1: / Line 1: @@
 ====== Update CMZs Dialog ======
-The updateCMZs Dialog {{:sift_update_cmz.png?30x30}} can be found on the main toolbar in Sift. This menu allows you to run Visual3D pipeline scripts to perform the following on your entire library:
+The updateCMZs Dialog {{:sift_update_cmz.png?30x30}} can be found on the main toolbar in Sift. This menu allows you to create and run Visual3D pipeline scripts to perform the following on your entire library:
-  - Creating BAD events or tags to indicate traces that were excluded in Sift
+  - Create BAD events or tags to indicate traces that were excluded in Sift
-  - Updating force assignments based on excluded traces
+  - Update force assignments based on excluded traces
-  - Creating events or tags to indicate traces that are included in Sift
+  - Create events or tags to indicate traces that are included in Sift
-  - Removing BAD events or tags that were created in the CMZ file by Sift
+  - Remove events or tags in the CMZ file(s)
 {{:UpdateCMZGrey.png}}
-===== UpdateCMZs Dialog =====
 ----
-==== Excluded Data ====
+===== Excluded Traces =====
 {{ :UpdateExclude.png}}
+Adding an Event to Exclude Signals will alter the workspace files to include the specified event during the bad cycle.
+  * This will also update the query definitions to exclude any trace containing the specified "Bad" event
 There are three methods for adding an event in order to exclude signals:
   * Only exclude individual traces
     * This means an event, such as AnkleAngle_BAD will be created during the bad cycle and the group definition of AnkleAngle will now exclude any sequences containing AnkleAngle_BAD
   * Exclude all traces for this side when any data is excluded
+    * This means an event will be created for ALL queried signals, during the specified cycle, on the SAME SIDE of the body (R/L)
   * 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
+    * This means an event will be created for ALL queried signals, during the specified cycle, regardless of side
 It is also possible to add tags in order to exclude specific trials:
   * A trial that contains excluded data will be tagged with the specified tag name
 ----
-==== Update Force Assignment ====
+===== Update Force Assignment =====
 {{ :UpdateForce.png}}
@@ Line 36: / Line 36: @@
 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
+  * For any groups that contain the specified text (ex. Force,GRF), delete force assignments during excluded cycles
 ----
-=== Included Data ===
+===== Included Data =====
 {{ :UpdateNew.png}}
@@ Line 46: / Line 46: @@
 ----
-=== Remove Exclusions ===
+===== Remove Exclusions =====
 {{ :UpdateRemove.png}}
-If you have created events or tags to exclude data, it is always possible to remove these events or tags from your CMZ file.
+If you want to remove events or tags from the loaded library, including those you have created to exclude data, it is always possible to remove them by selecting the tags or events.