visual3d:tutorials:events:kinematic_event_detection
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:tutorials:events:kinematic_event_detection [2025/06/02 20:17] – [Overview - Abstract] wikisysop | visual3d:tutorials:events:kinematic_event_detection [2025/06/02 20:33] (current) – [Workflow Outline] wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Assessing Kinematic Methods of Structuring Gait====== | ====== Assessing Kinematic Methods of Structuring Gait====== | ||
- | ===== Overview | + | ===== Overview ===== |
This tutorial is a comprehensive walkthrough of a research investigation presented at the Ontario Biomechanics Conference (OBC) 2025. | This tutorial is a comprehensive walkthrough of a research investigation presented at the Ontario Biomechanics Conference (OBC) 2025. | ||
Line 10: | Line 10: | ||
**Research Question: Are kinematic event detection methods able to reliably structure biomechanical waveforms in the gait cycle?** | **Research Question: Are kinematic event detection methods able to reliably structure biomechanical waveforms in the gait cycle?** | ||
- | The tutorial has been designed for biomechanics researchers, | + | The tutorial has been designed for biomechanics researchers, |
===== Introduction ====== | ===== Introduction ====== | ||
- | In gait analysis, the ability to structure biomechanical waveforms into gait cycles is crucial | + | In gait analysis, the ability to structure biomechanical waveforms into gait cycles is needed |
- | Traditionally, | + | Traditionally, |
- | Given these limitations, | + | Given these limitations, |
The aim of this tutorial is to present a step-by-step guide for using HAS-Motion software tools, specifically Visual3D, to process gait data and compare several kinematic-based methods against the kinetic-based gold standard. | The aim of this tutorial is to present a step-by-step guide for using HAS-Motion software tools, specifically Visual3D, to process gait data and compare several kinematic-based methods against the kinetic-based gold standard. | ||
- | ===== Dataset Description | + | ===== Data ===== |
{{: | {{: | ||
Line 33: | Line 33: | ||
This tutorial focuses exclusively on **treadmill trials** and analyzes only **left-side events** (LHS and LTO). This simplifies gait cycle definitions to the interval between two identical events on the same foot, which is essential for consistent waveform normalization. | This tutorial focuses exclusively on **treadmill trials** and analyzes only **left-side events** (LHS and LTO). This simplifies gait cycle definitions to the interval between two identical events on the same foot, which is essential for consistent waveform normalization. | ||
- | ===== Sample | + | ===== Sample |
To facilitate learning and application, | To facilitate learning and application, | ||
Line 51: | Line 51: | ||
===== Workflow Outline ====== | ===== Workflow Outline ====== | ||
- | 1. **Preprocessing in Visual3D** | + | ====1. Preprocessing in Visual3D |
The first stage involves preprocessing all participant data using the **Preprocessing_Pipeline.v3s** script. This step takes treadmill-only trials for each participant and puts them into a single CMZ file and computes joint kinematic data. | The first stage involves preprocessing all participant data using the **Preprocessing_Pipeline.v3s** script. This step takes treadmill-only trials for each participant and puts them into a single CMZ file and computes joint kinematic data. | ||
Line 57: | Line 57: | ||
During this stage, ground reaction force (GRF) data is used to automatically detect kinetic gait events, establishing a **baseline** for later comparison. Subject-specific anthropometric data (height and weight) are manually input from the provided spreadsheet. | During this stage, ground reaction force (GRF) data is used to automatically detect kinetic gait events, establishing a **baseline** for later comparison. Subject-specific anthropometric data (height and weight) are manually input from the provided spreadsheet. | ||
- | 2. **Understanding and Applying Kinematic Method Pipelines** | + | ==== 2. Understanding and Applying Kinematic Method Pipelines |
The next phase involves applying several published and custom kinematic methods to detect gait events without relying on kinetic data. | The next phase involves applying several published and custom kinematic methods to detect gait events without relying on kinetic data. | ||
Line 68: | Line 68: | ||
- | 3. **Apply and Generate Measures to Compare all Methods** | + | ==== 3. Apply and Generate Measures to Compare all Methods |
Once individual method pipelines were validated, they were consolidated into a master script (**FinalPipeline_ALL_METHODS_SEQUENCES.v3s**). This pipeline computes all gait event across all methods simultaneously and then defines gait cycles based on those events. | Once individual method pipelines were validated, they were consolidated into a master script (**FinalPipeline_ALL_METHODS_SEQUENCES.v3s**). This pipeline computes all gait event across all methods simultaneously and then defines gait cycles based on those events. | ||
Line 74: | Line 74: | ||
These durations are stored under the METRIC:: | These durations are stored under the METRIC:: | ||
- | 4. **Exporting to Python for Statistical Evaluation** | + | ==== 4. Exporting to Python for Statistical Evaluation |
Finally, the computed cycle durations are exported to an Excel file where each row represents one gait cycle instance. | Finally, the computed cycle durations are exported to an Excel file where each row represents one gait cycle instance. |
visual3d/tutorials/events/kinematic_event_detection.1748895421.txt.gz · Last modified: 2025/06/02 20:17 by wikisysop