visual3d:documentation:pipeline:metric_commands:metric_time_of_global_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_global_minimum_from_event [2024/06/19 12:51] – sgranger | visual3d:documentation:pipeline:metric_commands:metric_time_of_global_minimum_from_event [2025/09/19 15:20] (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 and kinetic calculations this is fine, because these signals only exist at motion capture frames. | + | ====== Metric Time of Global Minimum from Event ====== |
+ | ====Overview==== | ||
+ | The **Metric Time of Global Minimum from Event** command can be used to record | ||
- | 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: |
- | metrictimeofglobalminfromevent.png | + | < |
+ | Metric_Time_Of_Global_Minimum_From_Event | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
- | **metric_time_of_global_minimum_from_event** | + | ====Command Parameters==== |
- | /result_event_name= | + | |
- | ! /signal_types= | + | The following table shows the command parameters seen above and their descriptions: |
- | ! /signal_names= | + | |**/ |
- | ! /signal_folder=original | + | |**/RESULT_METRIC_VALUE=** |Value of minimum after event. |
- | ! /signal_components= | + | |**/RESULT_FOLDER=** |Name of folder designated for results. |
- | ! /frame_offset=0 | + | |**/RESULT_COMPONENTS=** |Components to be included in results. |
- | ! /time_offset= | + | |**/SIGNAL_TYPES=** |The type of signal to be processed |
- | ! /event_sequence= | + | |**/SIGNAL_NAMES=** |The name of the signal to be processed |
- | ! /exclude_events= | + | |**/SIGNAL_FOLDER** |
- | ! /event_sequence_instance=0 | + | |**/SIGNAL_COMPONENTS=** |The component of the signal to be processed |
- | ! /event_subsequence= | + | |**/FRAME_OFFSET=** |The offset (in frames) to apply to the event. |
- | ! /subsequence_exclude_events= | + | |**/TIME_OFFSET=** |The time offset (in seconds) to apply to the event. |
- | ! / | + | |**/EVENT_SEQUENCE=** |A list of events (separated by “+” signs). |
- | ! / | + | |**/EXCLUDE_EVENTS=** |This Event_Sequence must not be during the sequence requested. |
- | ! /select_x= | + | |**/EVENT_SEQUENCE_INSTANCE=** |Index of the sequence instance to evaluate (0 = all, 1 = first, etc.). |
- | ! /select_y= | + | |**/EVENT_SUBSEQUENCE=** |Optional inner event window within a broader sequence. |
- | ! /select_z= | + | |**/SUBSEQUENCE_EXCLUDE_EVENTS=** |This Event subsequence must not be during the sequence requested. |
- | ! /select_residual= | + | |**/EVENT_SUBSEQUENCE_INSTANCE=** |
- | ! /start_at_event= | + | |**/EVENT_INSTANCE=** |
- | ! / | + | |**THRESHOLD** |
- | **;** | + | |
+ | |||
+ | ====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_global_minimum_from_event.1718801490.txt.gz · Last modified: 2024/06/19 12:51 by sgranger