added support for the <abs> element
This commit is contained in:
parent
ec0ed21b73
commit
53ca437c7b
1 changed files with 6 additions and 0 deletions
|
@ -26,6 +26,7 @@ The complete XML syntax for a InputValue is
|
|||
<offset>0.0</offset>
|
||||
<max>infinity</max>
|
||||
<min>-infinity<min>
|
||||
<abs>false</abs>
|
||||
</some-element>
|
||||
|
||||
The enclosing element <some-element> is the element defined in each filter, like <input>, <u_min>,
|
||||
|
@ -55,6 +56,7 @@ The default values for elements not given are:
|
|||
<property/> : none
|
||||
<min/> : unclipped
|
||||
<max/> : unclipped
|
||||
<abs/> : false
|
||||
|
||||
Some examples:
|
||||
<input>
|
||||
|
@ -116,6 +118,10 @@ Example: Set the gain to 3.0 if /autopilot/locks/heading equals dg-heading-hold
|
|||
<gain>
|
||||
<digital-filter>
|
||||
|
||||
If the element <abs> is used and set to the value "true", only the absolute value of the input
|
||||
(the positive part) is used for further computations. The abs function is applied after all
|
||||
other computations are completed.
|
||||
|
||||
OutputValue
|
||||
==============================================================================
|
||||
Each filter drives one to many output properties. No scaling of offsetting is implemented
|
||||
|
|
Loading…
Reference in a new issue