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/06/19 12:51] – sgranger | visual3d:documentation:pipeline:metric_commands:metric_time_of_maximum_from_event [2025/09/19 14:14] (current) – wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{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 | + | ====== Metric Time of Maximum from Event ====== |
+ | ====Overview==== | ||
+ | The **Metric Time of Maximum from Event** command can be used to compute | ||
- | for measures of timing that involve signals that are at analog rate (e.g. force platform data) the motion capture rate isn't sufficient. | + | ====Pipeline Command==== |
- | in version 5 a series of metric commands were introduced to identify the time of a threshold crossing or maximum at the analog rate. | + | The command syntax is as follows: |
- | metrictimeofmaximumfromevent.png | + | < |
- | + | **Metric_Time_Of_Maximum_From_Event** | |
- | **metric_time_of_maximum_from_event** | + | /RESULT_EVENT_NAME= |
- | /result_event_name= | + | ! /SIGNAL_TYPES= |
- | ! /signal_types= | + | ! /SIGNAL_NAMES= |
- | ! /signal_names= | + | ! /SIGNAL_FOLDER=ORIGINAL |
- | ! /signal_folder=original | + | ! /SIGNAL_COMPONENTS= |
- | ! /signal_components= | + | ! /FRAME_OFFSET=0 |
- | ! /frame_offset=0 | + | ! /TIME_OFFSET= |
- | ! /time_offset= | + | ! /EVENT_SEQUENCE= |
- | ! /event_sequence= | + | ! /EXCLUDE_EVENTS= |
- | ! /exclude_events= | + | ! /EVENT_SEQUENCE_INSTANCE=0 |
- | ! /event_sequence_instance=0 | + | ! /EVENT_SUBSEQUENCE= |
- | ! /event_subsequence= | + | ! /SUBSEQUENCE_EXCLUDE_EVENTS= |
- | ! /subsequence_exclude_events= | + | ! /EVENT_SUBSEQUENCE_INSTANCE=0 |
- | ! /event_subsequence_instance=0 | + | ! /EVENT_INSTANCE=0 |
- | ! /event_instance=0 | + | ! /SELECT_X= |
- | ! /select_x= | + | ! /SELECT_Y= |
- | ! /select_y= | + | ! /SELECT_Z= |
- | ! /select_z= | + | ! /SELECT_RESIDUAL= |
- | ! /select_residual= | + | ! /START_AT_EVENT= |
- | ! /start_at_event= | + | ! /END_AT_EVENT= |
- | ! /end_at_event= | + | ! /FRAME_WINDOW=8 |
- | ! /frame_window=8 | + | |
**;** | **;** | ||
+ | </ | ||
+ | |||
+ | ====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.1718801490.txt.gz · Last modified: 2024/06/19 12:51 by sgranger