The Event_Copy command allows users to create a new event by copying an existing event and applying optional modifications. Users can specify an offset for the copied event in terms of frames, time or percentage of a defined range. Additionally, users can control the sequence of copied events, exclude certain events from copying, or define specific start and end events for more refined event duplication.

This command is particularly useful for scenarios where new events need to be derived from existing ones while maintaining precise temporal relationships.

The functionality of this command can also be achieved by right-clicking the event label within the data tree and selecting the “Event Copy” from the context menu. The interactive selection from the data tree is shown below:

The command below is the command as seen in the Visual3D application.

/EVENT_NAME=
/NEW_EVENT_NAME=
!/EVENT_INSTANCE=0
!/EVENT_INSTANCE_AS_LIST=FALSE
!/RANGE_INSTANCE=0
!/EVENT_SEQUENCE=
!/START_AT_EVENT=
!/END_AT_EVENT=
!/FRAME_OFFSET=
!/TIME_OFFSET=
!/PERCENT_OFFSET=

The following table shows the command parameters and descriptions:

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.

• Optional- Select Range Instance:

When set to 0, copies all instances of the event. When set to n, copy the nth instance of the event. If n<1, count instances from the last event; e.g. -1 = last instance.

• Optional - Select Event Instance:

When set to 0, it means all occurrences of the event will be processed. When Interpret Event Instance As List is checked, the event is treated as a list rather than a single value.

The following examples will go through the use of the Event_Copy command in the Visual3D application.

The stance phase of the gait cycle is the period when the foot is in contact with the ground, it is defined by the labels RON and ROFF. The following command will create an event mid way between RON and ROFF.

Event_Copy
/EVENT_NAME=RON
/NEW_EVENT_NAME=MID_STANCE
!/FRAME_OFFSET=
!/TIME_OFFSET=
/PERCENT_OFFSET=50
!/EVENT_INSTANCE=0
!/RANGE_INSTANCE=0
/EVENT_SEQUENCE=RON+ROFF
!/EXCLUDE_EVENTS=
!/START_AT_EVENT=
!/END_AT_EVENT=
;

The dialog corresponding to the example command is shown below:

This command will use all instances of a range defined by the Event_Sequence and Exclude_Event, and will use every occurrence of the Event_Name within this sequence.

The event sequence used in the Event_Copy command includes the first event, but not the last event. This idiosyncratic behavior was introduced to handle sequences that had the same event label name at each end of the sequence.

In order to copy the last event, you need to select the first event and an offset of 100%. For example, given a sequence of events A-B-C and you want to copy Event C and name it C2.

Event_Copy
/EVENT_NAME=A
/NEW_EVENT_NAME=C2
!/FRAME_OFFSET=
!/TIME_OFFSET=
/PERCENT_OFFSET=100
!/EVENT_INSTANCE=0
!/RANGE_INSTANCE=0
/EVENT_SEQUENCE=A+B+C
!/EXCLUDE_EVENTS=
!/START_AT_EVENT=
!/END_AT_EVENT=
;

In this example, an event named BAD is created if the time between two events (RHS→ RHS) exceeds a threshold. The following is the breakdown of the command:

1. Define a Stride: the time between two consecutive RHS.
2. Measure Stride Time: Calculates the duration of each STRIDE.
3. Identify Long Strides: Checks if any STRIDE duration is longer than 4 seconds, if this is the case, it is flagged.
4. Mark as “BAD”: For each stride that's longer than 4 seconds, it creates a new event called “BAD” at the time of the second RHS.

! Define an Event Sequence
Event_Define_Event_Sequence
/EVENT_SEQUENCE_NAME=STRIDE
/EVENT_SEQUENCE=RHS+RHS
!/EXCLUDE_EVENTS=
!/INSIDE_OF_SEQUENCE=
!/OFFSET_FROM_START=
!/OFFSET_FROM_END=
!/OFFSET_BY=PERCENT
/EVENT_SEQUENCE_INSTANCE=0
;

! Compute the times of the Event_Sequence
Metric_Time_Between_Events
/RESULT_METRIC_NAME=STRIDE_TIME
!/RESULT_METRIC_FOLDER=PROCESSED
/EVENT_SEQUENCE=STRIDE
/EXCLUDE_EVENTS=
/GENERATE_MEAN_AND_STDDEV=FALSE
!/APPEND_TO_EXISTING_VALUES=FALSE
;

! Create a binary signal from the stride time and threshold (4 in this case)
Evaluate_Expression
/EXPRESSION=(METRIC::PROCESSED::STRIDE_TIME>4)
!/SIGNAL_TYPES=
!/SIGNAL_FOLDER=ORIGINAL
!/SIGNAL_NAMES=
/RESULT_TYPES=METRIC
!/RESULT_FOLDERS=PROCESSED
/RESULT_NAME=STRIDE_TIME_BINARY
!/APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE
;

! Create a pipeline parameter from the binary signal
Set_Pipeline_Parameter_To_Data_Value
/SIGNAL_TYPES=METRIC
/SIGNAL_FOLDER=PROCESSED
/SIGNAL_NAMES=STRIDE_TIME_BINARY
!/SIGNAL_COMPONENTS=ALL_COMPONENTS
/PARAMETER_NAME=INSTANCE
;

! Create indices for a for each loop
**Get_Pipeline_Parameter_Count**
/PARAMETER_NAME=NUMCOUNT
/PARAMETER_VALUE=::INSTANCE
;

Set_Pipeline_Parameter_From_For_Loop
/PARAMETER_NAME=COUNT
/PARAMETER_INDEX_START=1
/PARAMETER_INDEX_END=::NUMCOUNT
/PARAMETER_INDEX_STEP=1
!/PARAMETER_INDEX_TYPE=INTEGER
;

For_Each
/ITERATION_PARAMETER_NAME=INDEX
/ITEMS=::COUNT
;

! If the binary signal is 1 execute event copy
Expression_Loop
/ITERATION_PARAMETER_NAME=TEST
/EXPRESSION=METRIC::PROCESSED::STRIDE_TIME_BINARY[&::INDEX&]
/AS_INTEGER=true
;

Event_Copy
/EVENT_NAME=RHS
/NEW_EVENT_NAME=BAD
!/EVENT_INSTANCE=0
/RANGE_INSTANCE=::INDEX
/EVENT_SEQUENCE=STRIDE_TIME
!/EXCLUDE_EVENTS=
!/START_AT_EVENT=
!/END_AT_EVENT=
/FRAME_OFFSET=10
!/TIME_OFFSET=
!/PERCENT_OFFSET=
;

Expression_Loop_End
/ITERATION_PARAMETER_NAME=TEST
;

End_For_Each
/ITERATION_PARAMETER_NAME=INDEX
;

• The /Percent_Offset parameter is only effective when /Start_At_Event and /End_At_Event are specified.
• Offset values (Frame_Offset, Time_Offset, Percent_Offset) should be used cautiously to ensure event placement aligns with analysis needs.