Differences

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

--- visual3d:documentation:pipeline:event_commands:automatic_gait_events [2025/02/28 19:35] – [Examples] wikisysop
+++ visual3d:documentation:pipeline:event_commands:automatic_gait_events [2025/03/03 19:27] (current) – [Command Parameters] wikisysop
@@ Line 6: / Line 6: @@
 Before running this command, the model must have segments created so that the program can recognize the left from the right. These segments are not limited to feet, they simply describe the part of body which makes contact with the force platform.
-Contact with the floor for which there are //no force platforms// can be determined using **Target Pattern Recognition (TPR)**, this will be seen in the dialog box for this command. No signals need to be provided for the TPR because Visual3D uses the kinematics of the segment making contact with the force platform.
+Contact with the floor for which there are //no force platforms// can be determined using **TPR**, this will be seen in the dialog box for this command. No signals need to be provided for the TPR because Visual3D uses the kinematics of the segment making contact with the force platform.
 ==== Pipeline Command ====
@@ Line 31: / Line 31: @@
 The following table shows the command parameters for **Version 5+**.
-|**Automatic_Gait_Events**|**Parameter Description**|
+|**Parameter**|**Parameter Description**|
 |**! /FRAME_WINDOW = 8**|The frame window used for pattern recognition (default = 8)|
 |**! /USE_TPR=TRUE**|Enables TPR Algorithm to be used to find the heelstrike (HS) and toeoff (TO).|
@@ Line 128: / Line 128: @@
 </code>
-After having simply run this pipeline, the program is able to display the following graph:
+After having run this pipeline, the program is able to display the following graph:
 \\
 {{:visual3d:documentation:pipeline:event_commands:samplegraph.png?500|}}
@@ Line 135: / Line 135: @@
 === Gait Event Acronyms ===
-Definitions of the gait event acronyms used in Visual3D are shown below.
+Definitions of gait event acronyms used in Visual3D are shown below.
-The automatic gait events command and many of the events created in the tutorials, and used in the example files have 3 (or 4) character labels that have been used consistently throughout history. The labels are divided into two categories:
+The automatic gait events command, many of the events created in the tutorials, and events used in the example files have a 3 (or 4) character label that have been used consistently throughout history. The labels are divided into two categories:
-. The kinematically based category includes:
+. Kinematic Events:
 <code>
 **RHS**= Right Heel Strike
@@ Line 147: / Line 147: @@
 </code>
-. The kinetically based category refers to those events that describe contact with a force platforms:
+. Kinetic Events:
 <code>
 **RON**= Right On
@@ Line 183: / Line 183: @@
 ;
-If_Condition
+Conditional_Statement
-/EXPRESSION=::FOOT == "LFT"
+/ITERATION_PARAMETER_NAME=LEFT
+! /EXPRESSION=::FOOT == "LFT"
+! /AS_INTEGER=TRUE
 ;
     Set_Pipeline_Parameter
@@ Line 202: / Line 204: @@
     /VALUE=LTO
     ;
-Else
+Conditional_Statement_End
+/ITERATION_PARAMETER_NAME=LEFT
+;
+Conditional_Statement
+/ITERATION_PARAMETER_NAME=RIGHT
+! /EXPRESSION=::FOOT != "LFT"
+! /AS_INTEGER=TRUE
 ;
     ! Right foot events
@@ Line 221: / Line 231: @@
     /VALUE=RTO
     ;
-End_If
+Conditional_Statement_End
+/ITERATION_PARAMETER_NAME=RIGHT
 ;