qwe

qwe

…riables.

… NaNs.

…model.

So that we can reuse them for the interpreter later on.

…].[cpp|h].

…() into generateInitialisationCode().

To make it easier to work with both the Generator and Interpreter classes.

…C profile.

There are indeed C functions to get the minimum/maximum of two values: fmin() and fmax().

…rStatement as a tree.

…coverage.

…an InterpreterStatement object as a tree.

…ments.

…coverage.

Indeed, it's accounted for in the CI type and the `rate()` method.

We had disabled them for coverage reasons.

…ctions.

... and actually fixed the one for acoth()!

…`otherwise` element.

See https://www.w3.org/TR/MathML2/chapter4.html#contm.piecewise for more details. Basically, a `piecewise` element can have 0+ `piece` child elements and optionally 1 `otherwise` child element. If there are no child elements then it's undefined, which in our case means that our InterpreterStatement class will evaluate such a `piecewise` element to NAN.

When evaluating it, we would have one extra call for nothing while we could directly evaluate the otherwise part.

…tor.

So, we need to construct our statement in the other branch!

So that it can be used in tests/test_utils.cpp.

This means fewer calls when evaluating a model.

…e statement.

So that the end-user can modify their values, if needed (e.g., for integration purposes).

…ted models.

Since we don't currently support the interpretation of DAE models.

So that we can compare it to our future InterpreterRpnStatement.

Indeed, it is 15 to 20 times slower than the AST-based interpreter. Clearly, handling a stack is more costly than handling recursion.

This was only done to check that we do indeed get the same results... and we do.

Very important to make sure that we do indeed get the results we expect for all aspects of the interpreter.

Rather than `std::vector<double>` (and then retrieve the data using `data()`. Indeed, some solvers may want to use temporary arrays (e.g., CVODE uses a temporary array of doubles for states and rates), which means that we need to be able to set them, if needed.

We now rely on the user providing them since some solvers may use temporary arrays to compute rates (e.g., CVODE uses temporary arrays for states and rates).