visual3d:documentation:pipeline:event_commands:event_tpr_signal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:event_commands:event_tpr_signal [2025/04/28 18:36] – wikisysop | visual3d:documentation:pipeline:event_commands:event_tpr_signal [2025/04/28 18:38] (current) – wikisysop | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Event TPR Signal ====== | ====== Event TPR Signal ====== | ||
| - | ==== Overview ==== | + | ===== Overview |
| The Event_TPR_Signal command performs pattern recognition on a signal by scanning the trial for segments that match a **Target Pattern Recognition (TPR) file**. When a segment of the trial is sufficiently similar to the pattern, an event is placed at the frame of best match. | The Event_TPR_Signal command performs pattern recognition on a signal by scanning the trial for segments that match a **Target Pattern Recognition (TPR) file**. When a segment of the trial is sufficiently similar to the pattern, an event is placed at the frame of best match. | ||
| Line 10: | Line 10: | ||
| A **pattern file** mut be available. This file defines the reference shape that Visual3D will try to match in the trial, it must also use the same signal type and coordinate structure. | A **pattern file** mut be available. This file defines the reference shape that Visual3D will try to match in the trial, it must also use the same signal type and coordinate structure. | ||
| - | ==== Pipeline Command ==== | + | ===== Pipeline Command |
| The command below is as seen on the Visual3D application, | The command below is as seen on the Visual3D application, | ||
| Line 33: | Line 33: | ||
| </ | </ | ||
| - | ==== Command Parameters ==== | + | ===== Command Parameters |
| The following table shows the command parameters and descriptions: | The following table shows the command parameters and descriptions: | ||
| Line 53: | Line 53: | ||
| - | ====Dialog==== | + | =====Dialog===== |
| A dialog will pop up when pipeline selection is edited by double clicking with the left mouse button (see diagram below). | A dialog will pop up when pipeline selection is edited by double clicking with the left mouse button (see diagram below). | ||
| Line 65: | Line 65: | ||
| * Changing the **radius** will change the number of frames used. | * Changing the **radius** will change the number of frames used. | ||
| * The parameter SIGNAL_TYPES and SIGNAL_NAMES are required parameters and need to be specified. This can be done by editing the command via the " | * The parameter SIGNAL_TYPES and SIGNAL_NAMES are required parameters and need to be specified. This can be done by editing the command via the " | ||
| - | * If you wish to save the TPR signal for further use in other cmo files for pattern matching, then use the dialog to set the parameters and then click **Save TPR Signal** button. The button will not appear until you have completed setting the parameters. After clicking the button, a browser will open and you can select a folder and filename for your TPR signal file. The file extension will be .tps. Go to [[Visual3D: | + | * If you wish to save the TPR signal for further use in other CMZ files for pattern matching, then use the dialog to set the parameters and then click **Save TPR Signal** button. The button will not appear until you have completed setting the parameters. After clicking the button, a browser will open and you can select a folder and filename for your TPR signal file. The file extension will be .tps. Go to [[Visual3D: |
| - | ==== Examples ==== | + | ===== Examples |
| The following examples will show the use of the Event_TPR_Signal command in the Visual3D application. | The following examples will show the use of the Event_TPR_Signal command in the Visual3D application. | ||
| - | ===Example 1: Matching Opposite-side Gait Events=== | + | ====Example 1: Matching Opposite-side Gait Events==== |
| In some cases, users may already have events defined for one side of the participant' | In some cases, users may already have events defined for one side of the participant' | ||
| Line 113: | Line 113: | ||
| - | ===Example 2=== | + | ====Example 2==== |
| Automatically detect right foot strike during running using the Y-axis acceleration of the right ankle, based on a template waveform. Then, save a refined version of this event’s pattern and evaluate how well it aligns with the force plate contact (`RHS`). | Automatically detect right foot strike during running using the Y-axis acceleration of the right ankle, based on a template waveform. Then, save a refined version of this event’s pattern and evaluate how well it aligns with the force plate contact (`RHS`). | ||
| Line 143: | Line 143: | ||
| ---- | ---- | ||
| - | ====Notes==== | + | =====Notes===== |
| A description of the use of TPR for determining gait events when a force platform signal is present is presented in the following article: | A description of the use of TPR for determining gait events when a force platform signal is present is presented in the following article: | ||
visual3d/documentation/pipeline/event_commands/event_tpr_signal.1745865399.txt.gz · Last modified: 2025/04/28 18:36 by wikisysop