Update fixed bug list with release of 4.6.4 authored by Sébastien Villemot's avatar Sébastien Villemot
This page documents known bugs in Dynare stable. This page documents known bugs in Dynare stable.
* Passing multiple shock values through a MATLAB/Octave vector in a `mshocks` block does not work (bug fixed in ffa828a659bec9a590ca3794012d1c5b828061a6 and 12ef75314a4d2ba3a36c90cb42476e74e1eec976)
* `mode_compute=12` is broken (bug fixed via !1784)
* The `use_mh_covariance` was ignored (bug fixed in cef13ffd)
* The `use_mh_covariance` does not work with `mh_tune_jscale` (bug fixed in 0090de63)
* `load_mh_file` together with `mh_replic=0` does not allow computing `moments_varendo` for a different list of variables (bug fixed in c27c4fd9)
* The `forecast`-option is ignored when using `mode_compute=0` without a mode-file to execute the smoother (bug fixed, see https://git.dynare.org/Dynare/dynare/-/merge_requests/1802)
* `discretionary_policy` crashes in the presence of news shocks (bug fixed
via !1767)
* `ramsey_constraints` crashes if the constraint contains defined `parameters` (bug fixed in https://git.dynare.org/Dynare/dynare/-/merge_requests/1788)
* Identification will display a wrong error message if a unit root is present and `diffuse_filter` has been set (bug fixed via !1782)
* particle filter estimation will crash if the initial state covariance becomes singular for a draw (bug fixed via 38e300b9)
* particle filter estimation will crash if `k_order_solver` is specified with `options_.particle.pruning` (bug fixed via 0b87f664)
* The initial state covariance in particle filter estimation may be `NaN` when using `nonlinear_filter_initialization=2` despite `options_.particles.pruning=1` (bug fixed in f19decf2)
* Output of `smoother`-results when using particle filters will be based on `order=1` (bug fixed, in 417f038c)
* Output of `moments_varendo`-results when using particle filters will be based on `order=1` (bug fixed in dedfd0c0, 314948ce. and b38d6f81)
* When decreasing the `order` in mod-files, `oo_.dr` may contain stale results from higher orders (bug fixed in 827a7fca)
* Estimation results using the particle filter at `order=3` will be incorrect if the restricted state space differs from the unrestricted one (bug fixed, see #1768)
* `mode_compute=102` (SOLVEOPT) may return with `Inf` instead of the last feasible value (bug fixed in a89f21b5)
* Using `analytic_derivation` for Bayesian estimation will result in wrong results when the multivariate Kalman filter enters the steady state stage (bug fixed in c6c9b4e3)
* Using `analytic_derivation` for ML estimation will result in a crash (bug fixed in 82aa669b)
* When using the Bayesian smoother with `filtered_vars`, the field for `Filtered_Variables_X_step_ahead` used the length of vector instead of the actual steps in `filter_step_ahead` (bug fixed in 59dd96db)
* `mode_compute=1,3` crashed when `analytic_derivation` was specified (bug fixed in 0718a3eb)
* `mode_compute=1,3,102` did only allow for Post-Matlab2016a option names (bug fixed in ff427807)
* `cova_compute=0` did not work with user-defined `MCMC_jumping_covariance` (bug fixed via https://git.dynare.org/Dynare/dynare/-/commit/9351fd662fa8ea089c763c403ee4f6d94413ae71)
* `mode_compute=1` does not work with `analytic_derivation` (bug fixed, see https://git.dynare.org/Dynare/dynare/-/issues/1770)
* Not all commands honor saving to the `M_.dname`-folder (bug fixed, see da3943be)
* LaTeX output of the simulated variance decomposition for observables with measurement error may have a wrong variable label (bug fixed in f721a14f)
* Forecasts are only based on the DSGE-model, not the DSGE-VAR (bug not yet fixed; see #819) * Forecasts are only based on the DSGE-model, not the DSGE-VAR (bug not yet fixed; see #819)
* `smoother2histval` will crash if variable names are too similar (bug fixed, see !1800) * `smoother2histval` will crash if variable names are too similar (bug fixed, see !1800)
* `smoother2histval` does not keep track of whether previously stored results were generate with `loglinear` (bug not yet fixed; see #1407) * `smoother2histval` does not keep track of whether previously stored results were generate with `loglinear` (bug not yet fixed; see #1407)
... ...
......