visual3d:documentation:pipeline:metric_commands:metric_explicit
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_explicit [2024/06/19 12:51] – sgranger | visual3d:documentation:pipeline:metric_commands:metric_explicit [2024/09/20 14:10] (current) – [Expressions] wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{{{{{this command creates a metric signal explicitly. | + | ====== Metric Explicit ====== |
- | |< | + | This command creates a metric |
- | previous versions | + | < |
+ | Metric_Explicit | ||
+ | / | ||
+ | ! / | ||
+ | / | ||
+ | </ | ||
- | ====== example ====== | + | {{: |
- | this example will create a metric signal with 3 component values | + | Previous versions |
- | |< | + | ===== Example ===== |
- | ===== result ===== | + | This example will create a metric signal with 3 component values of 1, 2, 3. The resulting signal will be named **NEW_SIGNAL** and be located in the **OFFSET** folder. |
- | event_explicit_exampleresult.jpg | + | < |
+ | Metric_Explicit | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | </ | ||
- | ===== expressions ===== | + | |
- | in early implementations of this command the values in metric_value were a list of components you wanted the metric explicitly set to (see example above), and expressions were not allowed. | + | ==== Result ==== |
- | in version 6 metric_value can be an expression, but this may lead to some confusion. | + | {{: |
- | for example, | + | ==== Expressions ==== |
- | **metric_explicit** | + | In early implementations of this command |
- | ! / | + | |
- | / | + | |
- | / | + | |
- | **;** | + | |
- | **metric_explicit** | + | |
- | ! / | + | |
- | / | + | |
- | / | + | |
- | **;** | + | |
- | the processing results for the second command are: | + | |
- | metric name : metric:: | + | In version 6 Metric_Value can be an expression, but this may lead to some confusion. |
- | metric expression : | + | |
- | metric value : 1.000000 , 1.000000 ; | + | |
- | the second command be re-written as follows: | + | |
- | **metric_explicit** | + | For example, |
- | ! /result_metric_folder=processed | + | |
- | /result_metric_name=test | + | < |
- | /metric_value=[[visual3d:documentation:pipeline:expressions:overview#pipeline_parameters_using_.2b_as_delimiter|add]](metric::processed::x,1) | + | Metric_Explicit |
- | **;** | + | ! /RESULT_METRIC_FOLDER=PROCESSED |
- | the processing results for the third command are: | + | /RESULT_METRIC_NAME=X |
+ | /METRIC_VALUE=1 | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | Metric_Explicit | ||
+ | ! / | ||
+ | / | ||
+ | / | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | The processing results for the second command are: | ||
+ | |||
+ | Metric Name : METRIC:: | ||
+ | Metric Expression : | ||
+ | Metric Value : 1.000000 , 1.000000 ; | ||
+ | The second command be re-written as follows: | ||
+ | |||
+ | Metric_Explicit\\ | ||
+ | ! / | ||
+ | / | ||
+ | / | ||
+ | ;\\ | ||
+ | |||
+ | The processing results for the third command are: | ||
+ | |||
+ | Metric Name : METRIC:: | ||
+ | Metric Expression : | ||
+ | Metric Value : 2.000000 ; | ||
- | metric name : metric:: | ||
- | metric expression : | ||
- | metric value : 2.000000 ; | ||
- | }}}}}} |
visual3d/documentation/pipeline/metric_commands/metric_explicit.1718801479.txt.gz · Last modified: 2024/06/19 12:51 by sgranger