dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2013-02-21T15:05:27Zhttps://git.dynare.org/Dynare/dynare/-/issues/1201st order coefficients reported by k-order DLL are not the same than Dynare++2013-02-21T15:05:27ZSébastien Villemot1st order coefficients reported by k-order DLL are not the same than Dynare++Reproducible on a model sent by Dario Caldara.
Reproducible on a model sent by Dario Caldara.
https://git.dynare.org/Dynare/dynare/-/issues/722nd and 3rd order approximation of purely backward and forward models2016-06-10T12:51:41ZSébastien Villemot2nd and 3rd order approximation of purely backward and forward models- need to write specialized code for 2nd and 3rd order approximation of purely backward and forward models
- need to write specialized code for 2nd and 3rd order approximation of purely backward and forward models
https://git.dynare.org/Dynare/dynare/-/issues/1039@#include should pull in mod files off the MATLAB path, not just the current ...2019-06-19T15:37:54ZTom Holden@#include should pull in mod files off the MATLAB path, not just the current folderTo enable @#include to be easily used with libraries of utilities e.g. https://github.com/tholden/DynareTransformationEngine , it needs to be able to include MOD files that are not in the current folder, and are instead somewhere in the ...To enable @#include to be easily used with libraries of utilities e.g. https://github.com/tholden/DynareTransformationEngine , it needs to be able to include MOD files that are not in the current folder, and are instead somewhere in the MATLAB path. Copying and pasting is both messy and unreliable.
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/1661`fast` option to dynare does not recompile every time the model changes2019-10-08T07:17:30ZHoutan Bastani`fast` option to dynare does not recompile every time the model changesThe temporary terms of the equations are not printed in the buffer on which the checksum is calculated. Hence, if the model is changed in a term that then becomes a temporary term, the checksum does not change.The temporary terms of the equations are not printed in the buffer on which the checksum is calculated. Hence, if the model is changed in a term that then becomes a temporary term, the checksum does not change.4.6Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/1714`get_error_message` does not return an output when `options_.noprint = 1`2020-03-10T08:26:24ZAliaksandr Zaretski`get_error_message` does not return an output when `options_.noprint = 1`The function `get_error_message` must return an output, but does so only when `options_.noprint = 0`. Hence, there is an unexpected error message when both `info(1) > 0` and `options_.noprint = 1`. To replicate, see attached [example1_ed...The function `get_error_message` must return an output, but does so only when `options_.noprint = 0`. Hence, there is an unexpected error message when both `info(1) > 0` and `options_.noprint = 1`. To replicate, see attached [example1_ed.mod](/uploads/f0716731f7540ce7030e68dd2e5de1eb/example1_ed.mod), where I set `alpha = -0.36` to generate an error and added the `noprint` option. See attached slightly revised [print_info.m](/uploads/30439caa39aacbdac9f9e1b2a644483b/print_info.m) and [get_error_message.m](/uploads/c15787c57bb9e46b6a3136be9a803db9/get_error_message.m) where the issue is solved.https://git.dynare.org/Dynare/dynare/-/issues/1337A linear model with options_.risky_steadystate = 1; and k_order_solver causes...2019-06-19T15:37:45ZHoutan BastaniA linear model with options_.risky_steadystate = 1; and k_order_solver causes a crashShould stop with error if a linear model is used.
See the mod file: https://gist.github.com/houtanb/d2eaa90121e26bdace138bf477c631eeShould stop with error if a linear model is used.
See the mod file: https://gist.github.com/houtanb/d2eaa90121e26bdace138bf477c631ee4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/1597Accept UTF-8 in .mod file2021-08-17T10:56:01ZHoutan BastaniAccept UTF-8 in .mod filehttps://git.dynare.org/Dynare/dynare/-/issues/543Acceptance Rates2019-06-19T15:38:12ZStéphane Adjemianstepan@adjemian.euAcceptance Rates*Created by: MichaelSpece*
Suggested labels: documentation, estimation, enhancement
Document acceptance rate behavior as output and saved by dynare in estimation (e.g. see http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=5051). Someth...*Created by: MichaelSpece*
Suggested labels: documentation, estimation, enhancement
Document acceptance rate behavior as output and saved by dynare in estimation (e.g. see http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=5051). Something like, “If mh_replic > 0 and load_mh_file is specified, only the new draws are used in updating the acceptance rate.”
As an enhancement, I suggest changing all uses of “acceptation” to “acceptance.” (Acceptation is non-standard usage in the context of Monte Carlo, and does not make sense given the narrow connotations of acceptation.)
4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/860Account for loglinear option with lagged/leaded exogenous variables2019-06-19T15:38:00ZJohannes PfeiferAccount for loglinear option with lagged/leaded exogenous variablesThe problem is that e.g. news shocks are incompatible with the `loglinear` option. The reason is that they require auxiliary variables with mean 0 so that taking the log of them is not possible. The easiest way to deal with this is proba...The problem is that e.g. news shocks are incompatible with the `loglinear` option. The reason is that they require auxiliary variables with mean 0 so that taking the log of them is not possible. The easiest way to deal with this is probably state this explicitly in the manual and let the preprocessor throw out an error when `loglinear` is used and there there is a substitution of exogenous lags.
MichelJuillardMichelJuillardhttps://git.dynare.org/Dynare/dynare/-/issues/1272Account for MAC in AnalyseComputationalEnvironment.m and GiveCPUnumber.m2019-06-19T15:37:49ZJohannes PfeiferAccount for MAC in AnalyseComputationalEnvironment.m and GiveCPUnumber.mThe call to
`[si0 de0]=system('grep processor /proc/cpuinfo');`
should be
`[si0 de0]=system('sysctl -a | grep machdep.cpu | grep core_count');` (see http://fortysomethinggeek.blogspot.de/2012/11/getting-cpu-info-from-command-line-in.htm...The call to
`[si0 de0]=system('grep processor /proc/cpuinfo');`
should be
`[si0 de0]=system('sysctl -a | grep machdep.cpu | grep core_count');` (see http://fortysomethinggeek.blogspot.de/2012/11/getting-cpu-info-from-command-line-in.html)
`GiveCPUnumber.m` then also needs to be adjusted to account for this.
Related to #838
4.5https://git.dynare.org/Dynare/dynare/-/issues/109adapt model_steady_state for deterministic simulations2013-02-21T15:05:27ZSébastien Villemotadapt model_steady_state for deterministic simulations- how to call <modfile>_steadystate.m for initial or terminal values?
- how to set steadystate values for exogenous variables in model_steady_state?
- how to call <modfile>_steadystate.m for initial or terminal values?
- how to set steadystate values for exogenous variables in model_steady_state?
4.3https://git.dynare.org/Dynare/dynare/-/issues/143adapt sim1.m for purely forward models and remove simk.m2013-02-21T15:03:52ZSébastien Villemotadapt sim1.m for purely forward models and remove simk.mFixed in 4b2405a0141473145db78e7a7af2754e981e3bae
Fixed in 4b2405a0141473145db78e7a7af2754e981e3bae
4.3https://git.dynare.org/Dynare/dynare/-/issues/180Adapt the testsuite for MATLAB2013-02-21T15:00:42ZSébastien VillemotAdapt the testsuite for MATLABIn particular this will help verifying that all functionalities work with old MATLAB versions.
In particular this will help verifying that all functionalities work with old MATLAB versions.
https://git.dynare.org/Dynare/dynare/-/issues/370Add (preprocessor) option for Fernandez-Villaverde et al (2012) type of IRFs ...2013-05-11T11:44:55ZJohannes PfeiferAdd (preprocessor) option for Fernandez-Villaverde et al (2012) type of IRFs in stoch_simulA frequent question is how to generate IRFs at order=3 that look like the ones in Fernandez-Villaverde et al (2012) "Risk matters". I will add a corresponding code over the next two weeks. But a preprocessor option would still be needed....A frequent question is how to generate IRFs at order=3 that look like the ones in Fernandez-Villaverde et al (2012) "Risk matters". I will add a corresponding code over the next two weeks. But a preprocessor option would still be needed. There are two issues that need to be discussed.
1. What should be the naming of the option? I would suggest something like `ergodic_mean_irf` as the IRFs are computed relative to the ergodic mean.
2. Should we allow for flexibility in the number of periods over which to compute the ergodic mean? If yes, we would need another option `ergodic_mean_periods`
https://git.dynare.org/Dynare/dynare/-/issues/279add --with-slicot and --with-matio options to configure2013-02-21T14:54:08ZSébastien Villemotadd --with-slicot and --with-matio options to configureAdd m4/ax_slicot.m4 and m4/ax_matio.m4 to conform with --with-gsl.
Add m4/ax_slicot.m4 and m4/ax_matio.m4 to conform with --with-gsl.
https://git.dynare.org/Dynare/dynare/-/issues/234add @#elseif to macroprocessor2019-08-19T15:05:51ZSébastien Villemotadd @#elseif to macroprocessorsaves users from:
if
else
if
else
endif
endif
saves users from:
if
else
if
else
endif
endif
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/223add @#ifdef functionality to macroprocessor2013-02-21T14:59:19ZSébastien Villemotadd @#ifdef functionality to macroprocessorCurrently, we only support @#if, meaning that every macro variable must be predefined. For large mod files with many clauses where you may want to include/exclude portions easily, this becomes cumbersome because it requires you to define...Currently, we only support @#if, meaning that every macro variable must be predefined. For large mod files with many clauses where you may want to include/exclude portions easily, this becomes cumbersome because it requires you to define all macro used anywhere to be equal to zero at the beginning of the modfile.
It is also cumbersome when certain macro variables are only defined based on the existence of others, making the definition at the beginning of the mod file all that much longer.
See GPM6.mod to get the general idea.
4.3https://git.dynare.org/Dynare/dynare/-/issues/265add @#ifndef to macroprocessor2013-02-21T14:55:30ZSébastien Villemotadd @#ifndef to macroprocessorfor gpm
for gpm
https://git.dynare.org/Dynare/dynare/-/issues/1502Add a dynare option for specifying if we consider a stochastic or determinist...2019-06-19T15:37:42ZStéphane Adjemianstepan@adjemian.euAdd a dynare option for specifying if we consider a stochastic or deterministic modelSee discussion in #1501.See discussion in #1501.4.6Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/220add a homotopy mode for simul() and for steady with endval2016-06-01T12:23:27ZSébastien Villemotadd a homotopy mode for simul() and for steady with endvalCurrently homotopy only exist for steady with initval.
These features would be useful for GIMF at the IMF.
Currently homotopy only exist for steady with initval.
These features would be useful for GIMF at the IMF.