Differences

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

--- visual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats [2025/09/23 14:23] – [Notes and Examples] wikisysop
+++ visual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats [2025/09/23 17:46] (current) – [Notes and Examples] wikisysop
@@ Line 156: / Line 156: @@
 ===Example 3===
-This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "X_Stats" to the name in the /Signal_Names parameter containing values related to the X-Component of the signal; "Y_Stats" to the name in the /Signal_Names parameter containing values related to the Y-Component of the signals.;"Z_Stats" to the name in the /Signal_Names parameter containing values related to the Z-Component of the signals.
+Computing stats from force plate data for left ankle angle using **Automatic Gait Events**: This group of commands results in a metric signal being created in the SIGNAL_STATS folder for all components of the left ankle angle during a trial. The command appends the string "X_Stats" to the name in the /Signal_Names parameter containing values related to the X-Component of the signal; "Y_Stats" to the name in the /Signal_Names parameter containing values related to the Y-Component of the signals.;"Z_Stats" to the name in the /Signal_Names parameter containing values related to the Z-Component of the signals.
+Gait events describe key moments in the walking or running cycle - such as heel-strikes and toe-offs. If [[Visual3D:Documentation:Kinematics_and_Kinetics:External_Forces:Force_Assignment|Force Platform assignments]] exist for a motion trial, the **Automatic_Gait_Events** command __automatically__ detects these gait events and places an **event label** at the frames where the subject steps ON and OFF the surface of the platform.
+Start by loading any trial with force plate data for a gait cycle. First, we will use **Automatic Gait Events** to label the key events in the cycle.
+<code>
+Automatic_Gait_Events
+! /FRAME_WINDOW=8
+! /USE_TPR=TRUE
+! /TPR_EVENT_INSTANCE=1
+;
+</code>
+Next we will use **Metric Compute Gait Signal Stats** to calculate key statistics for the **left ankle angle** using the events we just defined.
 <code>
 Metric_Compute_Gait_Signal_Stats
-/SIGNAL_TYPES=
+/SIGNAL_TYPES=LINK_MODEL_BASED
-/SIGNAL_FOLDER=
+! /SIGNAL_FOLDER=ORIGINAL
-/SIGNAL_NAMES=
+/SIGNAL_NAMES=LAnkleAngle
 ! /SIGNAL_COMPONENTS=
 /COMPONENT_SEQUENCE=ALL
-/COMPUTE_LEFT_SIDE=FALSE
+/COMPUTE_LEFT_SIDE=TRUE
-/COMPUTE_RIGHT_SIDE=TRUE
+/COMPUTE_RIGHT_SIDE=FALSE
 ! /RESULT_FOLDER=SIGNAL_STATS
 ! /RHS_EVENT=RHS
@@ Line 177: / Line 191: @@
 /APPEND_COMPONENT_TO_RESULT_NAME=TRUE
 ! /MERGE_COMPONENTS=FALSE
-;/code>
+;
+</code>
+The resulting folders and data should look something like this:
+{{:visual3d:documentation:pipeline:metric_commands:lankledata.png?600|}}