dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2021-08-15T19:47:20Zhttps://git.dynare.org/Dynare/dynare/-/issues/312Allow User to choose Mean or Median statistics2021-08-15T19:47:20ZJohannes PfeiferAllow User to choose Mean or Median statisticsCurrently the posterior IRFs make hardcoded use of the Mean IRFs,although we also compute the median. It might be good to let the user decide. This mainly affects PosteriorIRF and PosteriorIRF_core2, but could also be relevant at other p...Currently the posterior IRFs make hardcoded use of the Mean IRFs,although we also compute the median. It might be good to let the user decide. This mainly affects PosteriorIRF and PosteriorIRF_core2, but could also be relevant at other places in the code.https://git.dynare.org/Dynare/dynare/-/issues/310conditional forecasting within deterministic simulations2013-03-08T15:27:28ZSébastien Villemotconditional forecasting within deterministic simulationsThese are forecasts conditional to a given path for some endogenous variables in the future. This is equivalent to the "hard tunes" done by the GPM team.
For the IMF.
These are forecasts conditional to a given path for some endogenous variables in the future. This is equivalent to the "hard tunes" done by the GPM team.
For the IMF.
4.4https://git.dynare.org/Dynare/dynare/-/issues/308add reporting routines for creating PDF reports2013-05-30T13:46:36ZSébastien Villemotadd reporting routines for creating PDF reports4.4Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/309improve automatic detrending engine2013-04-05T13:27:21ZSébastien Villemotimprove automatic detrending engineThe goal is to be able to automatically detrend the new GPM6C model.
The missing features are:
- removing additive trends (for variables expressed in logs)
- dealing with unit roots
The goal is to be able to automatically detrend the new GPM6C model.
The missing features are:
- removing additive trends (for variables expressed in logs)
- dealing with unit roots
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/304Add the possibility of interrupting MEX files during computation with Ctrl-C2014-10-24T14:35:57ZSébastien VillemotAdd the possibility of interrupting MEX files during computation with Ctrl-CEspecially useful for bytecode and estimation DLLs.
The natural way would be to intercept the SIGINT signal within the MEX, but this is not possible with MATLAB. Maybe this is possible under Octave, we must check.
For MATLAB, there is ...Especially useful for bytecode and estimation DLLs.
The natural way would be to intercept the SIGINT signal within the MEX, but this is not possible with MATLAB. Maybe this is possible under Octave, we must check.
For MATLAB, there is an undocumented function `utIsInterrupt()` in `libut`, which must be polled at regular intervals. This seems to be working under Windows. Need to check under GNU/Linux and MacOSX.
4.5https://git.dynare.org/Dynare/dynare/-/issues/307more flexible mechanism for having different equations between the static and...2013-04-11T15:11:42ZSébastien Villemotmore flexible mechanism for having different equations between the static and the dynamic modelCurrently, if one wants to tell Dynare that an equation has a different form between the static and the dynamic model (for example when the modeler wants to use his knowledge about the steady state to simplify the steady state computatio...Currently, if one wants to tell Dynare that an equation has a different form between the static and the dynamic model (for example when the modeler wants to use his knowledge about the steady state to simplify the steady state computation), then the possibilities are:
- write a steady state file (heavy)
- write a `steady_state_model` block (one has to rewrite _all_ the equations in that block)
- use a dirty hack with the macroprocessor and run Dynare two times
The `steady_state_model` is good for small models. But for big models where you want to change only a few equations, only the third option of this list is reasonable, and it is dirty.
The proposal is to introduce two equation tags which will have a special meaning to the preprocessor:
- `[static]`: this equation belongs to the static model, but not to the dynamic model
- `[dynamic]`: the opposite
This would offer a very flexible way to change only a few equations during the steady state computations.
This is a request by @FerhatMihoubi for GPM and possibly GIMF.
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/306Add preprocessor messages (stdout, stderr) to the logfile2013-03-18T12:45:30ZSébastien VillemotAdd preprocessor messages (stdout, stderr) to the logfileCurrently these messages are not in the logfile, and can be lost if MATLAB creates too much output.
Currently these messages are not in the logfile, and can be lost if MATLAB creates too much output.
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/303Improve Forecast Documentation2013-06-10T08:01:58ZJohannes PfeiferImprove Forecast DocumentationJudging from the number of questions relating to forecasting, the documentation is insufficient. In particular, the recursive forecasting option and the fields it creates (e.g. oo_.RecursiveForecast) are undocumented.
Judging from the number of questions relating to forecasting, the documentation is insufficient. In particular, the recursive forecasting option and the fields it creates (e.g. oo_.RecursiveForecast) are undocumented.
4.4https://git.dynare.org/Dynare/dynare/-/issues/301Provide a way to disable warnings2013-02-28T10:31:14ZSébastien VillemotProvide a way to disable warningsFor the moment Dynare reports many warning after preprocessing step.
Add a quiet Dynare option to avoid to printout all the warnings (IMF request for GIMF).
For the moment Dynare reports many warning after preprocessing step.
Add a quiet Dynare option to avoid to printout all the warnings (IMF request for GIMF).
4.4https://git.dynare.org/Dynare/dynare/-/issues/302dynSeries: enable excel files to be read in2013-11-12T09:14:03ZSébastien VillemotdynSeries: enable excel files to be read increate load_xls_file_data.m like load_csv_file_data.m
create load_xls_file_data.m like load_csv_file_data.m
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/299make check: automatically run tests on matlab/*.m files using internals command2014-01-28T16:57:13ZSébastien Villemotmake check: automatically run tests on matlab/*.m files using internals command- read all matlab/*.m files
- if there are tests in it, create the .m files using internals.m (need to modify)
- run these new test.m files, creating a .trs file for each one
- read all matlab/*.m files
- if there are tests in it, create the .m files using internals.m (need to modify)
- run these new test.m files, creating a .trs file for each one
https://git.dynare.org/Dynare/dynare/-/issues/297Dynare (stable) and Slicot packages for RHEL 62015-09-07T09:59:40ZSébastien VillemotDynare (stable) and Slicot packages for RHEL 6Request from Gianni Lombardo and Petr Man from ECB.
Request from Gianni Lombardo and Petr Man from ECB.
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/298make check: add timing information of tests2015-11-24T17:34:21ZSébastien Villemotmake check: add timing information of testsAdd information to each .trs file about how long the test took to run
In the make check summary, list the 10 tests that took the longest
Add information to each .trs file about how long the test took to run
In the make check summary, list the 10 tests that took the longest
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/296add preprocessor check to report an error if the same parameter appears twice...2013-02-26T11:37:44ZSébastien Villemotadd preprocessor check to report an error if the same parameter appears twice in estimated_parameters block4.4https://git.dynare.org/Dynare/dynare/-/issues/294rework option handling2022-06-02T13:55:11ZSébastien Villemotrework option handlingIt's desirable at times to know whether or not a user has set an option in the .mod file.
To do this, we can hack the preprocessor to maintain a separate cellarray, that it would assign to every time it encounters an option. Something t...It's desirable at times to know whether or not a user has set an option in the .mod file.
To do this, we can hack the preprocessor to maintain a separate cellarray, that it would assign to every time it encounters an option. Something to the effect of:
'option' , assigned , default_val
<<string>>, <<0 or 1>>, <<general>>
This can be done in the preprocessor without changing the backend matlab code. It would thereby provide the possibility, when needed, to check whether or not an option was assigned by the user, allowing us to know whether or not we can change the value.https://git.dynare.org/Dynare/dynare/-/issues/291bugs related to auxiliary variables for lagged exogenous variables2013-02-21T14:54:09ZSébastien Villemotbugs related to auxiliary variables for lagged exogenous variablesIn ./tests/auxiliary_variables/test2.mod, the preprocessor fails to create auxiliary variable for lagged exogenous one.
When that is fixed, it will be necessary to check that the derivatives of the definition of the auxiliary variable i...In ./tests/auxiliary_variables/test2.mod, the preprocessor fails to create auxiliary variable for lagged exogenous one.
When that is fixed, it will be necessary to check that the derivatives of the definition of the auxiliary variable is correctly added to test2_static.m
When test2.mod runs correctly, please add it to ./tests/Makefile.am
https://git.dynare.org/Dynare/dynare/-/issues/293bug: maxit option in steady2019-02-08T08:31:00ZSébastien Villemotbug: maxit option in steadyCurrently, the preprocessor assigns the maxit option for the steady command to options_.maxit_ and it is used in dynare_solve_block_bytecode.m for finding the steady state; dynare_solve.m, on the other hand, uses options_.solve_maxit (i....Currently, the preprocessor assigns the maxit option for the steady command to options_.maxit_ and it is used in dynare_solve_block_bytecode.m for finding the steady state; dynare_solve.m, on the other hand, uses options_.solve_maxit (i.e. an option not passed to steady) for solve_algo = 1 or 2, whereas for solve_algo = 0 or 3 the values are hard-coded.
This needs to be made uniform. Stephane suggests assigning maxit to options_.solve_maxit in the preprocessor, changing dynare_solve_block_bytecode.m to use options_.solve_maxit, and replacing the hard-coded values in dynare_solve.m with this option as well.
4.5https://git.dynare.org/Dynare/dynare/-/issues/292model_diagnostics and lead/lag on exogenous variables2013-02-21T14:54:09ZSébastien Villemotmodel_diagnostics and lead/lag on exogenous variablesmodel_diagnostics breaks when there are longer lead/lag on exogenous variables than endogenous ones
model_diagnostics breaks when there are longer lead/lag on exogenous variables than endogenous ones
https://git.dynare.org/Dynare/dynare/-/issues/290Estimation+moments_varendo does not always deliver autocorrelation function2013-03-27T13:12:56ZSébastien VillemotEstimation+moments_varendo does not always deliver autocorrelation functionEven when option ar > 1, oo_.PosteriorTheoreticalMoments.mean.var1.var2 seems to be a scalar.
Even when option ar > 1, oo_.PosteriorTheoreticalMoments.mean.var1.var2 seems to be a scalar.
4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/287Test System: Support test we expect to fail2013-02-21T14:54:09ZSébastien VillemotTest System: Support test we expect to failShould report in a different category from regular tests: XFAIL and XPASS. XFAIL will show the tests that were expected to fail and failed. XPASS will show the tests that were expected to fail and passed.
Should report in a different category from regular tests: XFAIL and XPASS. XFAIL will show the tests that were expected to fail and failed. XPASS will show the tests that were expected to fail and passed.