visual3d:documentation:pipeline:metric_commands:metric_cross_product
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_cross_product [2025/09/18 15:14] – wikisysop | visual3d:documentation:pipeline:metric_commands:metric_cross_product [2025/10/03 17:35] (current) – [Example: Computing Step Length from Stride Vectors Using Dot Product] wikisysop | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The Metric Cross Product command is used to create a cross product of two metric vectors. This could include finding the torque acting on a joint or other similar uses. The command can be found within the **Pipeline Workshop** in the **Metric** folder. The command acts on the active files. | The Metric Cross Product command is used to create a cross product of two metric vectors. This could include finding the torque acting on a joint or other similar uses. The command can be found within the **Pipeline Workshop** in the **Metric** folder. The command acts on the active files. | ||
| - | {{: | + | ====Pipeline Command==== |
| + | |||
| + | The command, as seen in the pipeline workshop, is below. | ||
| < | < | ||
| Metric_Cross_Product | Metric_Cross_Product | ||
| + | ! / | ||
| + | ! / | ||
| / | / | ||
| - | ! / | ||
| ! / | ! / | ||
| + | ! / | ||
| / | / | ||
| - | ! / | ||
| ! / | ! / | ||
| - | /METRIC2_NAME= | + | ! /METRIC2_FOLDER=PROCESSED |
| - | ! /METRIC2_FOLDER= | + | /METRIC2_NAME= |
| - | ! / | + | ! / |
| - | ! / | + | ! / |
| - | ! / | + | ! / |
| - | ! / | + | ! / |
| - | ! / | + | ! / |
| ; | ; | ||
| </ | </ | ||
| Line 37: | Line 40: | ||
| |**APPEND_TO_EXISTING_VALUES**|**(True or False)Append this list of metrics to an existing metric of the same result name**| | |**APPEND_TO_EXISTING_VALUES**|**(True or False)Append this list of metrics to an existing metric of the same result name**| | ||
| |**GENERATE_VECTOR_LENGTH_METRIC**|**(True or False)Generate metric value for vector length**| | |**GENERATE_VECTOR_LENGTH_METRIC**|**(True or False)Generate metric value for vector length**| | ||
| - | |**RETAIN_NO_DATA_VALUES**|**(True or False)**| | + | |**RETAIN_NO_DATA_VALUES**|**In cases where there is NO_DATA at an event, you need to specify the parameter / |
| ====Dialog==== | ====Dialog==== | ||
| Line 60: | Line 63: | ||
| The results are concatenated to an existing signal. | The results are concatenated to an existing signal. | ||
| - | ====Examples==== | + | ====Example: Computing Step Length from Stride Vectors Using Dot Product==== |
| + | In this example the **Metric Cross Product** command is used along with **Metric Vector Between Events** and **Automatic Gait Events** to find the width of each step in a gait trial. | ||
| - | ===Simple example=== | + | First all files are selected as active and key gait events are defined for each trial: |
| - | Showing functionality of the command, using a diagram possibly to show output. | + | < |
| + | Select_Active_File | ||
| + | / | ||
| + | ; | ||
| - | ===Complex example=== | + | Automatic_Gait_Events |
| + | ! / | ||
| + | ! /USE_TPR=TRUE | ||
| + | ! / | ||
| + | ; | ||
| + | </ | ||
| + | |||
| + | Next **Metric Vector Between Events** is used twice for each side to define vectors for the proximal end of each foot between gait events: | ||
| + | |||
| + | < | ||
| + | Metric_Vector_Between_Events | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | ! / | ||
| + | ; | ||
| + | |||
| + | Metric_Vector_Between_Events | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | ! / | ||
| + | / | ||
| + | ! / | ||
| + | ; | ||
| + | |||
| + | Metric_Vector_Between_Events | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | ; | ||
| + | |||
| + | Metric_Vector_Between_Events | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | ; | ||
| + | </ | ||
| + | |||
| + | Now that the vectors for the feet have been defined, **Metric Cross Product** can be used to compute the dot product of those vectors and determine the step width for each stride: | ||
| + | |||
| + | < | ||
| + | ! Calculate LeftStepWidth by taking cross product of LeftStep vector and StrideVectors_MEAN | ||
| + | ! Generate Mean and STD DEV | ||
| + | Metric_Cross_Product | ||
| + | ! / | ||
| + | / | ||
| + | ! / | ||
| + | / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | ! / | ||
| + | / | ||
| + | ; | ||
| + | |||
| + | ! Calculate RightStepWidth by taking cross product of RightStep vector and StrideVectors_MEAN | ||
| + | ! Generate Mean and STD DEV | ||
| + | Metric_Cross_Product | ||
| + | ! / | ||
| + | / | ||
| + | ! / | ||
| + | / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | / | ||
| + | ! / | ||
| + | ! / | ||
| + | ! / | ||
| + | / | ||
| + | ; | ||
| + | </ | ||
| - | Combine with other commands | + | The **METRIC: |
| + | {{: | ||
| + | A more complete example including dot products is available [[visual3d: | ||
visual3d/documentation/pipeline/metric_commands/metric_cross_product.1758208468.txt.gz · Last modified: 2025/09/18 15:14 by wikisysop