dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2022-01-11T12:02:50Zhttps://git.dynare.org/Dynare/dynare/-/issues/1830dynare_version: add release date string as second output argument2022-01-11T12:02:50ZJohannes Pfeiferdynare_version: add release date string as second output argumentWill allow identifying whether a version on the stable branch is before or after the stable release. The second output should follow the logic of the unstable versions, e.gg.
```
5.0-2021-12-24
```Will allow identifying whether a version on the stable branch is before or after the stable release. The second output should follow the logic of the unstable versions, e.gg.
```
5.0-2021-12-24
```5.xhttps://git.dynare.org/Dynare/dynare/-/issues/1828occbin_write_regimes bug: smoothed regimes are not handled2021-12-11T17:50:17ZMarco Rattooccbin_write_regimes bug: smoothed regimes are not handledthe current behavior of `occbin_write_regimes` command points to the field `oo_.occbin.regime_history`, which is provided as a result of a model simulation.
when running a smoother, instead, regime history is stored in `oo_.occbin.smooth...the current behavior of `occbin_write_regimes` command points to the field `oo_.occbin.regime_history`, which is provided as a result of a model simulation.
when running a smoother, instead, regime history is stored in `oo_.occbin.smoother.regime_history`: we would then need an extra option to the command to specify whether the regmies come from a simulation or from a smoother, so to allow calling it;
`occbin_write_regimes(smoother);` or `occbin_write_regimes(simulation);`
at this point, we may also think to move the results of a simulation in a substructure `oo_.occbin.simul` ?Johannes PfeiferJohannes Pfeiferhttps://git.dynare.org/Dynare/dynare/-/issues/1827occbin bug: varables with trend are not properly handled in switching equations2021-12-11T17:50:17ZMarco Rattooccbin bug: varables with trend are not properly handled in switching equationsAssume a model with variables with trend:
```
var bg y (deflator=y0);
var t;
```
with parameters
```
parameters eta deftar
eta=0.01;
deftar=0.03;
```
I a variable with a trend appears in an equation that switches:
```
[name = 'debt sta...Assume a model with variables with trend:
```
var bg y (deflator=y0);
var t;
```
with parameters
```
parameters eta deftar
eta=0.01;
deftar=0.03;
```
I a variable with a trend appears in an equation that switches:
```
[name = 'debt stabilization rule', bind = 'bg0']
t=0;
[name = 'debt stabilization rule', relax = 'bg0']
t = eta*( (bg-bg(-1))/y - deftar);
...
```
```
steady_state_model;
t=0;
y=1;
bg=2.4;
end;
```
then, the switches are treated BEFORE handling the trends, which means that in static_resid the first difference `bg-bg(-1)` is first evaluated to be ZERO (which is wrong, since the trend is not considered there), so that in steady state we have a residual equation like
```
resid() = t_ss - eta*(-deftar);
```
which provides a non-zero residual.
I fear a similar issue pops up in the dynamic file.Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1826occbin: allow more general formulas for constraints2021-12-11T17:50:17ZMarco Rattooccbin: allow more general formulas for constraintscurrently it is not possible to define constraints like:
```
bind logical((a>0).*(b>0))>0;
```
since preprocessor impedes the use of .* in the definition
since a and b are time series, then the evaluation of the constraint goes wrong ...currently it is not possible to define constraints like:
```
bind logical((a>0).*(b>0))>0;
```
since preprocessor impedes the use of .* in the definition
since a and b are time series, then the evaluation of the constraint goes wrong since we are multiplying two vectors.
would this be something doable?Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1825Decide on whether to drop Dynare++2023-06-13T12:51:39ZJohannes PfeiferDecide on whether to drop Dynare++Most functionality of Dynare++ has been integrated to Dynare. We are moving closer/further with tickets like https://git.dynare.org/Dynare/dynare/-/issues/1802
But there still are some parts that Dynare++ is capable of that are not suppo...Most functionality of Dynare++ has been integrated to Dynare. We are moving closer/further with tickets like https://git.dynare.org/Dynare/dynare/-/issues/1802
But there still are some parts that Dynare++ is capable of that are not supported in Dynare. From what I can see we have
1. approximation around something like the stochastic steady state (`--steps` option for steps in the volatility direction). Related Dynare ticket:
2. numerical accuracy checks.
I would propose to drop Dynare++ once we have these features in place in Dynare. For
1. we have the related risky steady state (https://git.dynare.org/Dynare/dynare/-/issues/1338), the nonlinear moving average codes (https://git.dynare.org/Dynare/dynare/-/merge_requests/653). I am also pretty sure there are newer developments.
2. we have the ticket https://git.dynare.org/Dynare/dynare/-/issues/1476.xhttps://git.dynare.org/Dynare/dynare/-/issues/1824Please add FreeBSD to the Download page on https://www.dynare.org2021-11-23T15:34:39Zyuri@FreeBSDPlease add FreeBSD to the Download page on https://www.dynare.org
Please add the dynare FreeBSD package to your [Download page](https://www.dynare.org/download/).
It should probably be in a separate page (```BSD```).
The link is [here](https://www.freshports.org/science/dynare/).
The text could say...
Please add the dynare FreeBSD package to your [Download page](https://www.dynare.org/download/).
It should probably be in a separate page (```BSD```).
The link is [here](https://www.freshports.org/science/dynare/).
The text could say that to install ```Dynare``` on ```FreeBSD``` please use the command: ```pkg install dynare```.
Thank you,
Yuri (the maintainer of the FreeBSD dynare port).Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1823Fix or block interplay of stochastic Ramsey and block2021-11-24T10:32:33ZJohannes PfeiferFix or block interplay of stochastic Ramsey and block1. The attached file has a problem with the residual of the static model. It outputs residuals of the conditional steady state file that do not exist without `block` [rams1.mod](/uploads/708d194c770eb1cb8e1747f533139c19/rams1.mod)
2. Whe...1. The attached file has a problem with the residual of the static model. It outputs residuals of the conditional steady state file that do not exist without `block` [rams1.mod](/uploads/708d194c770eb1cb8e1747f533139c19/rams1.mod)
2. When overriding this and moving into `dyn_ramsey_static`, the `nblock`-input of the `+FNAME.static.m`-file is not set, suggesting that `block` is not supported in the first place.5.xSébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1822MacOS M1 compilation of manual: TypeError: 'DynareLexer' object is not callable2021-10-24T11:19:23ZWilli Mutschlerwilli@mutschler.euMacOS M1 compilation of manual: TypeError: 'DynareLexer' object is not callableWhen I try to compile the manual on my M1 Macbook Air using Rosetta 2 (i.e. `arch -x86_64 make html` or `arch -x86_64 make pdf`), I get the following error: `TypeError: 'DynareLexer' object is not callable
`.
Here is the full traceback:...When I try to compile the manual on my M1 Macbook Air using Rosetta 2 (i.e. `arch -x86_64 make html` or `arch -x86_64 make pdf`), I get the following error: `TypeError: 'DynareLexer' object is not callable
`.
Here is the full traceback:
```
# Sphinx version: 4.2.0
# Python version: 3.10.0 (CPython)
# Docutils version: 0.17.1 release
# Jinja2 version: 3.0.1
# Last messages:
# looking for now-outdated files...
# none found
# pickling environment...
# done
# checking consistency...
# done
# preparing documents...
# done
# writing output... [ 9%] bibliography
# writing output... [ 18%] dynare-misc-commands
# Loaded extensions:
# sphinx.ext.mathjax (4.2.0) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/ext/mathjax.py
# sphinxcontrib.applehelp (1.0.2) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinxcontrib/applehelp/__init__.py
# sphinxcontrib.devhelp (1.0.2) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinxcontrib/devhelp/__init__.py
# sphinxcontrib.htmlhelp (2.0.0) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinxcontrib/htmlhelp/__init__.py
# sphinxcontrib.serializinghtml (1.1.5) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinxcontrib/serializinghtml/__init__.py
# sphinxcontrib.qthelp (1.0.3) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinxcontrib/qthelp/__init__.py
# alabaster (0.7.12) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/alabaster/__init__.py
# sphinx.ext.autodoc.preserve_defaults (1.0) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/ext/autodoc/preserve_defaults.py
# sphinx.ext.autodoc.type_comment (4.2.0) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/ext/autodoc/type_comment.py
# sphinx.ext.autodoc (4.2.0) from /usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/ext/autodoc/__init__.py
Traceback (most recent call last):
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/cmd/build.py", line 280, in build_main
app.build(args.force_all, filenames)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/application.py", line 343, in build
self.builder.build_update()
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/builders/__init__.py", line 293, in build_update
self.build(to_build,
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/builders/__init__.py", line 357, in build
self.write(docnames, list(updated_docnames), method)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/builders/__init__.py", line 531, in write
self._write_serial(sorted(docnames))
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/builders/__init__.py", line 541, in _write_serial
self.write_doc(docname, doctree)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/builders/html/__init__.py", line 626, in write_doc
self.docwriter.write(doctree, destination)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/docutils/writers/__init__.py", line 78, in write
self.translate()
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/writers/html.py", line 70, in translate
self.document.walkabout(visitor)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/docutils/nodes.py", line 227, in walkabout
if child.walkabout(visitor):
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/docutils/nodes.py", line 227, in walkabout
if child.walkabout(visitor):
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/docutils/nodes.py", line 227, in walkabout
if child.walkabout(visitor):
[Previous line repeated 3 more times]
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/docutils/nodes.py", line 219, in walkabout
visitor.dispatch_visit(self)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/util/docutils.py", line 477, in dispatch_visit
method(node)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/writers/html5.py", line 417, in visit_literal_block
highlighted = self.highlighter.highlight_block(
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/highlighting.py", line 149, in highlight_block
lexer = self.get_lexer(source, lang, opts, force, location)
File "/usr/local/Cellar/sphinx-doc/4.2.0_1/libexec/lib/python3.10/site-packages/sphinx/highlighting.py", line 127, in get_lexer
lexer = lexer_classes[lang](**opts)
TypeError: 'DynareLexer' object is not callable
```https://git.dynare.org/Dynare/dynare/-/issues/1821evaluate_planner_objective does not compute expected utility correctly2021-10-18T16:43:48ZJohannes Pfeiferevaluate_planner_objective does not compute expected utility correctlySee the failed tests in !1945
The proximate cause is that the expected value `EU` in `evaluate_planner_objective.m` differs from what you would get when it were part of the variables in `oo_.mean`.See the failed tests in !1945
The proximate cause is that the expected value `EU` in `evaluate_planner_objective.m` differs from what you would get when it were part of the variables in `oo_.mean`.5.xhttps://git.dynare.org/Dynare/dynare/-/issues/1820Invalid memory accesses in local_state_space_iteration_2 when there are more ...2021-10-21T18:11:05ZSébastien VillemotInvalid memory accesses in local_state_space_iteration_2 when there are more shocks than statesIn [local_state_space_iteration_2](mex/sources/local_state_space_iterations/local_state_space_iteration_2.cc#L166), in function `ss2Iteration`, the block that computes `ghx·yhat+ghu·u` reads as follows:
```
for (int column = 0,...In [local_state_space_iteration_2](mex/sources/local_state_space_iterations/local_state_space_iteration_2.cc#L166), in function `ss2Iteration`, the block that computes `ghx·yhat+ghu·u` reads as follows:
```
for (int column = 0, column_ = 0; column < q; column++, column_ += m)
{
int i1 = variable+column_;
int i2 = column+particle__;
int i3 = column+particle___;
y[variable_] += ghx[i1]*yhat[i2];
y[variable_] += ghu[i1]*epsilon[i3];
}
for (int column = q, column_ = q*m; column < n; column++, column_ += m)
y[variable_] += ghx[variable+column_]*yhat[column+particle__];
```
This code makes the implicit assumption that `q⩽n`, i.e. that the number of shocks is less than or equal to the number of states. If `q>n`, it will try to read invalid memory references in `ghx` and `yhat`, and it will either crash or return dummy results.
The same problem is present in the `ss2Iteration_pruning` function.
The fix is simply to reorganize the loops, with one loop that only deals with the states and another one that deals with shocks.
@stepan-a If you agree with this diagnostic, I will take care of fixing it.5.xSébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1819Fix bug in mex k-order-simulations (i.e. without pruning)2021-10-12T15:39:39ZJohannes PfeiferFix bug in mex k-order-simulations (i.e. without pruning)The mex-file `dynare_simul_` erroneously iterates on the policy function with a zero shock vector for the first (non-endogenous) period. As a consequence, results differ from the m-file-based simulations at second order and from a one at...The mex-file `dynare_simul_` erroneously iterates on the policy function with a zero shock vector for the first (non-endogenous) period. As a consequence, results differ from the m-file-based simulations at second order and from a one at a time sequential simulation (see https://forum.dynare.org/t/simult-results-different-with-loop/19053/3).
The bug will not affect
1. third order simulations with pruning, which are based on the m-file.
2. IRFs starting the stochastic steady state/ergodic mean in the absence of shocks due to it being the fixed point of the simulation.
The bug will typically hardly affect moment computations and IRFs at the ergodic mean due to the initial burn-in period. In that case, the initial condition should wash out.5.xhttps://git.dynare.org/Dynare/dynare/-/issues/1817Find workaround for warnings at Dynare startup under Octave2021-09-21T16:43:54ZSébastien VillemotFind workaround for warnings at Dynare startup under OctaveWhen Dynare starts under Octave, one gets:
```
warning: function /home/sebastien/dynare/unstable/matlab/+pac/+bgp/get.m shadows a built-in function
warning: called from
dynun at line 4 column 5
warning: function /home/sebastien/dyna...When Dynare starts under Octave, one gets:
```
warning: function /home/sebastien/dynare/unstable/matlab/+pac/+bgp/get.m shadows a built-in function
warning: called from
dynun at line 4 column 5
warning: function /home/sebastien/dynare/unstable/matlab/+pac/+bgp/set.m shadows a built-in function
warning: called from
dynun at line 4 column 5
```
This is the consequence of an [Octave bug](https://savannah.gnu.org/bugs/?46849).
A partial workaround was implemented in 4c0b2e8c4ec2df8f1833769db1c873486d2b87f7, but it does not suppress early warnings.
A better solution should be found.5.xSébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1816Document VAR and PAC routines2024-01-29T20:46:19ZSébastien VillemotDocument VAR and PAC routines6.xStéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/1815bytecode locks .bin file after entering homotopy.2021-09-20T16:44:50ZJohannes Pfeiferbytecode locks .bin file after entering homotopy.Running [ireland.mod](/uploads/27aa0ebc6b17c399aa0a9f0ee2929c23/ireland.mod) triggers an exception
`Fatal error in bytecode: umfpack_dl_solve failed`
in the first iteration so that we enter homotopy mode. This it successful. But subseque...Running [ireland.mod](/uploads/27aa0ebc6b17c399aa0a9f0ee2929c23/ireland.mod) triggers an exception
`Fatal error in bytecode: umfpack_dl_solve failed`
in the first iteration so that we enter homotopy mode. This it successful. But subsequently, the mod-file cannot be run a second time due to `model/bytecode/dynamic.bin` being locked. It seems that
`SparseMatrix.cc` opens
```
SaveCode.open(file_name + "/model/bytecode/dynamic.bin", ios::in | ios::binary);
```
but never closes it in case of an exception.5.xSébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1813cherrypick() and aggregate() bug over some variables names ending with 'min' ...2022-05-04T15:59:17ZUgo Duboischerrypick() and aggregate() bug over some variables names ending with 'min' / 'max' / 'log'Having a lagged variable name ending with 'min', 'max' or 'log' in an equation interacts in unexpected ways with the cherrypick() and aggregation() procedures.
In the joined example: the variable 'xmin' (exogenous) and 'ymax' (endogeno...Having a lagged variable name ending with 'min', 'max' or 'log' in an equation interacts in unexpected ways with the cherrypick() and aggregation() procedures.
In the joined example: the variable 'xmin' (exogenous) and 'ymax' (endogenous) both appears in the equation for 'ymax' as xmin(-1) and ymax(-2).
Cherrypicking this equation makes superfluous 'x' and 'y' exogenous variables appear in the aggregated model, variables that do not exist in the model. The error seems to stem from the program responsible for the 'exogenous.inc' file creation, where exogenous variables 'x' and 'y' are written.
Trying to run the aggregated model outputted this way will have Dynare complaining about the unknown symbol 'xmin' and the unused 'x' and 'y' variables.
This bug seems to also be triggered by variables names ending with 'max' and 'log'.
See the very simple .mod file attached: [TestModel.mod](/uploads/8c9d651a17217c3bd4cd538ac379d808/TestModel.mod)https://git.dynare.org/Dynare/dynare/-/issues/1811Clarify auxiliary variable types2021-09-17T14:39:12ZJohannes PfeiferClarify auxiliary variable types- [x] Move https://archives.dynare.org/DynareWiki/AuxiliaryVariables to new Wiki
- [x] According to https://git.dynare.org/Dynare/dynare/-/blob/master/matlab/isauxiliary.m there are more than the 6 documented types
- [x] Check https://gi...- [x] Move https://archives.dynare.org/DynareWiki/AuxiliaryVariables to new Wiki
- [x] According to https://git.dynare.org/Dynare/dynare/-/blob/master/matlab/isauxiliary.m there are more than the 6 documented types
- [x] Check https://git.dynare.org/Dynare/dynare/-/blob/master/matlab/disp_dr.m for consistency (type 10 is missing)
- [x] Check whether type >8 still actually arises5.xhttps://git.dynare.org/Dynare/dynare/-/issues/1810macOS: solve installation problems2021-09-01T13:44:39ZJohannes PfeifermacOS: solve installation problemsSee https://forum.dynare.org/t/installation-failure-with-dynare-4-6-4/18563/18
and
https://github.com/Homebrew/discussions/discussions/1990#discussioncomment-1190489See https://forum.dynare.org/t/installation-failure-with-dynare-4-6-4/18563/18
and
https://github.com/Homebrew/discussions/discussions/1990#discussioncomment-11904895.xhttps://git.dynare.org/Dynare/dynare/-/issues/1809rbc.mod: error: sq_string cannot be indexed with .2021-08-15T07:29:26Zyuri@FreeBSDrbc.mod: error: sq_string cannot be indexed with .This model fails:
```
error: sq_string cannot be indexed with .
error: called from
dyntable at line 35 column 1
driver at line 200 column 1
dynare at line 293 column 1
```
Version: 4.6.4
Octave: 6.3.0
OS: FreeBSD 13
[rbc...This model fails:
```
error: sq_string cannot be indexed with .
error: called from
dyntable at line 35 column 1
driver at line 200 column 1
dynare at line 293 column 1
```
Version: 4.6.4
Octave: 6.3.0
OS: FreeBSD 13
[rbc.mod](/uploads/626e8e116f4fa959325cddeeee600244/rbc.mod)https://git.dynare.org/Dynare/dynare/-/issues/1808Update or remove https://archives.dynare.org/DynareWiki/EquationsTags2021-08-17T10:04:38ZJohannes PfeiferUpdate or remove https://archives.dynare.org/DynareWiki/EquationsTagsThe information there seems outdated or redundant, but it is still linked from the manual.The information there seems outdated or redundant, but it is still linked from the manual.5.xhttps://git.dynare.org/Dynare/dynare/-/issues/1807Manual: fix broken references2021-09-20T16:34:02ZJohannes PfeiferManual: fix broken referencesThe manual contains a bunch of broken internal references that seems to occur when referencing something that does not have a natural anchor. For example
```
.. _quote-note:
.. note::
Note on Quotes
```
and
```
...The manual contains a bunch of broken internal references that seems to occur when referencing something that does not have a natural anchor. For example
```
.. _quote-note:
.. note::
Note on Quotes
```
and
```
.. _VarianceDecomposition:
``VarianceDecomposition``
Decomposition of variance (unconditional variance, i.e. at
horizon infinity). [#f5]_
``VarianceDecompositionME``
Same as `VarianceDecomposition`_, but contains
```
do not work5.x