Table of Contents

Event TPR Signal

Overview

- Describe the functionality of the command

- Placement within pipeline folders

- Use cases

- Requirements for use (i.e gait event labels can only be used if force assignments exist)

Pipeline Command

Event_TPR_Signal
/SIGNAL_TYPES=
! /SIGNAL_FOLDER=ORIGINAL
/SIGNAL_NAMES=
! /PATTERN_FILE=
! /PATTERN_TYPE=
! /PATTERN_FOLDER=ORIGINAL
! /PATTERN_SIGNAL=
/PATTERN_EVENT_NAME=
! /PATTERN_EVENT_INSTANCE=1
! /SELECT_X=FALSE
! /SELECT_Y=FALSE
! /SELECT_Z=FALSE
! /TPR_WINDOW=7
! /TOLERANCE=20.0
/EVENT_NAME=
;

Command Parameters

The following table shows the command parameters and descriptions:

Parameter Description
/SIGNAL_TYPE=Specifies the type of signal being analyzed (Analog, Link Model Based, etc.)
! /SIGNAL_FOLDER=ORIGINALThe folder where the signal is stored.
/SIGNAL_NAMES=Defines the specific signal name within the selected type
! /PATTERN_FILE=
! /PATTERN_TYPE=
! /PATTERN_FOLDER=ORIGINAL
! /PATTERN_SIGNAL=
/PATTERN_EVENT_NAME=
! /PATTERN_EVENT_ISNTANCE=1
! /SELECT_(X,Y,Z)=FALSEDetermines which component of the signal should be evaluated (TRUE/FALSE)
! /TPR_WINDOW=7Set number of windows which the TPR algorithm will base it's predictions off of.
! /TOLERANCE=20.0“Goodness of fit” for the match.
/EVENT_NAME=The Event Name to be placed on the labels for the generated events.

Dialog

The command can be edited in a text editor or in a dialog form. To edit in the dialog pop up form either click on the Edit button in the pipeline workshop or double-click on the pipeline command. The dialog is shown below.

Examples

Simple example

Showing functionality of the command, using a diagram possibly to show output.

Complex example

Combine with other commands and show step-by-step process for frequent use case

Notes

- Important considerations (anything included in the page before the reformat)