GitLab

Bugfix for simult_.m when used with k_order_pert and pruning at order=1

Make error message if mode violated prior more explicit

In the rare combination of k_order_solver, pruning, and order=1 the steady state was not subtracted from the starting values when doing simulations

Fix typo in manual

Remove mexErrorCheck from k_order_pert to make it obey the noprint-option

Currently, all stochastic solvers put the error code to info(1) and use
print_info to output the error. The only exception was k_order_pert,
which immediately created an error. Thus, the use of k_order_pert did
not allow for continuing after encountering errors, because only
print_info obeys the noprint-option. Replacing mexErrCheck by setting
info should deliver the correct behavior.

This reverts commit 2815d5fb.

For parallel computations, the relative path is necessary.

bug fix GSA

Bugfix in initial_estimation_checks; making graphs more explicit

bug fixes in mode_compute=5 and gsa

-) estimation options for data set must be given also when ppost=1 (fix in testsuite);

Previously, the strings were concatenated, rendering calls to strmatch
wrong. Changed to cell arrays on which strmatch operates.

Ref #351

GSA fixes for rmse analysis

Proper use of dataset_ structure and remove the dangerous dat_fil_ utility;
Added r2 in output.

recursive formulation of price setting equations where the steady state
file is used to update parameters and invoke a non-linear solver.

Increased linewidth and changed color to differentiate from background
grid.

Closes #329