* Perfect foresight simulations may deliver an incorrect result if the following three conditions are met: (i) the model is declared as linear through the `linear` option (ii) there are exogenous variables with a lead or a lag (iii) `stack_solve_algo` is equal to 0 (the default) or 7
*`generate_trace_plots` crashes when measurement errors are present (bug fixed in f717712e)
*`generate_trace_plots` crashes when measurement errors are present (bug fixed in f717712e)
*`estimation` crashes for correlated measurement errors (bug fixed in f717712e)
*`estimation` crashes for correlated measurement errors (bug fixed in f717712e)
* In stochastic simulations, for variables that actually do not leave the steady state, reported simulated moments may be spurious (due to division by zero) (#1736)
* In stochastic simulations, for variables that actually do not leave the steady state, reported simulated moments may be spurious (due to division by zero) (#1736)
* Parallel execution/testing may crash instead of aborting with a proper error message (but not yet fixed, see https://git.dynare.org/Dynare/dynare/-/merge_requests/1758)
* Parallel execution/testing may crash instead of aborting with a proper error message (bug fixed via !1758)
* Dynare will display variance decompositions considering measurement error only if measurement errors are present for all observed variables (bug fixed in 6e06acc7)
* Dynare will display variance decompositions considering measurement error only if measurement errors are present for all observed variables (bug fixed in 6e06acc7)
* The posterior variance decompositions with measurement errors computed with `moments_varendo` are incorrect (bug fixed in 6e06acc7)
* The posterior variance decompositions with measurement errors computed with `moments_varendo` are incorrect (bug fixed in 6e06acc7)
*`moments_varendo` will not update `oo_.PosteriorTheoreticalMoments` if it is already present from e.g. earlier run of `estimation` (bug fixed in f3329c2d)
*`moments_varendo` will not update `oo_.PosteriorTheoreticalMoments` if it is already present from e.g. earlier run of `estimation` (bug fixed in f3329c2d)
...
@@ -11,7 +12,7 @@ This page documents known bugs in Dynare stable.
...
@@ -11,7 +12,7 @@ This page documents known bugs in Dynare stable.
* Identification will in some cases compute wrong Jacobian of moments (bug fix in Dynare/dynare!1733)
* Identification will in some cases compute wrong Jacobian of moments (bug fix in Dynare/dynare!1733)
* Identification will display incorrect results if parameter dependence is implemented via a steady state file (bug fix in Dynare/dynare!1732; see discussion in https://git.dynare.org/Dynare/dynare/-/issues/1733)
* Identification will display incorrect results if parameter dependence is implemented via a steady state file (bug fix in Dynare/dynare!1732; see discussion in https://git.dynare.org/Dynare/dynare/-/issues/1733)
* Using external functions in a model local variable crashes the preprocessor (bug fixed in preprocessor@931935a9420804db7e7d528659ef3be2801886d6)
* Using external functions in a model local variable crashes the preprocessor (bug fixed in preprocessor@931935a9420804db7e7d528659ef3be2801886d6)
* Tolerance criteria for steady state computations were inconsistently set (fixed in https://git.dynare.org/Dynare/dynare/-/commit/607a273bb0086ed36831b36327c1b3c456e539b2
* Tolerance criteria for steady state computations were inconsistently set (fixed in 607a273bb0086ed36831b36327c1b3c456e539b2)
*`stoch_simul` with its default `order=2` will crash with a message about `hessian_eq_zero` not existing if an explicit `order=1` is present somewhere else in the mod-file (bug fixed in preprocessor@5cc9f216).
*`stoch_simul` with its default `order=2` will crash with a message about `hessian_eq_zero` not existing if an explicit `order=1` is present somewhere else in the mod-file (bug fixed in preprocessor@5cc9f216).
* Model local variables are not in the `modfile.json` JSON file (#1723)
* Model local variables are not in the `modfile.json` JSON file (#1723)
* Model local variables names have two spurious underscores when they are defined in the `dynamic.json` and `static.json` files (but only in the definition, not when they are used, which is inconsistent) (bug fixed in preprocessor@f9ab44da56558ae4be891ad97e52b637484551f6)
* Model local variables names have two spurious underscores when they are defined in the `dynamic.json` and `static.json` files (but only in the definition, not when they are used, which is inconsistent) (bug fixed in preprocessor@f9ab44da56558ae4be891ad97e52b637484551f6)
