This page (revision-21) was last changed on 21-Oct-2017 12:32 by Albrecht Striffler

This page was created on 26-Oct-2012 10:15 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
21 21-Oct-2017 12:32 19 KB Albrecht Striffler to previous

Page References

Incoming links Outgoing links
Doc Expressions
Doc Expressions

Version management

Difference between version and

At line 2 changed one line
The functionalities described on this page are only available using a commercial extension.
The functionalities described on this page are only available using a commercial extension. Please contact info@denkbares.com for more information.
At line 5 removed one line
Expressions allows to use mathematical formulas to be used in d3web knowledge bases. In every formula you may access existing questions and their values, as well as predefined constants. The results of those formulas may be used to assign it to an existing question or as a precondition in a rule.
At line 6 added 2 lines
Expressions allow to use mathematical formulas to be used in d3web knowledge bases. In every formula you may access existing questions and their values, as well as predefined constants. The results of those formulas may be used to assign it to an existing question (e.g. in a rule action) or as a condition in a rule.
At line 18 added one line
At line 23 changed one line
IF eval( gradient( measurement[-10s,0s] ) > 1 )
IF eval(gradient(measurement[-10s, 0s]) > 1)
At line 25 changed one line
/%
%
At line 33 changed 2 lines
THEN myGradient = eval( gradient( measurement[-10s,0s] ) )
/%
THEN myGradient = eval(gradient(measurement[-10s, 0s]) )
%
At line 55 added one line
At line 64 changed one line
// use other constants is NOT ALLOWED!!! --> error signaled
// using other constants is NOT ALLOWED!!! --> error signaled
At line 71 added one line
At line 77 added one line
At line 83 added one line
At line 112 added one line
At line 115 added one line
At line 141 added one line
At line 150 changed one line
| ~[..., ...~] | subHistory | Access a sub-history in a certain time range.
| ~[..., ...~] | subHistory | Access a sub-history in a certain time range. If there is not value directly at the start of the subhistory, the next earlier value will be included.
| !~[..., ...~] | strictSubHistory | Access a sub-history in a certain time range. The sub-history will not contain values that were set before the given start.
At line 173 added one line
At line 166 changed one line
* __<object-name>~[<time-point>, <time-point>~]__: \\ Returns the sub-history of the object with the name <object-name> starting from the earlier of the two time-points and lasting to the latter one. The sub-history contains all values of the object's full history that has been valid during the specified interval. This lead to that the sub-history usually starts before the specified time-points and have their latest value before the latter of those specified time-points.
* __<object-name>~[<time-point>, <time-point>~]__: \\ Returns the sub-history of the object with the name <object-name> starting from the earlier of the two time-points and lasting to the latter one. The sub-history contains all values of the object's full history that have been valid during the specified interval. This lead to that the sub-history usually starts before the specified time-points and have their latest value before the latter of those specified time-points.
* __<object-name>!~[<time-point>, <time-point>~]__: \\ Returns the strict sub-history of the object with the name <object-name> starting from the earlier of the two time-points and lasting to the latter one. The sub-history contains all values of the object's full history that have been set during the specified interval. In contrast to the 'normal' sub-history, this strict sub-history will not maybe start before the specified earlier time-point, but only at that earlier time-point or later (but of course not later than the later time-point).
At line 180 added one line
At line 173 changed 2 lines
average(myQuestion[]) // average of all values myQuestion had before (incl. current one)
average(myQuestion[now-10min, now]) // average of the last 10 minutes
average(myQuestion[]) // average of all values myQuestion had before (incl. current one)
average(myQuestion[now-10min, now]) // average of the last 10 minutes
average(myQuestion![now-10min, now]) // average of all values that were set between 10 minutes ago and now
At line 227 added one line
At line 271 added 2 lines
Below you see all functions that come with the TimeDB plugin by default. If you need additional functionality that is not covered by the provided functions, you might consider defining your own specialized function using Javascript. See __[Doc Javascript Functions]__ for more info.
This page (revision-21) was last changed on 21-Oct-2017 12:32 by Albrecht Striffler Top