visual3d:documentation:pipeline:metric_commands:metric_time_of_maximum_from_event
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_of_maximum_from_event [2024/07/03 17:41] – created sgranger | visual3d:documentation:pipeline:metric_commands:metric_time_of_maximum_from_event [2025/09/19 14:14] (current) – wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | ====Overview==== | ||
+ | The **Metric Time of Maximum from Event** command can be used to compute the time between an event and a maximum signal. For example, this command could be used to determine the time between initial foot contact with the ground and max grf. The command can be found in the **Pipeline Workshop** under **Metric**. | ||
- | Event_Labels are defined by the c3d format. Event_Labels exist only at Motion Capture frames (e.g. at Point Rate). For model based kinematic and kinetic calculations this is fine, because these signals only exist at Motion Capture frames. | + | ====Pipeline Command==== |
- | For measures of timing that involve signals that are at ANALOG rate (e.g. Force Platform data) the motion capture rate isn't sufficient. | + | The command syntax is as follows: |
- | + | ||
- | In Version 5 a series of metric commands were introduced to identify the time of a threshold crossing or maximum at the analog rate. | + | |
- | + | ||
- | {{MetricTimeofMaximumfromEvent.png}} | + | |
+ | < | ||
**Metric_Time_Of_Maximum_From_Event** | **Metric_Time_Of_Maximum_From_Event** | ||
/ | / | ||
Line 32: | Line 31: | ||
! / | ! / | ||
**;** | **;** | ||
+ | </ | ||
+ | |||
+ | ====Command Parameters==== | ||
+ | |||
+ | The following table shows the command parameters seen above and their descriptions: | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**/ | ||
+ | |**START_AT_EVENT=** | ||
+ | |**/ | ||
+ | |**FRAME_WINDOW** | ||
+ | |||
+ | ====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. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | The dialog box allows you to assign values to the command parameters outlined above. | ||
+ | |||
+ | ====Notes==== | ||
+ | |||
+ | Event_Labels are defined by the c3d format. Event_Labels exist only at Motion Capture frames (e.g. at Point Rate). For model based kinematic and kinetic calculations this is fine, because these signals only exist at Motion Capture frames. | ||
+ | |||
+ | For measures of timing that involve signals that are at ANALOG rate (e.g. Force Platform data) the motion capture rate isn't sufficient. | ||
+ | |||
+ | In Version 5 a series of metric commands were introduced to identify the time of a threshold crossing or maximum at the analog rate. | ||
+ | ====Examples==== | ||
visual3d/documentation/pipeline/metric_commands/metric_time_of_maximum_from_event.1720028516.txt.gz · Last modified: 2024/07/03 17:41 by sgranger