visual3d:documentation:pipeline:event_commands:event_threshold
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_threshold [2025/02/27 17:44] – [Event Threshold] wikisysop | visual3d:documentation:pipeline:event_commands:event_threshold [2025/04/29 13:39] (current) – [Dialog] wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Event Threshold ====== | ====== Event Threshold ====== | ||
- | ==== Overview ==== | + | ===== Overview |
- | The **Event_Threshold** command is used to detect threshold crossings in biomechanical | + | The **Event_Threshold** command is used to detect threshold crossings |
- | **Place an event label at the frame where a signal | + | This command is particularly useful for defining critical events based on signal |
- | **This is a complicated command because there are so many options.** | + | **Note**: The threshold parameter specified can be a number, a PROCESSED METRIC, or an expression. |
- | ==== Command | + | ===== Pipeline |
+ | The command below is as seen on the Visual3D application, | ||
< | < | ||
Event_Threshold | Event_Threshold | ||
- | / | + | / |
- | ! /Signal_Types= The type of signal to be evaluated | + | ! /SIGNAL_TYPES= |
- | ! /SIGNAL_NAMES= The name of the signal to be evaluated | + | ! /SIGNAL_FOLDER=ORIGINAL |
- | ! /Signal_Folder= The name of the signal folder | + | ! /SIGNAL_NAMES= |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | ! / | + | ! / |
- | A value of 0 results in all crossing being assigned a label. | + | ! / |
- | A positive number indicates the event (in sequence) to select. | + | ! / |
- | A negative number indicates the event starting from the last event and progressing to the first event. | + | ! / |
- | ! /SELECT_X= (True or False)Use this component of the signal | + | ! /FRAME_WINDOW=8 |
- | ! /SELECT_Y= (True or False)Use this component of the signal | + | ! / |
- | ! /SELECT_Z= (True or False)Use this component of the signal | + | ! / |
- | ! / | + | ; |
- | ! / | + | |
- | ! / | + | |
- | ! / | + | |
- | ! / | + | |
- | ! / | + | |
- | ! /Frame_Window= The range of frames of data that must satisfy the threshold crossing. Used by the " | + | |
- | ! / | + | |
- | ! / | + | |
</ | </ | ||
- | {{: | ||
+ | ===== Command Parameters ===== | ||
+ | The following table shows the command parameters and descriptions: | ||
- | ==== THRESHOLD | + | |**Parameter** |
+ | |**/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/THRESHOLD=**|Threshold value to trigger event detection.| | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
- | The Threshold parameter | + | ===== Dialog ===== |
+ | The command | ||
- | **a number** | + | {{: |
- | **a PROCESSED METRIC** | + | |
- | **an expression** | + | |
- | For example: | + | * **New Event Label Name**: Name to assign event that reaches threshold value. |
+ | * **Signal Component**: | ||
+ | * **Frame Window**: Number of frames to check for threshold condition. | ||
+ | * **Frame Offset**: Shift event by a specified number of frames. | ||
+ | * **Time Offset**: Shift event by time (in seconds). | ||
+ | * **Threshold**: | ||
+ | * **Event Instance**: Specify which instance of the event to label. (0 = all) | ||
+ | * **Label on Ascent/ | ||
+ | * **Ensure Window Before/ | ||
+ | * **Event Sequence**: Specify range in which to search for threshold crossings. | ||
+ | * **Event Subsequence**: | ||
- | **a number**\\ | ||
- | /Threshold= 1 | ||
- | **a PROCESSED METRIC**\\ | ||
- | If a METRIC value is stored in the PROCESSED folder, the Event_Threshold command will recognize and use the signal based only on the signal name.\\ | ||
- | Given a METRIC signal named THRESH stored in the PROCESSED folder, you can specify the parameter as:\\ | ||
- | /Threshold= THRESH | ||
- | **an expression**\\ | ||
- | It is also possible to use expressions, | ||
- | Given a METRIC signals THRESH that is stored in a folder labeled TEST\\ | + | ===== Examples ===== |
- | /Threshold= METRIC:: | + | The following examples will go through the use of the Event_Threshold command in the Visual3D application. |
- | But you can also elaborate this expression, such as\\ | + | ==== Example |
- | /Threshold= 1.0 + 0.2 * METRIC:: | + | This example uses the **Event_Threshold** command to detect the event Max_GRF when the vertical ground reaction force (GRF_Z) crosses 1000N in the ascending direction: |
- | ==== Example | + | < |
- | + | Event_Threshold | |
- | **Create events using the Event_Threshold command**: **FP3_Y and FP3_Y_ENSURE** | + | / |
+ | / | ||
+ | ! / | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | /THRESHOLD= 1000 | ||
+ | /ON_ASCENT= TRUE | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
- | The event **FP3_Y_ENSURE** will use the Ensure Window After option | + | ==== Example 2: Maintaining Event Window after Threshold Closing ==== |
+ | In this example, the events **FP3_Y** and **FP3_Y_ENSURE** are created using the command. | ||
- | **Make sure to:**\\ | + | To ensure correct functionality of the example, the following must be done: |
- | 1) Import the SIGNAL_TYPE/ | + | |
- | 2) Only one signal component | + | - Specify only one signal component at a time. |
- | 3) Select label on Ascent/ | + | - One of either **ON_ASCENT** or **ON_DESCENT** must be selected, |
< | < | ||
Line 112: | Line 149: | ||
/ | / | ||
; | ; | ||
- | </ | ||
- | {{: | ||
- | < | ||
Event_Threshold | Event_Threshold | ||
/ | / | ||
Line 145: | Line 179: | ||
; | ; | ||
</ | </ | ||
- | {{: | ||
- | === Example - Result === | + | === Result === |
+ | After running this pipeline, you will notice 3 events have been created: | ||
+ | * 2 instances of **FP3_Y**, crosses the threshold (0.05) two times during the trial. | ||
+ | * 1 instance of **FP3_Y_ENSURE**, | ||
- | Three events should be created: | + | {{:EventThreshold_FP3_Y_Ensure_Graph.jpg}} |
- | 2 Instances of **FP3_Y** -The FP3_Y signal crosses the threshold (0.05) two times during the trial | ||
- | 1 Instance of **FP3_Y_ENSURE** -The FP3_Y signal crosses the threshold (0.05) and stays above the threshold for the frame window (25) one time during the trial |{{: | + | ===== Notes ===== |
- | ==== Visual3D Versions supporting Subject Prefixes | + | === Visual3D Versions supporting Subject Prefixes === |
When defining events for subjects that use a prefix to define the data belonging to that subject, event labels will also have the prefix of the subject the events belong to. | When defining events for subjects that use a prefix to define the data belonging to that subject, event labels will also have the prefix of the subject the events belong to. |
visual3d/documentation/pipeline/event_commands/event_threshold.1740678256.txt.gz · Last modified: 2025/02/27 17:44 by wikisysop