... | ... | @@ -28,7 +28,7 @@ Run-time variables are created at run-time during pre-processing, processing or |
|
|
|
|
|
Some run-time variables (“current values”) are read-only and are only modified by built-in GetDP algorithms or functions, like `$Time` or `$TimeStep`.
|
|
|
|
|
|
In the following example the run-time variable `$a` is set in two different ways in functions; the run-time variables `$b_1`, `$b_2`, ... are dynamically created and used depending on the index of the quadrature point in a formulation term; and the run-time variable `$c` is set using the `Evaluate` operation in a `Resolution` or by storing the result of a `PostOperation`:
|
|
|
In the following example the run-time variable `$a` is set in two different ways in functions; the run-time variables `$b_1`, `$b_2`, ... are dynamically created and used depending on the index of the quadrature point in a formulation term (using the built-in function `GetQuadraturePointIndex[]`); and the run-time variable `$c` is set using the `Evaluate` operation in a `Resolution` or by storing the result of a `PostOperation`:
|
|
|
|
|
|
```cpp
|
|
|
Function{
|
... | ... | @@ -62,6 +62,8 @@ PostOperation{ |
|
|
}
|
|
|
```
|
|
|
|
|
|
Other built-in functions like `ElementNum[]` can be used to create a cache of evaluated expressions, per element and per quadrature point, to speed up calculations.
|
|
|
|
|
|
## ONELAB parameters
|
|
|
|
|
|
ONELAB parameters are exchanged with a ONELAB server, and can thus be exchanged with other ONELAB clients connected to the same server. ONELAB parameters can be created or accessed both at parse time (using the parser commands `DefineNumber`, `DefineConstant`, `GetNumber` and `SetNumber`) or at run-time (using the functions `GetNumberRunTime` and `SetNumberRunTime`). ONELAB parameters potentially involve the most overhead, as they can be exchanged e.g. over a network through a TCP-IP socket.
|
... | ... | |