HAS-Motion Software Documentation

This is an old revision of the document!

---

1 plus]] * [[#minus|2 minus]] * [[#multiply|3 multiply]] * [[#divide|4 divide]] * [[#power|5 power]] * [[#logical_or|6 logical_or]] * [[#logical_and|7 logical_and]] * [[#equals|8 equals]] * [[#not_equals|9 not_equals]] * [[#using_the_adjective_not|10 using the adjective not]] * [[#less_than|11 less_than]] * [[#less_than_or_equals|12 less_than_or_equals]] * [[#greater_than|13 greater_than]] * [[#greater_than_or_equals|14 greater_than_or_equals]] ===== plus ===== note: pipeline command parameters use + as delimiter if the user wants to use an expression containing a + in a command parameter that allows multiple signals, visual3d will likely interpret this plus sign incorrectly. the workaround is to use a mathematical function add() to express the addition. **add(a,b)** -- adds two expressions. ===== minus ===== ===== multiply ===== ===== divide ===== ===== power ===== ===== logical_or ===== logical or ===== logical_and ===== logical and ===== equals ===== **= or ==** - boolean operator //equals// example: comparing a model metric with a string consider a model metric that is defined as a string. **set_model_metric** ! /calibration_file= /metric_name=test /metric_value="ttt" **;** now compare it to the text string "ttt" **evaluate_expression** /expression=model::metric::test="ttt" /result_name=scott /result_type=metric ! /result_folder=processed **;** the text strings should be equal so the resulting signal contains a 1 ===== not_equals ===== **<> or ><** - boolean operator "not equals" ===== using the adjective not ===== not can be used with the logical and and logical or example: given a workspace containing 3 trials (*trial1.c3d, *trial2.c3d, and *trial3.c3d) all trials are assigned a tag labeled walk * trial1.c3d is also assigned a tag labeled bad [[visual3d:documentation:pipeline:file_commands:select_active_file|select_active_file]] /file_name=walk /query=bad **;** this command results in *trial1.c3d being active [[visual3d:documentation:pipeline:file_commands:select_active_file|select_active_file]] /file_name=walk /query=not(bad) **;** this command results in *trial2.c3d and *trial3.c3d being active. ===== less_than ===== **<** boolean operator //less than// **example** given two signals target::original::rft1 target::original::lft1 use the boolean operator < to identify when the z component of rft1 is less than the z component of lft1 **evaluate_expression** /expression= target::original::rft1::z < target::original::lft1::z /result_name=rft1_greater /result_type=derived /result_folder=processed **;** the output signal will be 1 when rft1::z is less than lft1::z and 0 otherwise **example - foot clearance** given the following situation. heel and toe clearance are defined by two paths. one might consider foot clearance to be the lower value of the heel and toe clearance values at each frame. heel_toe_clearance.jpg here is a simplified test of this make the global workspace active. create 2 signals as follows **evaluate_expression** /expression=list(1,2,3,4,5) ! /signal_types= ! /signal_folder=original ! /signal_names= ! /signal_components= /result_types=derived /result_folders=processed /result_name=signal1 ! /apply_as_suffix_to_signal_name=false **;** **evaluate_expression** /expression=list(5,4,3,2,1) ! /signal_types= ! /signal_folder=original ! /signal_names= ! /signal_components= /result_types=derived /result_folders=processed /result_name=signal2 ! /apply_as_suffix_to_signal_name=false **;** !create a new signal that is the lower value of the two signals **evaluate_expression** /expression=(derived::processed::signal1<=derived::processed::signal2)*derived::processed::signal1 +(derived::processed::signal2<derived::processed::signal1)*derived::processed::signal2 ! /signal_types= ! /signal_folder=original ! /signal_names= ! /signal_components= /result_types=derived /result_folders=processed /result_name=signal_lower ! /apply_as_suffix_to_signal_name=false **;** heel_toe_clearance2.jpg ===== less_than_or_equals ===== ! style="text-align:left;" |      **<=** or **=<** boolean operator //less than or equal to// example: given two signals target::original::rft1 target::original::lft1 use the boolean operator <= or the boolean operative =< to identify when the z component of rft1 is less than or equal to the z component of lft1 **evaluate_expression** /expression= target::original::rft1::z <= target::original::lft1::z /result_name=rft1_greater /result_type=derived /result_folder=processed **;** the output signal will be 1 when rft1::z is less than or equal tolft1::z and 0 otherwise ===== greater_than ===== **>** boolean operator //greater than// example: given two signals target::original::rft1 target::original::lft1 use the boolean operator > to identify when the y component of rft1 is greater than the y component of lft1 **evaluate_expression** /expression= target::original::rft1::y > target::original::lft1::y /result_name=rft1_greater /result_type=derived /result_folder=processed **;** the output signal will be 1 when rft1::y is greater than lft1::y and 0 otherwise ===== greater_than_or_equals ===== **>=** boolean operator //greater than or equals// }}