HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » metric_commands » Metric Compute Gait Signal Stats
visual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats [2025/09/23 14:24] – [Notes and Examples] wikisysopvisual3d: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=== ===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> <code>
 Metric_Compute_Gait_Signal_Stats Metric_Compute_Gait_Signal_Stats
-/SIGNAL_TYPES= +/SIGNAL_TYPES=LINK_MODEL_BASED 
-/SIGNAL_FOLDER= +! /SIGNAL_FOLDER=ORIGINAL 
-/SIGNAL_NAMES=+/SIGNAL_NAMES=LAnkleAngle
 ! /SIGNAL_COMPONENTS= ! /SIGNAL_COMPONENTS=
 /COMPONENT_SEQUENCE=ALL /COMPONENT_SEQUENCE=ALL
-/COMPUTE_LEFT_SIDE=FALSE +/COMPUTE_LEFT_SIDE=TRUE 
-/COMPUTE_RIGHT_SIDE=TRUE+/COMPUTE_RIGHT_SIDE=FALSE
 ! /RESULT_FOLDER=SIGNAL_STATS ! /RESULT_FOLDER=SIGNAL_STATS
 ! /RHS_EVENT=RHS ! /RHS_EVENT=RHS
Line 180: Line 194:
 </code> </code>
  
 +The resulting folders and data should look something like this:
 +
 +{{:visual3d:documentation:pipeline:metric_commands:lankledata.png?600|}}
visual3d/documentation/pipeline/metric_commands/metric_compute_gait_signal_stats.1758637462.txt.gz · Last modified: 2025/09/23 14:24 by wikisysop