filter_step_ahead authored by Johannes Pfeifer's avatar Johannes Pfeifer
...@@ -20,6 +20,7 @@ This page documents known bugs in Dynare stable. ...@@ -20,6 +20,7 @@ This page documents known bugs in Dynare stable.
* `mode_compute=102` (SOLVEOPT) may return with `Inf` instead of the last feasible value (bug fixed in a89f21b5) * `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 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) * 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` 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) * `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) * `cova_compute=0` did not work with user-defined `MCMC_jumping_covariance` (bug fixed via https://git.dynare.org/Dynare/dynare/-/commit/9351fd662fa8ea089c763c403ee4f6d94413ae71)
... ...
......