dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2024-03-27T14:03:31Zhttps://git.dynare.org/Dynare/dynare/-/issues/1927oo_ used but undefined in +occbin/kalman_update_algo_3.m2024-03-27T14:03:31ZSébastien Villemotoo_ used but undefined in +occbin/kalman_update_algo_3.mLine 259 of `matlab/+occbin/kalman_update_algo_3.m` reads:
```
[~, out, ss] = occbin.solver(M_,oo_,options_);
```
But `oo_` is undefined in that file.
I encountered this error when running `calib_smoother` after `oc...Line 259 of `matlab/+occbin/kalman_update_algo_3.m` reads:
```
[~, out, ss] = occbin.solver(M_,oo_,options_);
```
But `oo_` is undefined in that file.
I encountered this error when running `calib_smoother` after `occbin_setup`.https://git.dynare.org/Dynare/dynare/-/issues/1721Get rid of oo_.dr.kstate2024-03-26T09:53:46ZSébastien VillemotGet rid of oo_.dr.kstateIn particular, see the discussion in #1653In particular, see the discussion in #16537.xSébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1925Issues when modifying values of dseries on a loop2024-03-12T10:40:40ZRaphaël MARTINIssues when modifying values of dseries on a loopDear Dynare Team,
As a new user of Dynare, I'm reaching out to report a potential bug I've encountered while working with dseries objects in Matlab, specifically using the latest unstable version of Dynare. This is my first time reporti...Dear Dynare Team,
As a new user of Dynare, I'm reaching out to report a potential bug I've encountered while working with dseries objects in Matlab, specifically using the latest unstable version of Dynare. This is my first time reporting an issue, so please excuse any inadvertent mistakes in my submission. I've noticed an issue where modifying the value of a second dseries object (which was initially set to be equal to a first dseries object) inadvertently alters the values of the first dseries object as well. This behavior is unexpected and seems to occur when the modifications are made within a loop. Here is a quick code snippet illustrating this bug :
```
addpath 'C:\Produits\dynare\dynare-7-unstable-2024-03-04-1703-7d332dee'
dynare_config;
A=dseries([0;0;0],'2020Y','toto');
B=A;
for i=1:length(B.dates)
B(B.dates(i))=B(B.dates(i))+1;
end
disp(A)
disp(B)
```https://git.dynare.org/Dynare/dynare/-/issues/1884Investigate why det_cond_forecast does not distinguish between surprise and a...2024-02-29T12:53:15ZJohannes PfeiferInvestigate why det_cond_forecast does not distinguish between surprise and anticipated shocksSee [simulation_det_cond.mod](/uploads/f162f70fa8cd7a060919c6902e6ca1da/simulation_det_cond.mod)See [simulation_det_cond.mod](/uploads/f162f70fa8cd7a060919c6902e6ca1da/simulation_det_cond.mod)Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1922Create GitLab CI to build, test and deploy docker containers2024-02-22T10:22:30ZWilli Mutschlerwilli@mutschler.euCreate GitLab CI to build, test and deploy docker containersIt would be beneficial to have a workflow with GitLab to build, test and deploy the docker containers.It would be beneficial to have a workflow with GitLab to build, test and deploy the docker containers.Willi Mutschlerwilli@mutschler.euWilli Mutschlerwilli@mutschler.euhttps://git.dynare.org/Dynare/dynare/-/issues/1919bug in annualized shock decomposition2024-01-30T10:18:34ZMarco Rattobug in annualized shock decompositionwhen removing unused output args in commit 735bd66d4dea2f244918687fa0fa57051df59673, we created a bug in annualized_shock_decomposition.
there, the second unised argument is actually necessary to trigger the behavior in plot_shock_decomp...when removing unused output args in commit 735bd66d4dea2f244918687fa0fa57051df59673, we created a bug in annualized_shock_decomposition.
there, the second unised argument is actually necessary to trigger the behavior in plot_shock_decomposition that depends on nargout inline 535 .[https://git.dynare.org/Dynare/dynare/-/blob/master/matlab/shock_decomposition/plot_shock_decomposition.m?ref_type=heads#L535](url)
Admittedly, this is a very obscure feature...https://git.dynare.org/Dynare/dynare/-/issues/1688fix `basic_plan`, `flip_plan` in doc2024-01-29T20:57:50ZHoutan Bastanifix `basic_plan`, `flip_plan` in docThe calling structure for both of these functions runs off the end of the pageThe calling structure for both of these functions runs off the end of the page6.xStéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/1660Update documentation of dseries2024-01-29T20:51:00ZSébastien VillemotUpdate documentation of dseriesSince dseries have been substantially rewritten since 4.5, the documentation in the reference needs to be updated.Since dseries have been substantially rewritten since 4.5, the documentation in the reference needs to be updated.6.xStéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://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/1918Preprocessor issue with mensual dates with month > 9 passed to daynre into ma...2024-01-29T11:17:26ZUgo DuboisPreprocessor issue with mensual dates with month > 9 passed to daynre into macrovariablesI think I just stumbled into an interesting bug while passing macrovariables containing mensual dates to dynare.
In a very simple mod: [SimpleMod.mod](/uploads/c460c03b98abd0f7acee934530394df5/SimpleMod.mod)
I have (a dummy model) and ...I think I just stumbled into an interesting bug while passing macrovariables containing mensual dates to dynare.
In a very simple mod: [SimpleMod.mod](/uploads/c460c03b98abd0f7acee934530394df5/SimpleMod.mod)
I have (a dummy model) and the instruction: `Toto = @{MensualDate};`
I call this .mod with dynare as follows: `dynare('SimpleMod.mod', '-DMensualDate="2005M10"');`
And get an 'invalid expression' error on `SimpleMod.driver` because what gets written in the driver for the `Toto = @{MensualDate};` instruction is : `Toto = dates('2005M1')0;`
2005M9 works, 2005M11 results into `Toto = dates('2005M1')1;` and 2005M12 results into `Toto = dates('2005M1')2;`Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/103bug in dealing with <fname>_steadystate.m functions that modify parameters2024-01-26T19:34:22ZSébastien Villemotbug in dealing with <fname>_steadystate.m functions that modify parametersThe changes to M_.params introduced in <fname>_steadystate.m functions are not taken into accounts by calling functions that obtain M_ as argument and not as global variable.
Need to add
M_.params = evalin('base','M_.params');
after ea...The changes to M_.params introduced in <fname>_steadystate.m functions are not taken into accounts by calling functions that obtain M_ as argument and not as global variable.
Need to add
M_.params = evalin('base','M_.params');
after each call to <fname>_steadystate.m function
4.2https://git.dynare.org/Dynare/dynare/-/issues/1707Macro commands that take no arguments have spurious parentheses appended to t...2024-01-17T20:31:14ZSébastien VillemotMacro commands that take no arguments have spurious parentheses appended to their synopsisSee for example the definition of `@#else`, `@#endif`, `@#endfor`, `@#echomacrovars` in the reference manual.See for example the definition of `@#else`, `@#endif`, `@#endfor`, `@#echomacrovars` in the reference manual.6.xhttps://git.dynare.org/Dynare/dynare/-/issues/1611Make dynare_sensitivity compatible with recursive estimation or provide infor...2024-01-17T20:31:14ZJohannes PfeiferMake 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/1892Octave testsuite on macOS: xvfb-run: command not found2023-12-21T13:05:00ZWilli Mutschlerwilli@mutschler.euOctave testsuite on macOS: xvfb-run: command not found`make check-octave` does not work on my Apple Silicon Mac running Ventura, it says `xvfb-run: command not found`. I tried installing xquartz, which gave me the `xvfb` command but not the run script. Is there a workaround?`make check-octave` does not work on my Apple Silicon Mac running Ventura, it says `xvfb-run: command not found`. I tried installing xquartz, which gave me the `xvfb` command but not the run script. Is there a workaround?6.xSébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/1915Unknow index in parallel/closeSlave.m2023-12-21T13:05:00ZStéphane Adjemianstepan@adjemian.euUnknow index in parallel/closeSlave.mLine 77 we have:
```matlab
isempty(dynareParallelDir(['P_slave_',int2str(j),'End.txt'],TmpFolder,Parallel))
```
under a `if` statement, but index `j` is not defined. Matlab interprets j as a complex number and `int2str(j)` evaluates to `...Line 77 we have:
```matlab
isempty(dynareParallelDir(['P_slave_',int2str(j),'End.txt'],TmpFolder,Parallel))
```
under a `if` statement, but index `j` is not defined. Matlab interprets j as a complex number and `int2str(j)` evaluates to `'0'`.https://git.dynare.org/Dynare/dynare/-/issues/1917macOS: drop ld_classic workaround2023-12-21T12:16:41ZWilli Mutschlerwilli@mutschler.eumacOS: drop ld_classic workaround~~Xcode CLT 15.1 fixed this [issue](https://github.com/mesonbuild/meson/issues/12282), the `ld_classic` workaround in the native file is not necessary anymore, so we can remove it once the runner is updated. Either way the workaround con...~~Xcode CLT 15.1 fixed this [issue](https://github.com/mesonbuild/meson/issues/12282), the `ld_classic` workaround in the native file is not necessary anymore, so we can remove it once the runner is updated. Either way the workaround continues to work.~~
Nope, 15.1 did not fix this.https://git.dynare.org/Dynare/dynare/-/issues/1914Fix saving of _mh_mode after integration of SMC2023-12-15T13:59:45ZJohannes PfeiferFix saving of _mh_mode after integration of SMC60c0ed01 changed the behavior of `compute_mh_covariance_matrix` to not save the `_mh_mode.mat` file. That is now done in `compute_posterior_covariance_matrix`. This breaks backward compatibility as e.g. `fs2000.mod` now does not save the...60c0ed01 changed the behavior of `compute_mh_covariance_matrix` to not save the `_mh_mode.mat` file. That is now done in `compute_posterior_covariance_matrix`. This breaks backward compatibility as e.g. `fs2000.mod` now does not save the `_mh_mode.mat` anymore via the call to `marginal_density.m`.Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/1846Remove global variables from dynare_sensitivity2023-12-14T20:00:14ZJohannes PfeiferRemove global variables from dynare_sensitivityThe command resets various options permanently, causing unexpected downstream problems. An example is !2009The command resets various options permanently, causing unexpected downstream problems. An example is !20096.xhttps://git.dynare.org/Dynare/dynare/-/issues/1905Rework fs2000.mod example file to use actual data2023-12-14T13:06:29ZJohannes PfeiferRework fs2000.mod example file to use actual dataSee https://git.dynare.org/Dynare/dynare/-/merge_requests/2160#note_19189See https://git.dynare.org/Dynare/dynare/-/merge_requests/2160#note_19189https://git.dynare.org/Dynare/dynare/-/issues/1907Decide the minimal required versions of MATLAB and Octave for Dynare 62023-12-04T08:51:40ZSébastien VillemotDecide the minimal required versions of MATLAB and Octave for Dynare 6We need to decide the minimal required versions of MATLAB and Octave for Dynare 6.
Dynare 5 requires at least MATLAB R2014a and Octave 5 (at the source code level for the latter).
Since Dynare 5 was released in January 2022, it means t...We need to decide the minimal required versions of MATLAB and Octave for Dynare 6.
Dynare 5 requires at least MATLAB R2014a and Octave 5 (at the source code level for the latter).
Since Dynare 5 was released in January 2022, it means that upon release we were supporting 8 years of MATLAB (R2014a to R2021b); and we are currently supporting 10 years of MATLAB.
If we were to apply the same policy for Dynare 6, that would mean requiring R2016a. But we could also be more aggressive, which would bring some benefits (see the [MATLAB versions](https://git.dynare.org/Dynare/dynare/-/wikis/MATLAB-Versions) page):
- R2016b would allow us to remove all calls to `bsxfun`, and also to drop the JSONlab toolbox under `contrib/` (provided that we also require Octave 7)
- R2018a would allow us to ship only one flavour of the MEX files (since that version introduced an ABI break)
- R2018b would allow us to use double quoted strings (and thus stop worrying about using single quotes everywhere)
And requiring R2019a would mean moving to 5-years window of MATLAB releases supported, which is already quite a lot.
I think we should go for at least R2016b, and maybe even R2018b.
For Octave, we already require Octave 6 in unstable. I would be inclined to require Octave 7, because that would allow us to drop JSONlab (if we also require MATLAB R2016b). My only concern is that Ubuntu 22.04 LTS ships with Octave 6 (so that may affect you @wmutschl); however note that Ubuntu 24.04 LTS will be released shortly after Dynare 6, and it will include Octave 8.
Waiting for your thoughts on this. We should also ask our institutional users about their constraints.6.xSébastien VillemotSébastien Villemot