Differences

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

--- sift:application:exclude_data [2026/03/10 15:24] – [Tutorials] wikisysop
+++ sift:application:exclude_data [2026/07/06 19:51] (current) – [How Exclusions Work] desmond
@@ Line 1: / Line 1: @@
 ====== Excluding Data in Sift ======
-In biomechanics, some trials or trace may not be suitable for analysis. A missed marker, an incorrect force plate assignment, or an unexpected movement during a trial can all introduce noise into the results. Rather than deleting these trials outright, Sift allows users to flag them for exclusion, which keeps the analysis clean while preserving the original data.
+In biomechanics, some trials or traces may not be suitable for analysis and require exclusion. A missed marker, an incorrect force plate assignment, or an unexpected movement during a trial can all introduce noise into the results. Rather than deleting these trials outright, Sift allows users to flag them for exclusion, which keeps the analysis clean while preserving the original data.
 Data cleaning is an ongoing process, and exclusions can be revisited at any time as new issues are identified.
@@ Line 7: / Line 7: @@
 ===== How Exclusions Work =====
-Excluding a trace removes it from analysis (and optionally, plots), but does not delete the underlying data. Exclusions can be undone at any time using Ctrl+Z or by right-clicking a workspace and selecting Re-Include Data, and excluded traces can be toggled back on to review them alongside valid data.
+Excluding a trace removes it from analysis (and optionally, plots), but does not delete the underlying data. Exclusions can be undone at any time using Ctrl+Z or by right-clicking a workspace and selecting Re-Include Data, and visibility of excluded traces can be toggled back on to review them alongside valid data.
 Sift supports three levels of exclusion:
   * **Individual trace**: exclude a single signal cycle only
+{{:sift:application:individual_trace_exclusion.png?400|Individual trace exclusion}}
   * **All traces at those frames**: exclude all queried signals during the same cycle
-  * **Entire trial**: exclude all data from the affected trial
-===== Writing Exclusions Back to the Data =====
+{{:sift:application:traces_at_frames_exclusion.png?400|Exclude traces by frames}}
-Once exclusions have been identified, they can be written back to the original workspace files. This is done by adding a "Bad" event, using one of the three methods:
+  * **Entire trial**: exclude all data from the affected trial
-  * Only exclude individual traces: the narrowest option. An event like AnkleAngle_BAD is created during the bad cycle, and the group definition for AnkleAngle then excludes any sequences containing that event. has-motion So only that specific signal on that specific cycle is flagged.
+{{:sift:application:entire_trial_exclusion.png?400|Exclude entire trial}}
-  * Exclude all traces for this side: a mid-level option. An event is created for all queried signals during the specified cycle, but only on the same side of the body (R/L). has-motion Useful if, say, a right-side marker dropout corrupts all right-side kinematics for that cycle.
-  * Exclude all traces regardless of side: the broadest option. An event is created for all queried signals during that cycle, regardless of side. has-motion Use this when the entire trial/cycle is compromised.
-See the [[sift:application:update_cmzs_dialog|excluded_traces]] section of the Update CMZs Dialog.
+===== Writing Exclusions Back to the Data  (Optional) =====
+Once exclusions have been identified, they can be written back to the original workspace files using the [[sift:application:update_cmzs_dialog#excluded_traces|excluded traces]] option in the Update CMZs Dialog. This is done by adding a "Bad" event using one of three methods:
-It is also possible to tag entire trials that contain excluded data, making it easy to identify and filter problematic files downstream.
+  * **Only exclude individual traces**: Flags a single signal for a single cycle. A signal-specific event (e.g. "AnkleAngle_BAD") is written to the workspace, and the group definition is updated to exclude any cycle containing that event.
+  * **Exclude all traces for this side**: Flags all queried signals on the affected side (R/L) for that cycle. Useful when an issue (such as a marker dropout) affects all same-side signals.
+  * **Exclude all traces regardless of side**: Flags all queried signals for that cycle, regardless of side. Use this when the entire cycle is compromised.
+It is also possible to tag entire trials that contain excluded data, making it easy to identify and filter problematic files downstream.
 ===== Plot Options =====
@@ Line 34: / Line 38: @@
 ===== Tutorials =====
-  * [[sift:tutorials:clean_your_data|Clean your Data]]
+[[sift:tutorials:clean_your_data|Clean your Data]]: A step-by-step walkthrough of using Sift to identify and exclude bad trials across a full dataset, using a ground reaction force quality check as an example.
-     *  A step-by-step walkthrough of using Sift to identify and exclude bad trials across a full dataset, using a ground reaction force quality check as an example.