Difference between revisions of "Euler"
From BioUML platform
(Draft page for Euler solving method) |
Ilya Kiselev (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Explicit Euler method for solving ODE initial value problem. Does not support | + | Explicit Euler method for solving ODE initial value problem. Support events detection. Does not support stiffness detection and varying time step. In general, usage of this method can not be recommended. |
User-provided solver parameters: | User-provided solver parameters: | ||
| − | * ''Initial step''. Time step for | + | * ''Initial time step''. Time step for Euler schema. Note this step is different from ''Time increment'' which defines time span for simulation results. |
| + | * ''Locate events''. Indicates whether events will be detected during simulation. | ||
| + | * ''Statistics mode''. Specifies how much information will be logged during simulation. | ||
| + | * ''Detect incorrect numbers (NaNs, Infs)''. If ''true;; then solver will frequently check if any of model variables turned NaN or Infinite. This may happen for example if division by zero occurs at some point. In these cases solver will stop simulation and log information about which variables turned incorrect. It is useful for model debug. If ''false'', then simulation will proceed even if variables turned NaN or infinite. | ||
Revision as of 12:10, 10 February 2017
Explicit Euler method for solving ODE initial value problem. Support events detection. Does not support stiffness detection and varying time step. In general, usage of this method can not be recommended.
User-provided solver parameters:
- Initial time step. Time step for Euler schema. Note this step is different from Time increment which defines time span for simulation results.
- Locate events. Indicates whether events will be detected during simulation.
- Statistics mode. Specifies how much information will be logged during simulation.
- Detect incorrect numbers (NaNs, Infs). If true;; then solver will frequently check if any of model variables turned NaN or Infinite. This may happen for example if division by zero occurs at some point. In these cases solver will stop simulation and log information about which variables turned incorrect. It is useful for model debug. If false, then simulation will proceed even if variables turned NaN or infinite.
