visual3d:documentation:pipeline:metric_commands:metric_time_of_threshold_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_threshold_from_event [2025/09/19 15:34] – wikisysop | visual3d:documentation:pipeline:metric_commands:metric_time_of_threshold_from_event [2025/09/22 18:05] (current) – [Examples] wikisysop | ||
|---|---|---|---|
| Line 82: | Line 82: | ||
| ====Examples==== | ====Examples==== | ||
| - | 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_threshold_from_event.1758296085.txt.gz · Last modified: 2025/09/19 15:34 by wikisysop