Dynare issueshttps://git.dynare.org/groups/Dynare/-/issues2021-04-13T08:44:24Zhttps://git.dynare.org/Dynare/website/-/issues/1Improve mobile website2021-04-13T08:44:24ZWilli Mutschlerwilli@mutschler.euImprove mobile websiteI just noticed that the mobile version lacks parts of the top menu and displays only the last few menu entries. Here are some screenshots taken with my iPhone SE (2020) in landscape and horizontal mode. We should somehow add a „burger-st...I just noticed that the mobile version lacks parts of the top menu and displays only the last few menu entries. Here are some screenshots taken with my iPhone SE (2020) in landscape and horizontal mode. We should somehow add a „burger-style“ menu to have access to all subpages.
![73359EE2-CAE5-44E0-9F90-5F8D5100C271](/uploads/49347dbdc207b1c2ee9edcb9d237a0d8/73359EE2-CAE5-44E0-9F90-5F8D5100C271.png)
![46F02AB9-3C35-4A49-B8C6-CC00E46FA8EB](/uploads/37a72b85283d0784399d4e256d13f012/46F02AB9-3C35-4A49-B8C6-CC00E46FA8EB.png)https://git.dynare.org/Dynare/particles/-/issues/4Handle the case where the measurement errors are non additive2018-10-25T15:22:46ZStéphane Adjemianstepan@adjemian.euHandle the case where the measurement errors are non additiveIn the current state, the filter codes are written under the assumption that the measurement errors enter linearly in the measurement equation. For instance in `sequential_importance_particle_filter` we compute the variance of the predic...In the current state, the filter codes are written under the assumption that the measurement errors enter linearly in the measurement equation. For instance in `sequential_importance_particle_filter` we compute the variance of the prediction errors, `PredictedObservedVariance`, by adding the covariance matrix of the measurement errors, `H`, to the covariance of the predicted observed variables.
0.2https://git.dynare.org/Dynare/m-unit-tests/-/issues/1Add missing isoctave routine2018-10-25T02:31:35ZStéphane Adjemianstepan@adjemian.euAdd missing isoctave routineThis routine is distributed with dynare. If `m-unit-tests` routines are not used as a submodule of dynare or if dynare/matlab directory is not in the path, unit tests will fail because of the absence of the routine `isoctave`.
This routine is distributed with dynare. If `m-unit-tests` routines are not used as a submodule of dynare or if dynare/matlab directory is not in the path, unit tests will fail because of the absence of the routine `isoctave`.
https://git.dynare.org/Dynare/particles/-/issues/5Add an interface/flag for declaring that the measurement equation is linear...2018-10-25T15:22:46ZStéphane Adjemianstepan@adjemian.euAdd an interface/flag for declaring that the measurement equation is linear...... with respect to the measurement errors. The code for computing the covariance of the predicted errors is conditional on this property (See also issue #4). If the measurement equation is not linear w.r.t. the measurement errors, we mu...... with respect to the measurement errors. The code for computing the covariance of the predicted errors is conditional on this property (See also issue #4). If the measurement equation is not linear w.r.t. the measurement errors, we must explicitly add noise in the measurement equations (as we do with the structural shocks in the state equations).
0.2https://git.dynare.org/Dynare/matlab-gui/-/issues/7Link to new dynare functionality for groups2018-11-16T03:54:49ZStéphane Adjemianstepan@adjemian.euLink to new dynare functionality for groups*Created by: milicalabus*
Dear @stepan-a,
Can you please send me some example or write short explanation how to use new Dynare functionality for group names?
Thank you.
*Created by: milicalabus*
Dear @stepan-a,
Can you please send me some example or write short explanation how to use new Dynare functionality for group names?
Thank you.
https://git.dynare.org/Dynare/particles/-/issues/3Use index_resample in auxiliary filter2018-10-25T15:22:46ZStéphane Adjemianstepan@adjemian.euUse index_resample in auxiliary filter0.1Frédéric KaraméFrédéric Karaméhttps://git.dynare.org/Dynare/matlab-gui/-/issues/4group declaration for variables and shocks2018-11-16T03:54:49ZMarco Rattogroup declaration for variables and shocks@stepan-a, in the wiki you mentioned the possibility to add another keyword, like `group`, similar to `long_name` to be used in the declaration of variables.
Did you think/discuss about this in the dynare development?
Another possibili...@stepan-a, in the wiki you mentioned the possibility to add another keyword, like `group`, similar to `long_name` to be used in the declaration of variables.
Did you think/discuss about this in the dynare development?
Another possibility might also be a similar syntax as the equation tags, so that a variable might have different tags, using user-defined keywords for example
```
var
y_us $y$ (long_name = 'GDP US') [group = 'real variables', country = 'US']
y_ea $y$ (long_name = 'GDP EA') [group = 'real variables', country = 'EA']
...
```
what do you think?
https://git.dynare.org/Dynare/reporting/-/issues/1create canned reporting routines2020-05-07T17:47:04ZHoutan Bastanicreate canned reporting routinese.g. create a reporting routine that users can call after calling a Dynare command that will convert its graphic output to a report. Create a dynare preprocessor option such as `pdf` that users can pass to a Dynare command that will call...e.g. create a reporting routine that users can call after calling a Dynare command that will convert its graphic output to a report. Create a dynare preprocessor option such as `pdf` that users can pass to a Dynare command that will call said function.
https://git.dynare.org/Dynare/particles/-/issues/2Remove calls to local_state_space_iteration_22021-08-15T19:40:51ZStéphane Adjemianstepan@adjemian.euRemove calls to local_state_space_iteration_2To be replaced by a function handle that targets a routine for iterating on the nonlinear state space model.
To be replaced by a function handle that targets a routine for iterating on the nonlinear state space model.
0.1Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/1611Make dynare_sensitivity compatible with recursive estimation or provide infor...2021-08-15T19:07:37ZJohannes Pfeifer Make dynare_sensitivity compatible with recursive estimation or provide informative errorSee https://forum.dynare.org/t/calculating-rmses/11903See https://forum.dynare.org/t/calculating-rmses/119036.xhttps://git.dynare.org/Dynare/dynare/-/issues/1603Allow simulation with var_exo_det with stoch_simul2021-07-23T15:08:18ZJohannes Pfeifer Allow simulation with var_exo_det with stoch_simulSee https://forum.dynare.org/t/varexo-det-to-simulate-random-shocks-during-a-predetermined-period/11637
It seems there is at least one call to `make_ex_` missingSee https://forum.dynare.org/t/varexo-det-to-simulate-random-shocks-during-a-predetermined-period/11637
It seems there is at least one call to `make_ex_` missing6.xhttps://git.dynare.org/Dynare/preprocessor/-/issues/74Accept UTF-8 in .mod file2021-08-17T10:56:00ZHoutan BastaniAccept UTF-8 in .mod filehttps://git.dynare.org/Dynare/preprocessor/-/issues/75add maximum lag info by variable2021-08-17T10:56:45ZHoutan Bastaniadd maximum lag info by variable```
M_.maximum_endo_lag_by_var = [ ... ];
M_.maximum_exo_lag_by_var = [ ... ];
```
Where the vectors are the length of `M_.orig_endo_nbr````
M_.maximum_endo_lag_by_var = [ ... ];
M_.maximum_exo_lag_by_var = [ ... ];
```
Where the vectors are the length of `M_.orig_endo_nbr`https://git.dynare.org/Dynare/dynare/-/issues/1593Add truncated priors2021-09-01T14:33:18ZJohannes Pfeifer Add truncated priorsFollowing the discussions in #1591 and #750, we currently do not have a way to introduce a proper truncated prior. But this is an often requested feature that e.g. @rattoma would like to have. Waiting for the new estimation interface (e....Following the discussions in #1591 and #750, we currently do not have a way to introduce a proper truncated prior. But this is an often requested feature that e.g. @rattoma would like to have. Waiting for the new estimation interface (e.g. #824 and #846) seems to long to wait.
My specific proposal would be to add a new token `truncated_norm_pdf` that uses the third and fourth hyperparameter (which is usually reserved for generalized (beta) distributions) to specify the truncation. I consider this a natural interpretation of these hyperparameters for the normal distribution.
@stepan-a What do you think?
@rattoma Woud that satisfy your immediate needs? Or do you need a truncated distribution other than the normal?6.xStéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/reporting/-/issues/16create a reporting tutorial website2020-05-07T17:46:42ZHoutan Bastanicreate a reporting tutorial websiteGoing from simple examples to more complex examples to make the code more approachable
Going from simple examples to more complex examples to make the code more approachable
https://git.dynare.org/Dynare/matlab-gui/-/issues/16options_ when loading dynare model currently in workspace2020-12-07T11:43:13ZMarco Rattooptions_ when loading dynare model currently in workspaceI am trying a bit the behavior of the GUI when I load a project that has been run in the standard command line form, for which one would like to do some post-processing/analysis with the GUI.
M_ oo_ structures a loaded properly, however ...I am trying a bit the behavior of the GUI when I load a project that has been run in the standard command line form, for which one would like to do some post-processing/analysis with the GUI.
M_ oo_ structures a loaded properly, however the options_ which have been set during the executions are not reflected in the options that are set in the GUI. For example, after an estimation, all fields like options_.datafile, first_obs, etc., they have been set, but opening the estimation tab provides the DYNARE defaults etc., which then implies crashes unless one sets manually the options again.
I think it would be extremely useful that all the options set in the GUI reflect the actual values from the session in the workspace and not the default ones.
would this be possible?
thank you!Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/1573Allow mode_compute to be a vector2021-08-15T19:07:59ZJohannes Pfeifer Allow mode_compute to be a vectorAllow `mode_compute` to be a vector and the sequentially execute the mode-finders specified. See e.g. https://forum.dynare.org/t/simulated-annealing-block/11052 for why this may be useful.Allow `mode_compute` to be a vector and the sequentially execute the mode-finders specified. See e.g. https://forum.dynare.org/t/simulated-annealing-block/11052 for why this may be useful.6.xhttps://git.dynare.org/Dynare/dseries/-/issues/42Extend dseries constructor for Excel files2021-11-11T13:21:39ZMichelJuillardExtend dseries constructor for Excel filesUsers want to load data from an Excle file by specifying sheet name and rang. I suggest to introduce the following syntax:
```
dseries(FILENAME, OPTION_NAME_1, OPTION_VALUE_1, OPTION_NAME_2, OPTION_VALUE_2,...)
```
The new options would ...Users want to load data from an Excle file by specifying sheet name and rang. I suggest to introduce the following syntax:
```
dseries(FILENAME, OPTION_NAME_1, OPTION_VALUE_1, OPTION_NAME_2, OPTION_VALUE_2,...)
```
The new options would be ``xls_sheet`` and ``xls_range`` as for Dynare ``estimation`` command
It would be good to also introduce option names for the existing options: ``initial_dates``, ``range_of_dates``, ``list_of_names`` (or, better, ``variable_names``), ``tex_names`` (or better ``variable_tex_names``)
and permit the syntax
```
dseries(DATA_MATRIX, OPTION_NAME_1, OPTION_VALUE_1, OPTION_NAME_2, OPTION_VALUE_2,...)
```
Note that we can distinguish between the existing constructors and the new proposed ones as the second argument is a ``date`` in the existing constructor and a ``char array`` or ``string`` in the new onehttps://git.dynare.org/Dynare/dynare/-/issues/846Provide inverse gamma prior with indeterminate moments2021-09-01T14:31:35ZJohannes Pfeifer Provide inverse gamma prior with indeterminate momentsWe currently only allow specifying inverse gamma priors with finite/unique mean and variance. But Leeper/Walker/Yang (2010) in an influential paper use an inverse gamma prior with s=1 and nu=4 (parametrization as at http://en.wikipedia.o...We currently only allow specifying inverse gamma priors with finite/unique mean and variance. But Leeper/Walker/Yang (2010) in an influential paper use an inverse gamma prior with s=1 and nu=4 (parametrization as at http://en.wikipedia.org/wiki/Inverse-gamma_distribution), which implies non-existing first and second moments. I would suggest to provide a new prior `inv_gamma_parametrized` that takes the values provided in the mean and standard deviation fields of the `estimated_params`-block directly as the parameters of the distribution, thereby avoiding the impossible transformation from mean and variances.
I would implement this when doing #5206.xhttps://git.dynare.org/Dynare/dynare/-/issues/1556Allow running mode-finding on random draws from prior distribution to check f...2018-11-08T10:13:54ZJohannes Pfeifer Allow running mode-finding on random draws from prior distribution to check for local modes