Changes

Page history
Update Known bugs present in the current stable version authored by Sébastien Villemot's avatar Sébastien Villemot
Show whitespace changes
Inline Side-by-side
Known-bugs-present-in-the-current-stable-version.md
View page @ b6ecbcb7
This page documents known bugs in Dynare stable. This page documents known bugs in Dynare stable.
* Perfect foresight simulations with `bytecode` and `block` options can crash if there is a purely forward variable whose value in all periods can be evaluated backward (typically a process of the form `y=a*y(+1)+e`) (fixed; see #1727) * Perfect foresight simulations with `bytecode` and `block` options can crash if there is a purely forward variable whose value in all periods can be evaluated backward (typically a process of the form `y=a*y(+1)+e`) (fixed; see #1727)
* `extended_path` is (still) broken with `bytecode` (fixed in b9812a0ff05b48f783c9bc19d7eeb283e97cff1e) * `extended_path` is (still) broken with `bytecode` (fixed in 71e3e0d4)
* 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` 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)
* The `initval_file` option does not yet support Dynare's translation of a model into a one lead/lag-model via auxiliary variables (bug not yet fixed; see #1004) * The `initval_file` option does not yet support Dynare's translation of a model into a one lead/lag-model via auxiliary variables (bug not yet fixed; see #1004)
... ...
......