Differences

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

--- visual3d:tutorials:events:gait_events [2024/11/29 14:35] – sgranger
+++ visual3d:tutorials:events:gait_events [2024/11/29 18:50] (current) – sgranger
@@ Line 1: / Line 1: @@
 ====== Gait Events ======
 Gait Events, such as //Heel Strike// and //Toe Off//, are commonly used to identify gait cycles, and normalize signals accordingly. Generally, using force platforms is the most accurate method to automatically identify gait events. However, when force platforms are not available, or due to certain gait pathologies, it is also possible to identify gait events manually. This tutorial describes the different ways to create gait events.
 ===== Gait Event Acronyms =====
 Definitions of the gait event acronyms used in Visual3D
@@ Line 22: / Line 20: @@
 \\
-All RON events are also RHS events, but RON events are only created when contact is made with a force platform. This provides a means to declare a range of data for reporting only when in contact with the force platform because Joint Moments and Joint Powers for example to not have meaningful data when the foot is in contact with ground but no ground reaction forces are measured.
+All RON events are also RHS events, but RON events are only created when contact is made with a force platform. This provides a means to declare a range of data for reporting only when in contact with the force platform because Joint Moments and Joint Powers for example do not have meaningful data when the foot is in contact with ground but no ground reaction forces are measured.
 ===== Using the Ground Reaction Force =====
 If Force Platform data exists, and if Visual3D model segments have been created, Visual3D can detect contact with the force platform and compute the appropriate event labels.
   - Open the Command Pipeline
   - Expand the **Event Creation** folder
-  - Double click with the **Left Mouse Button** on the **[[Visual3D:Documentation:Pipeline:Event_Commands:Automatic_Gait_Events|Automatic_Gait_Events]]** command\\
+  - Double click with the **Left Mouse Button** on the **[[Visual3D:Documentation:Pipeline:Event_Commands:Automatic_Gait_Events|Automatic_Gait_Events]]** command \\ {{:tutorial6_7.jpg?850}} \\
-{{:tutorial6_7.jpg}}\\
+  - Execute the Pipeline
+  - Several Events have been created and highlighted on the graphs. \\ {{:tutorial6_9.jpg?850}} \\
-  - Double click with the **Left Mouse Button** on the **Automatic_Gait_Events** command in the processing list box.\\
-{{:tutorial6_8.jpg}}\\
-  - Select the direction of gravity. For this file select **Z**
-  - Execute the Pipeline\\
-{{:tutorial6_9.jpg}}\\
-  - Several Events have been created and highlighted on the graphs.
 ===== Creating Events Manually =====
+  - Select the graph of the Z-component of the Ground Reaction Force signal by Left clicking on the graph. You will see the graph is now framed. \\ {{:tutorial6_2.jpg?850}} \\
-  - Select the graph of the Z-component of the Ground Reaction Force signal by Left clicking on the graph. You will see the graph is now framed.\\
-{{:tutorial6_2.jpg}}\\
   - To create the event, double click on the Fz force signal at the frame that the signal rises above zero.
-  - Enter the name **RON** into the popup dialog box. **RON** is a typical name used in Visual3D to indicate that the Right has contacted a force platform. **In principle** the event can be assigned any name, but when Visual3D computes Heel Strike and Toe Off automatically, the events are labeled ON and OFF.\\
+  - Enter the name **RON** into the popup dialog box. **RON** is a typical name used in Visual3D to indicate that the Right has contacted a force platform. **In principle** the event can be assigned any name, but when Visual3D computes Heel Strike and Toe Off automatically, the events are labeled ON and OFF. \\ {{:tutorial6_3.jpg?850}} \\
-{{:tutorial6_3.jpg}}\\
   - An event labeled **RON** has been added to the Event_Label data tree.
-  - To highlight this event (actually all occurrences of this event), select the RON signal with a Right Mouse Button click and select **Highlight Event on Graphs.** The Frames corresponding to RON will be highlighted in yellow on all signals in each graph.\\
+  - To highlight this event (actually all occurrences of this event), select the RON signal with a Right Mouse Button click and select **Highlight Event on Graphs.** The Frames corresponding to RON will be highlighted in yellow on all signals in each graph. \\ {{:tutorial6_4.jpg?850}} \\
-{{:tutorial6_4.jpg}}\\
 ==== Create Events Dialog ====
@@ Line 223: / Line 205: @@
 === Method 2. Velocity Based Algorithm ===
-The velocity based algorithm is essentially t=he same. The zero crossing of the first derivative to the model based items computed above (LHEEL_WRT_PELVIS, RHEEL_WRT_PELVIS, RTOE_WRT_PELVIS, and LTOE_WRT_PELVIS) are computed.
+The velocity based algorithm is essentially the same. The zero crossing of the first derivative to the model based items computed above (LHEEL_WRT_PELVIS, RHEEL_WRT_PELVIS, RTOE_WRT_PELVIS, and LTOE_WRT_PELVIS) are computed.
 <code>