Dynare 5.1 Released
Posted on 06 April 2022We are pleased to announce the release of Dynare 5.1.
This maintenance release fixes various bugs.
The Windows, macOS and source packages are already available for download at the Dynare website.
All users are strongly encouraged to upgrade.
This release is compatible with MATLAB versions ranging from 8.3 (R2014a) to 9.12 (R2022a), and with GNU Octave version 6.4.0 (under Windows).
Here is a list of the problems identified in version 5.0 and that have been fixed in version 5.1:
- Various problems with perfect foresight simulations in combination with
blockand/orbytecodeoptions of themodelblock:- Simulation with
bytecodeandstack_solve_algo=4could give incorrect results if the model has a linear block of type “Solve two boundaries simple/complete” - Simulation with
bytecodeandstack_solve_algo=1could fail to converge - Simulation with
block(but withoutbytecode) andstack_solve_algo=1gave wrong results in the last simulation period if the model has a block of type “Solve two boundaries simple/complete” - Simulation with
bytecodeandblockwould give incorrect results if the model has a linear block of type “Solve forward simple/complete” - Simulation with
block(but withoutbytecode) would crash or give incorrect results if the model has a block of type “Solve forward/backward simple/complete” - Simulation with
bytecode,blockandstack_solve_algo={0,1,4}would crash or give incorrect results if the model has a block of type “Solve forward/backward complete” - Simulation with
block(but withoutbytecode) gave incorrect results if the model has a block of type “Solve backward simple/complete” - Simulation with
block(with or withoutbytecode) could give incorrect results if the model has a nonlinear block of type “Solve forward/backward simple/complete” - Simulation with
bytecode,blockandstack_solve_algo=4could give incorrect results if the model has a block of type “Solve backward/forward simple/complete” that follows a block of type “Solve two boundaries” (in the sense of the dependency graph) - The convergence criterion in simulations with
block(but withoutbytecode) was incorrect: the value of thetolfoption from thesteadycommand was used instead of the value oftolfoption from theperfect_foresight_solvercommand
- Simulation with
- Various problems with steady state computation in combination with
blockand/orbytecodeoptions of themodelblock:- Steady state computation with
bytecodeandblockcould fail if some equations are marked[static] - Steady state computation with
bytecode,blockandsolve_algo⩽ 4 or ⩾ 9 could fail - Steady state computation with
bytecode,blockandsolve_algo=6would crash or give incorrect results if the model has a block of type “Solve forward/backward complete”
- Steady state computation with
- The
checkcommand would crash or give incorrect results when using theblockoption of themodelblock and if the model has a block of type “Solve backward complete” - The
staticandincidenceoptions of themodel_infocommand did not work as documented in the reference manual - Various problems with the
method_of_momentscommand:- It would crash if no
matched_momentsblock is present - It would always load the full range of the first Excel sheet instead of the
xls_rangeof the specifiedxls_sheet - SMM would crash if a parameter draw triggers an error during
additional_optimizer_steps = 13 - The
debugoption could not be passed to the command
- It would crash if no
- In the
estimationcommand, thescale_filefield of theposterior_sampler_optionsoption did not correctly load the scale - The
moments_varendooption of theestimationcommand could crash for large models - The
residcommand would not shownametags when used in conjunction with theramsey_modelcommand - Simulations with the
occbin_solvercommand would not work if there is only a surprise shock in the first period - The Liu & West auxiliary particle filter could enter infinite loops
As a reminder, the list of new features introduced in versions 5.x can be found in the release notes for 5.0.