User Tools

Site Tools


visual3d:documentation:pipeline:metric_commands:metric_explicit

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
visual3d:documentation:pipeline:metric_commands:metric_explicit [2024/06/19 12:51] sgrangervisual3d: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 ======
  
-|<code>\\ metric_explicit\\ /result_metric_name=              name of the resulting signal\\ ! /result_metric_folder=processed name of the resulting folder\\ /metric_value=                    component value(s)\\ ;\\ </code>  |  event_explicit.jpg|+This command creates a metric signal explicitly.
  
-previous versions of visual3d labeled this command explicit_metric+<code> 
 +Metric_Explicit 
 +/RESULT_METRIC_NAME=              Name of the resulting signal 
 +! /RESULT_METRIC_FOLDER=PROCESSED Name of the resulting folder 
 +/METRIC_VALUE=                    Component Value(s); 
 +</code>  
  
-====== example ======+{{:Event_Explicit.jpg}}
  
-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.+Previous versions of Visual3D labeled this command Explicit_Metric
  
-|<code>\\ metric_explicit\\ /result_metric_namenew_signal\\ /result_metric_folderoffset\\ /metric_value1+2+3\\ ;\\ </code>  |  event_explicit_example.jpg|+===== 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+<code> 
 +Metric_Explicit 
 +/RESULT_METRIC_NAME= NEW_SIGNAL 
 +/RESULT_METRIC_FOLDER= OFFSET 
 +/METRIC_VALUE= 1+2+3; 
 +</code> 
  
-===== expressions =====+ {{:Event_Explicit_example.jpg}}
  
-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.+{{:Event_Explicit_exampleresult.jpg}}
  
-for example,+==== Expressions ====
  
-**metric_explicit** +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_metric_folder=processed +
-/result_metric_name=x +
-/metric_value=1 +
-**;** +
-**metric_explicit** +
-! /result_metric_folder=processed +
-/result_metric_name=test +
-/metric_value=metric::processed::x+1 +
-**;** +
-the processing results for the second command are:+
  
-metric name : metric::processed::test +In version 6 Metric_Value can be an expressionbut this may lead to some confusion.
-metric expression : vector(metric::processed::x,1) +
-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 +<code> 
-/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 
 +
 +</code> 
 + 
 +<code> 
 +Metric_Explicit 
 +! /RESULT_METRIC_FOLDER=PROCESSED 
 +/RESULT_METRIC_NAME=TEST 
 +/METRIC_VALUE=METRIC::PROCESSED::X+1 
 +
 +</code> 
 + 
 +The processing results for the second command are: 
 + 
 +Metric Name : METRIC::PROCESSED::TEST\\ 
 +Metric Expression : VECTOR(METRIC::PROCESSED::X,1)\\ 
 +Metric Value : 1.000000 , 1.000000 ;\\ 
 +The second command be re-written as follows: 
 + 
 +Metric_Explicit\\ 
 +! /RESULT_METRIC_FOLDER=PROCESSED\\ 
 +/RESULT_METRIC_NAME=TEST\\ 
 +/METRIC_VALUE=[[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview#Pipeline_parameters_using_.2B_as_delimiter|Add]](METRIC::PROCESSED::X,1)\\ 
 +;\\ 
 + 
 +The processing results for the third command are: 
 + 
 +Metric Name : METRIC::PROCESSED::TEST\\ 
 +Metric Expression : Add(METRIC::PROCESSED::X,1)\\ 
 +Metric Value : 2.000000 ;\\
  
-metric name : metric::processed::test 
-metric expression : add(metric::processed::x,1) 
-metric value : 2.000000 ; 
  
-}}}}}} 
visual3d/documentation/pipeline/metric_commands/metric_explicit.1718801479.txt.gz · Last modified: 2024/06/19 12:51 by sgranger