visual3d:documentation:pipeline:metric_commands:metric_time_between_events
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:metric_commands:metric_time_between_events [2024/06/17 18:20] – created sgranger | visual3d:documentation:pipeline:metric_commands:metric_time_between_events [2024/07/17 15:46] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | + | ====== Metric Time Between Events ====== | |
| - | + | ||
| Computes the time between events (or start and end of a sequence of events) as a metric. | Computes the time between events (or start and end of a sequence of events) as a metric. | ||
| Line 7: | Line 5: | ||
| **Note:** In cases where the maximum event is located at the start event (time between=0), the command metric_time_between_events will not allow zero time. This is because there could be multiple instances for that event and Visual 3D would not know which instance of that event to use for the calculation. A workaround can be found here [[Visual3D: | **Note:** In cases where the maximum event is located at the start event (time between=0), the command metric_time_between_events will not allow zero time. This is because there could be multiple instances for that event and Visual 3D would not know which instance of that event to use for the calculation. A workaround can be found here [[Visual3D: | ||
| - | ===== Metric_Time_Between_Events Command Details | + | ==== Metric_Time_Between_Events Command Details ==== |
| Below are the details for this command: | Below are the details for this command: | ||
| Line 35: | Line 33: | ||
| Below is the dialog that pops up when pipeline selection is edited by double clicking with the left mouse button. | Below is the dialog that pops up when pipeline selection is edited by double clicking with the left mouse button. | ||
| - | [[TimeBetweenEventsDlg.png]] | + | {{:TimeBetweenEventsDlg.png}} |
| **Note: Event_Sequence** - It is important to note that this command assumes that the events are specified in the correct order chronologically. | **Note: Event_Sequence** - It is important to note that this command assumes that the events are specified in the correct order chronologically. | ||
| Line 46: | Line 44: | ||
| If it is not always possible to ensure the chronological order, a series of Pipeline Commands may be necessary. | If it is not always possible to ensure the chronological order, a series of Pipeline Commands may be necessary. | ||
| - | ===== Example 1 : There is only one occurrence of E1 and E2 ===== | + | ==== Example 1 : There is only one occurrence of E1 and E2 ==== |
| Execute the **Metric_Time_Between_Events** twice in succession, once with the range E1+E2, then the second one with the range E2+E1 and set the option / | Execute the **Metric_Time_Between_Events** twice in succession, once with the range E1+E2, then the second one with the range E2+E1 and set the option / | ||
| Line 74: | Line 72: | ||
| E1+MID+E2, and | E1+MID+E2, and | ||
| E2+MID+E1 | E2+MID+E1 | ||
| - | ===== Example 2 : There is always the same number of occurrences of E1 and E2 ===== | + | ==== Example 2 : There is always the same number of occurrences of E1 and E2 ==== |
| An alternative to the **Metric Time Between Events** would be to use the command **Evaluate_Expression**. In this case you can use **Evaluate_Expression** to compute the time differences between E2 and E1. | An alternative to the **Metric Time Between Events** would be to use the command **Evaluate_Expression**. In this case you can use **Evaluate_Expression** to compute the time differences between E2 and E1. | ||
| Line 87: | Line 85: | ||
| </ | </ | ||
| - | ===== Visual3D Versions supporting Subject Prefixes | + | ==== 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 and sequences listed as command parameters should NOT contain a prefix. As each subject is processed, the event range/ | NOTE: When using events in a command, the commands will iterate across subjects contained in the current workspace. As such, events and sequences listed as command parameters should NOT contain a prefix. As each subject is processed, the event range/ | ||
| - | |||
| - | |||
visual3d/documentation/pipeline/metric_commands/metric_time_between_events.1718648444.txt.gz · Last modified: 2024/06/17 18:20 by sgranger