visual3d:documentation:pipeline:event_commands:event_save_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_save_tpr_signal [2025/04/28 18:22] – wikisysop | visual3d:documentation:pipeline:event_commands:event_save_tpr_signal [2025/04/29 14:02] (current) – [Dialog] wikisysop | ||
---|---|---|---|
Line 49: | Line 49: | ||
{{: | {{: | ||
- | These options are reflected | + | * **File Name**: The name of the output where the TPR signal will be saved. |
+ | * **Pattern File**: File with applied TPR used to generate events | ||
+ | * **Display Short Filenames**: | ||
+ | * **Pattern Type**: The type of signal which the TPR algorithm is applied to (ANALOG, LINK_MODEL_BASED, | ||
+ | * **Pattern Folder**: Folder name where the pattern signal is stored. | ||
+ | * **Pattern Signal Name**: Name of signal which has the TPR algorithm applied to it. | ||
+ | * **Pattern Event**: Event which TPR algorithm bases off of. | ||
+ | * **Event Instance**: Specifies which instance of the event to label. | ||
+ | * **Radius Samples**: Defines the width of the matching window around the event in samples. | ||
=====Examples===== | =====Examples===== | ||
The following example shows the use of Event_Save_TPR_Signal command in the Visual3D application. | The following example shows the use of Event_Save_TPR_Signal command in the Visual3D application. | ||
Line 59: | Line 67: | ||
This command, **Event_Save_TPR_Signal** provides a way save that pattern file to serve as a **template** (e.g. you need to apply the command to multiple files to generate opposite side events). | This command, **Event_Save_TPR_Signal** provides a way save that pattern file to serve as a **template** (e.g. you need to apply the command to multiple files to generate opposite side events). | ||
- | In the case of this example, the TPR signal used LHS events to determine RHS events from the opposite foot. So the process would be that you select a file with LHS Events, select a specific trial and fill in the other information | + | In the case of this example, the TPR signal used LHS events to determine RHS events from the opposite foot. So the process would be that you select a file with LHS Events, select a specific trial and fill in the other parameters |
< | < | ||
Event_Save_TPR_Signal | Event_Save_TPR_Signal | ||
- | ! /FILE_NAME= | + | /FILE_NAME=C:/ |
/ | / | ||
/ | / | ||
Line 74: | Line 82: | ||
</ | </ | ||
- | This can now be used as the pattern file when looking to specify right side events or apply LHS events to a file that does not have any yet. | + | This can now be used as the pattern file when looking to specify right side events or apply LHS events to a file that does not have any yet. This file can be used via the [[visual3d: |
- | |||
- | |||
- | ====Notes==== | ||
visual3d/documentation/pipeline/event_commands/event_save_tpr_signal.1745864552.txt.gz · Last modified: 2025/04/28 18:22 by wikisysop