visual3d:documentation:pipeline:metric_commands:metric_time_of_minimum_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_minimum_from_event [2024/06/17 17:07] – removed sgranger | visual3d:documentation:pipeline:metric_commands:metric_time_of_minimum_from_event [2024/07/17 15:46] (current) – created sgranger | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Metric Time of Minimum from Event ====== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **Metric_Time_Of_Minimum_From_Event** | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! /SELECT_X= | ||
+ | ! /SELECT_Y= | ||
+ | ! /SELECT_Z= | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | **;** | ||
+ | |||
visual3d/documentation/pipeline/metric_commands/metric_time_of_minimum_from_event.1718644054.txt.gz · Last modified: 2024/06/17 17:07 by sgranger