dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2019-06-19T15:38:03Zhttps://git.dynare.org/Dynare/dynare/-/issues/774Formatting issue with impulse response charts after running sbvar( ... )2019-06-19T15:38:03ZStéphane Adjemianstepan@adjemian.euFormatting issue with impulse response charts after running sbvar( ... )*Created by: RolandMeeks*
Tick marks and labels do not appear on the M_.endo_nbr by M_.endo_nbr grid of impulse-response functions that are produced by a call to sbvar( ... ).
*Created by: RolandMeeks*
Tick marks and labels do not appear on the M_.endo_nbr by M_.endo_nbr grid of impulse-response functions that are produced by a call to sbvar( ... ).
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/803Be more flexible with calib_smoother command2019-06-19T15:38:02ZJohannes PfeiferBe more flexible with calib_smoother commandCurrently, we do not allow `prefilter`, `loglinear`, and `first_obs`. I think they are all valid options that can be easily handled within the current framework. The first step would be to add the preprocessor interface allowing these op...Currently, we do not allow `prefilter`, `loglinear`, and `first_obs`. I think they are all valid options that can be easily handled within the current framework. The first step would be to add the preprocessor interface allowing these options.
4.5Johannes PfeiferJohannes Pfeiferhttps://git.dynare.org/Dynare/dynare/-/issues/804Factorize saving of smoother results used in dynare_estimation_1 and evaluate...2019-06-19T15:38:02ZJohannes PfeiferFactorize saving of smoother results used in dynare_estimation_1 and evaluate_smootherIn `dynare_estimation_1` both the calibrated smoother and ML/MCMC without replications write the smoother results to oo_. The same holds true for `evaluate_smoother.m`. I would propose to outsource this code to a separate function that i...In `dynare_estimation_1` both the calibrated smoother and ML/MCMC without replications write the smoother results to oo_. The same holds true for `evaluate_smoother.m`. I would propose to outsource this code to a separate function that is easier to maintain (in particular when working on #679). This would also make sure that the saving is consistent. Currently, I don't think the calibrated smoother saves all necessary fields.
If agreed upon, I would volunteer to do this.
4.5Johannes PfeiferJohannes Pfeiferhttps://git.dynare.org/Dynare/dynare/-/issues/806Harmonize initval-file loading and update documentation2019-06-19T15:38:02ZJohannes PfeiferHarmonize initval-file loading and update documentation`oo_.exo_simul` is `periods` by `exo_nbr`, i.e. a collection of column vectors. In contrast, `oo_.endo_simul` is `endo_nbr` by `periods`, i.e. a collection of row vectors. This is confusing and leads to problems with initval-files where ...`oo_.exo_simul` is `periods` by `exo_nbr`, i.e. a collection of column vectors. In contrast, `oo_.endo_simul` is `endo_nbr` by `periods`, i.e. a collection of row vectors. This is confusing and leads to problems with initval-files where this needs to be taken into account. See
http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6261.
This should be harmonized in 4.5.
Moreover, in `initvalf` we should simply transpose non-conforming vectors to be more flexibe.
4.5https://git.dynare.org/Dynare/dynare/-/issues/809allow timeseries to be represented as bar graphs2019-06-19T15:38:02ZHoutan Bastaniallow timeseries to be represented as bar graphs4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/810investigate legend placement options2019-06-19T15:38:02ZHoutan Bastaniinvestigate legend placement optionsCan they be automatically placed?
Can they be placed in the middle of the plot?
Can they be automatically placed?
Can they be placed in the middle of the plot?
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/811move reporting code to a different repository and include it as a submodule2019-06-19T15:38:02ZHoutan Bastanimove reporting code to a different repository and include it as a submoduleEmails on Nov 29, 2014
Emails on Nov 29, 2014
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/812Potentially make oo_recursive_ accessible by default.2019-06-19T15:38:02ZJohannes PfeiferPotentially make oo_recursive_ accessible by default.See http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6274
See http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6274
4.5Johannes PfeiferJohannes Pfeiferhttps://git.dynare.org/Dynare/dynare/-/issues/822Investigate MS-SBVAR bug2019-06-19T15:38:02ZHoutan BastaniInvestigate MS-SBVAR bugEmail from Stéphane Lhuissier 10 Dec 3:32PM
Email from Stéphane Lhuissier 10 Dec 3:32PM
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/823Clear up unused or stale files2019-06-19T15:38:02ZJohannes PfeiferClear up unused or stale files1. In Master we have a function `PosteriorFilterSmootherAndForecast.m` that seems not be called by any other function. Can it be deleted?
2. In Master, we have both `rndprior.m`, used only in `forcst_unc`, and `prior_draw.m` to draw fr...1. In Master we have a function `PosteriorFilterSmootherAndForecast.m` that seems not be called by any other function. Can it be deleted?
2. In Master, we have both `rndprior.m`, used only in `forcst_unc`, and `prior_draw.m` to draw from the prior. I would suggest to switch to the latter and delete the first one, because `rndprior.m` does not check for violation of prior bounds.
3. The `forcst_unc.m` also does not seem to be used. Can it be deleted?
4.5Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/820Clean up setting of bayestopt_.mf* in dynare_estimation_init2019-06-19T15:38:02ZJohannes PfeiferClean up setting of bayestopt_.mf* in dynare_estimation_initThe setting of fields like `bayestopt_.mf0` is present twice and seems partially recursive. This is confusing and error-prone. We should make sure there are not redundant definitions.
The setting of fields like `bayestopt_.mf0` is present twice and seems partially recursive. This is confusing and error-prone. We should make sure there are not redundant definitions.
4.5MichelJuillardMichelJuillardhttps://git.dynare.org/Dynare/dynare/-/issues/838fix parallel on os x2019-06-19T15:38:02ZHoutan Bastanifix parallel on os xSee: http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6373
respond there when fixed
See: http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6373
respond there when fixed
4.5Marco RattoMarco Rattohttps://git.dynare.org/Dynare/dynare/-/issues/841Investigate crash in bytecode due to incompatible dimensions of jacobia_2019-06-19T15:38:02ZJohannes PfeiferInvestigate crash in bytecode due to incompatible dimensions of jacobia_See Email from 22.01.2015
The problem is due to some exogenous (e7, e8) being declared but not used in the model. Removing them solves the issue.
See Email from 22.01.2015
The problem is due to some exogenous (e7, e8) being declared but not used in the model. Removing them solves the issue.
4.5MichelJuillardHoutan BastaniMichelJuillardhttps://git.dynare.org/Dynare/dynare/-/issues/843Check why name GF is suddenly blocked in preprocessor2019-06-19T15:38:01ZJohannes PfeiferCheck why name GF is suddenly blocked in preprocessorThe mod-file
```
////////////////////////////////////////////////////////////////////////////////////
////// Deregulation at the Cost of Shadow Work /////////////////////////////////////
////// Deterministic simulation file with es...The mod-file
```
////////////////////////////////////////////////////////////////////////////////////
////// Deregulation at the Cost of Shadow Work /////////////////////////////////////
////// Deterministic simulation file with estimated parameters, South Africa ///////
////// R. Anand, P. Khera, Z. Munkacsi, M. Saxegaard ///////////////////////////////
////// IMF, Jan 2015 ///////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////////
```
For some reason, it thinks GF is a reserved name/token. It works in 4.4.3.
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/844Make sure order=3 implies k_order_solver in the preprocessor2019-06-19T15:38:01ZJohannes PfeiferMake sure order=3 implies k_order_solver in the preprocessorCurrently, we set `k_order_solver = 1` if `order=3` within two functions: `stoch_simul` and `simult_`. This approach is prone to problems. `stoch_simul` will not pass `k_order_solver = 1` to the `options`-structure, because it is local t...Currently, we set `k_order_solver = 1` if `order=3` within two functions: `stoch_simul` and `simult_`. This approach is prone to problems. `stoch_simul` will not pass `k_order_solver = 1` to the `options`-structure, because it is local to the function. When a user tries to directly call `resol`, this will thus fail, see http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6432
We should take this out of specialized functions and use the preprocessor to set `k_order_solver = 1` whenever `order=3`. This would assure the option is always correctly set.
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/849Make use_calibration option compatible with ML2019-06-19T15:38:00ZJohannes PfeiferMake use_calibration option compatible with MLML currently requires to specify explicit starting values inside of the `estimated_params` block, rendering the `estimated_params_init` block useless.
ML currently requires to specify explicit starting values inside of the `estimated_params` block, rendering the `estimated_params_init` block useless.
4.5Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/855preprocessor and matlab command lines2019-06-19T15:38:00ZMarco Rattopreprocessor and matlab command linesI was trying to do tests on the current status of HEAD, but I am getting an error from the preprocessor, that does no longer allow to call matlab functions with multiple output arguments, like
`[out1, out2, out3] = function_name(bla1, b...I was trying to do tests on the current status of HEAD, but I am getting an error from the preprocessor, that does no longer allow to call matlab functions with multiple output arguments, like
`[out1, out2, out3] = function_name(bla1, bla2);`
the preprocessor complains with the following message
`ERROR: gemc.dyn: line 1686, col 15: syntax error, unexpected '[', expecting '.'`
is there a new way to properly call matlab functions, or this is a bug or a desired behavior of the pre-processor?
the call to matlab is outside of any model or other block.
thank you for your help
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/857Investigate problem in .mod file2019-06-19T15:38:00ZHoutan BastaniInvestigate problem in .mod filehttp://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6577
14 endos in .mod file but preprocessor sees 15
http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6577
14 endos in .mod file but preprocessor sees 15
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/862support 32bit and 64bit preprocessors2019-06-19T15:38:00ZHoutan Bastanisupport 32bit and 64bit preprocessors- if a 64 bit preprocessor is created, rename it to `dynare_m64` (32 bit remains `dynare_m`)
- depending on whether the host OS is 32 or 64 bit, call the appropriate preprocessor from the matlab code
- if a 64 bit preprocessor is created, rename it to `dynare_m64` (32 bit remains `dynare_m`)
- depending on whether the host OS is 32 or 64 bit, call the appropriate preprocessor from the matlab code
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/867add fan charts to reporting2019-06-19T15:38:00ZHoutan Bastaniadd fan charts to reportingpass 3 series to the plot command
pass 3 series to the plot command
4.5Houtan BastaniHoutan Bastani