HAS-Motion Software Documentation

This is an old revision of the document!

---

<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| previous versions of visual3d labeled this command explicit_metric ====== example ====== 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. |<code>\\ metric_explicit\\ /result_metric_name= new_signal\\ /result_metric_folder= offset\\ /metric_value= 1+2+3\\ ;\\ </code> | event_explicit_example.jpg| ===== result ===== event_explicit_exampleresult.jpg ===== 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. in version 6 metric_value can be an expression, but this may lead to some confusion. for example, **metric_explicit** ! /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 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: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 ; }}}}