Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:pipeline:metric_commands:metric_minimum [2025/10/02 18:08] – [Example] wikisysop
+++ visual3d:documentation:pipeline:metric_commands:metric_minimum [2025/10/02 18:18] (current) – [Example] wikisysop
@@ Line 57: / Line 57: @@
 The dialog box allows you to assign values to the command parameters outlined above.
-====Example====
+====Example 1: Minimum Handspeed====
 In the following example, compute the Minimum Value of the derived signal **HANDSPEED** between the events **FRAME1** and **GO**, with any range containing the Event **SPEED_CHANGE** being ignored.
@@ Line 78: / Line 78: @@
+====Example 2: Minimum GRF of Trail Foot in Baseball Swing====
+Here the **Metric Minimum** command is used to find minimum vertical ground reaction force value at the trail foot in a baseball swing.
+The command is as follows:
+<code>
+Metric_Minimum
+! /RESULT_METRIC_FOLDER=PROCESSED
+/RESULT_METRIC_NAME=Minimum_Trail_GRF
+! /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE
+/SIGNAL_TYPES=FORCE
+/SIGNAL_FOLDER=ORIGINAL
+ /SIGNAL_NAMES=FP4
+/COMPONENT_SEQUENCE=Z
+/EVENT_SEQUENCE=
+/EXCLUDE_EVENTS=
+! /GENERATE_MEAN_AND_STDDEV=TRUE
+! /GENERATE_MEAN_AND_STDDEV_ACROSS_SUBJECTS=FALSE
+! /APPEND_TO_EXISTING_VALUES=FALSE
+! /CREATE_GLOBAL_MINIMUM=FALSE
+! /CREATE_TRIAL_MINIMUM=FALSE
+;
+</code>
+The resulting value for each swing can be found in the **METRIC:PROCESSED** folder and should look similar to below.
+{{:visual3d:documentation:pipeline:metric_commands:trail_grf1.png?600|}}