visual3d:documentation:pipeline:metric_commands:metric_dot_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_dot_product [2024/06/17 18:20] – created sgranger | visual3d:documentation:pipeline:metric_commands:metric_dot_product [2025/09/18 15:53] (current) – wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Metric Dot Product ====== | ||
+ | ====Overview==== | ||
+ | This command creates a dot product of two metric vectors, it can be used to calculate helpful values like angles and work. The command acts on the active files. The **Metric Dot Product** command can be found in the **Pipeline Workshop** under the **Metric** folder. | ||
+ | ==== Pipeline Command ==== | ||
- | Creates a dot product of two metric vectors. | + | < |
+ | Metric_Dot_Product | ||
+ | ! / | ||
+ | ! / | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
- | The command acts on the active files. | + | ====Command Parameters==== |
- | [[MetricDotProductDlg.png]] | + | The following table shows the command parameters seen above and their descriptions: |
- | ===== Command Syntax ===== | + | |**RESULT_FILE**|**The file type of the result**| |
+ | |**RESULT_METRIC_FOLDER**|**The name of the result signal folder**| | ||
+ | |**RESULT_METRIC_NAME**|**The name of the result signal**| | ||
+ | |**METRIC1_FILE**|**The movement trial containing the first metric value**| | ||
+ | |**METRIC1_NAME**|**The name of the signal containing the first metric value**| | ||
+ | |**METRIC1_FOLDER**|**The name of the metric signal folder**| | ||
+ | |**DIVIDE_BY_METRIC2_LENGTH**|**(True or False) Divide the resulting signal by the length of the second metric**| | ||
+ | |**GENERATE_MEAN_AND_STDDEV**|**(True or False)Generate the mean and standard deviation for all of the metrics created**| | ||
+ | |**APPEND_TO_EXISTING_VALUES**|**(True or False)Append this list of metrics to an existing metric of the same result name**| | ||
+ | |**RETAIN_NO_DATA_VALUES**|**In cases where there is NO_DATA at an event, you need to specify the parameter / | ||
- | **Metric_Dot_Product** | + | ====Dialog==== |
- | / | + | |
- | / | + | The command can be edited in a text editor |
- | / | + | |
- | / | + | {{: |
- | / | + | |
- | / | + | The dialog box allows you to assign values |
- | / | + | |
- | / | + | === Metric_File === |
- | / | + | |
- | / | + | |
- | **;** | + | |
- | ==== Metric_File | + | |
If **Metric1_File** or **Metric2_File** are empty, Visual3D uses each active file when processing the command. | If **Metric1_File** or **Metric2_File** are empty, Visual3D uses each active file when processing the command. | ||
Line 29: | Line 54: | ||
These parameters exist because the user may want to compute the dot product relative to a signal in the GLOBAL workspace or a specified file. | These parameters exist because the user may want to compute the dot product relative to a signal in the GLOBAL workspace or a specified file. | ||
- | ==== Divide_By_Metric2_Length | + | === Divide_By_Metric2_Length === |
When this is true, a unit vector of Metric2 is used. | When this is true, a unit vector of Metric2 is used. | ||
- | ==== Append_to_Existing_Values | + | === Append_to_Existing_Values === |
The results are concatenated to an existing signal. | The results are concatenated to an existing signal. | ||
+ | ====Examples==== | ||
+ | |||
+ | ===Simple example=== | ||
+ | |||
+ | Showing functionality of the command, using a diagram possibly to show output. | ||
+ | |||
+ | ===Complex example=== | ||
+ | |||
+ | Combine with other commands and show step-by-step process for frequent use case | ||
visual3d/documentation/pipeline/metric_commands/metric_dot_product.1718648431.txt.gz · Last modified: 2024/06/17 18:20 by sgranger