Event Define Event Sequence: Difference between revisions
No edit summary |
No edit summary |
||
Line 53: | Line 53: | ||
:! /APPEND_TO_EXISTING_VALUES=FALSE | :! /APPEND_TO_EXISTING_VALUES=FALSE | ||
:''';''' | :''';''' | ||
==Visual3D Versions supporting Subject Prefixes== | |||
NOTE: When using events in a command, the commands will iterate across subjects contained in the current workspace. As such, events being created should list the generic event label name, and as the event command iterates through subjects, it will create the subject specific events that are prefixed with the specific subject prefix. | |||
In commands using event labels and event sequences to process data, the event labels and sequences listed to process between should be generic (without a subject prefix), and as each subject is processed, the event range/sequence specified will automatically use the specific events prefixed for each subject as they are processed. |
Latest revision as of 18:48, 9 November 2021
Defining an Event_Sequence as a single command parameter.
This option provides the flexibility to set offsets on the Event_Sequence and to embed an Event Sequence inside another event.
- Event_Define_Event_Sequence
- /EVENT_SEQUENCE_NAME=RSTANCE
- /EVENT_SEQUENCE=RON+ROFF
- ! /EXCLUDE_EVENTS=
- ! /INSIDE_OF_SEQUENCE=
- /OFFSET_FROM_START=-1
- ! /OFFSET_FROM_END=
- /OFFSET_BY=FRAMES
- /EVENT_SEQUENCE_INSTANCE=0
- ;
This event sequence will start one frame before the sequence RON+ROFF
The resulting signal can be used wherever an Event_Sequence is used.
For example, Metric_Mean
Instead of the following syntax:
- Metric_Mean
- /RESULT_METRIC_NAME=_MEAN
- /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=TRUE
- ! /RESULT_METRIC_FOLDER=PROCESSED
- /SIGNAL_TYPES=LINK_MODEL_BASED
- /SIGNAL_NAMES=RKNEE_ANGLE
- ! /SIGNAL_FOLDER=ORIGINAL
- ! /SIGNAL_COMPONENTS=ALL_COMPONENTS
- /EVENT_SEQUENCE=RON+ROFF
- /EXCLUDE_EVENTS=
- ! /GENERATE_MEAN_AND_STDDEV=TRUE
- ! /APPEND_TO_EXISTING_VALUES=FALSE
- ;
you could use
- Metric_Mean
- /RESULT_METRIC_NAME=_MEAN
- /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=TRUE
- ! /RESULT_METRIC_FOLDER=PROCESSED
- /SIGNAL_TYPES=LINK_MODEL_BASED
- /SIGNAL_NAMES=RKNEE_ANGLE
- ! /SIGNAL_FOLDER=ORIGINAL
- ! /SIGNAL_COMPONENTS=ALL_COMPONENTS
- /EVENT_SEQUENCE=RSTANCE
- /EXCLUDE_EVENTS=
- ! /GENERATE_MEAN_AND_STDDEV=TRUE
- ! /APPEND_TO_EXISTING_VALUES=FALSE
- ;
Visual3D Versions supporting Subject Prefixes
NOTE: When using events in a command, the commands will iterate across subjects contained in the current workspace. As such, events being created should list the generic event label name, and as the event command iterates through subjects, it will create the subject specific events that are prefixed with the specific subject prefix.
In commands using event labels and event sequences to process data, the event labels and sequences listed to process between should be generic (without a subject prefix), and as each subject is processed, the event range/sequence specified will automatically use the specific events prefixed for each subject as they are processed.