dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2013-02-21T14:54:08Zhttps://git.dynare.org/Dynare/dynare/-/issues/275Fix estimation to work with both matio 1.3 and 1.52013-02-21T14:54:08ZSébastien VillemotFix estimation to work with both matio 1.3 and 1.5Some function definitions have changed in the new matio library version.
Still need to support 1.3 because Debian takes years to update its software :)
Some function definitions have changed in the new matio library version.
Still need to support 1.3 because Debian takes years to update its software :)
https://git.dynare.org/Dynare/dynare/-/issues/274On Windows, nan and inf are incorrectly translated in <filename>.m2013-02-21T14:54:08ZSébastien VillemotOn Windows, nan and inf are incorrectly translated in <filename>.mUnder Windows 7 (and possibly Windows XP, need to check), the nan and inf values are respectively printed as 1.#IND and 1.#INF in the M-files generated by the preprocessor. This obviously leads to a crash.
Under Windows 7 (and possibly Windows XP, need to check), the nan and inf values are respectively printed as 1.#IND and 1.#INF in the M-files generated by the preprocessor. This obviously leads to a crash.
https://git.dynare.org/Dynare/dynare/-/issues/272graph_format with multiple formats2013-02-21T14:55:30ZSébastien Villemotgraph_format with multiple formatsCurrently the option graph_format only allows only one format at a time to be selected.
This can be a strong limitation (assume one wants both eps for latex and fig to handle and edit plots).
We should allow multiple entries with a prep...Currently the option graph_format only allows only one format at a time to be selected.
This can be a strong limitation (assume one wants both eps for latex and fig to handle and edit plots).
We should allow multiple entries with a preprocessor syntax
graph_format =(eps,fig)
The preprocessor would define the variable in options_ as:
options_.graph_format = char('eps', 'fig' );
which would properly be handled in dyn_saveas by changing strcmp with strmatch.
https://git.dynare.org/Dynare/dynare/-/issues/271correct initialization of simulation variables2014-04-08T15:53:59ZSébastien Villemotcorrect initialization of simulation variables1) the current implementation process on the fly the initialization information provided by initval, endval and shocks, creating along the way oo_.endo_simul, oo_.exo_simul and oo_.exo_det_simul (information provided by histval is now co...1) the current implementation process on the fly the initialization information provided by initval, endval and shocks, creating along the way oo_.endo_simul, oo_.exo_simul and oo_.exo_det_simul (information provided by histval is now correctly stored in M_ before processing)
2) this implementation is prone to errors and forces users to respect a strict order of declaration. Simple checks of compliance with this order prevents users some legitimate usage such as macro loops
3) the solution is to record the initialization information in fields of M_ and to create/initialized oo_.endo_simul, oo_.exo_simul and oo_.exo_det_simul just before they are used.
4) set_shocks, make_y and make_ex should be rewritten and, for the last two, their name changed.
https://git.dynare.org/Dynare/dynare/-/issues/270Determinant computation in marginal_density.m looks sub-optimal2015-08-06T13:33:30ZSébastien VillemotDeterminant computation in marginal_density.m looks sub-optimalIn marginal_density.m, the determinant is computed (at three places) using the det() function. This function is known to be less precise than a Cholesky-based determinant computation when the determinant is close to zero.
Stéphane think...In marginal_density.m, the determinant is computed (at three places) using the det() function. This function is known to be less precise than a Cholesky-based determinant computation when the determinant is close to zero.
Stéphane thinks that the Cholesky was used before, so we need to understand why this has changed, and therefore whether we can go back to the Cholesky.
Issue reported by Gilles Bélanger (Ministère des Finances du Québec)
https://git.dynare.org/Dynare/dynare/-/issues/269add dynare_version() to the manual2013-02-21T14:55:30ZSébastien Villemotadd dynare_version() to the manualhttps://git.dynare.org/Dynare/dynare/-/issues/268In Dynare++, use libmatio instead of home-made routines for MAT files2013-02-21T14:55:30ZSébastien VillemotIn Dynare++, use libmatio instead of home-made routines for MAT fileshttps://git.dynare.org/Dynare/dynare/-/issues/266allow inf in threshold redform option of sensitivity analysis2013-02-21T14:55:30ZSébastien Villemotallow inf in threshold redform option of sensitivity analysisCurrently, only real numbers are accepted by the option
threshold_redform of the sensitivity toolbox.
However, it would be handful to allow inf as input, e.g. if one wants to filter positive numbers in an irf, one would like to use a syn...Currently, only real numbers are accepted by the option
threshold_redform of the sensitivity toolbox.
However, it would be handful to allow inf as input, e.g. if one wants to filter positive numbers in an irf, one would like to use a syntax [0 inf].
https://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/264add checksum to download section of web site2013-02-21T14:55:30ZSébastien Villemotadd checksum to download section of web sitehttps://git.dynare.org/Dynare/dynare/-/issues/262unify names for maxit options2019-02-08T08:31:00ZSébastien Villemotunify names for maxit optionsSeveral functions need an optional maximum number of iterations. There is currently no unified name style for these options.
Until now, we tried to have exactly the same name for the option in the language and the options_ fieldname.
...Several functions need an optional maximum number of iterations. There is currently no unified name style for these options.
Until now, we tried to have exactly the same name for the option in the language and the options_ fieldname.
In that case, I wonder if we should not have always maxit in the language and specialized the fieldname with a reference to the function. For example
maxit in steady -> options_.solve_maxit
Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/255Check for consistent use of dataset_.descriptive.mean vs. bayestopt_.mean_var...2016-03-23T13:17:57ZSébastien VillemotCheck for consistent use of dataset_.descriptive.mean vs. bayestopt_.mean_varobs in smoother and estimationCurrently, both structures are still present. prior_posterior_statistics.m sets
bayestopt_.mean_varobs = dataset.descriptive.mean';
to have both. Thus, use should be made consistent and storage be confined to one structure. As the mea...Currently, both structures are still present. prior_posterior_statistics.m sets
bayestopt_.mean_varobs = dataset.descriptive.mean';
to have both. Thus, use should be made consistent and storage be confined to one structure. As the mean of the data belongs to the dataset and not the estimation, the dataset_ structure is better suited than bayestopt_.
https://git.dynare.org/Dynare/dynare/-/issues/253bytecode: implement the possibility of handling complex numbers2013-02-21T14:56:04ZSébastien Villemotbytecode: implement the possibility of handling complex numbersFor some models (GIMF in particular), it would be interesting if the bytecode DLL could switch to complex numbers when the solver go into an area outside the domain of definition of functions in the real numbers.
MATLAB routines already...For some models (GIMF in particular), it would be interesting if the bytecode DLL could switch to complex numbers when the solver go into an area outside the domain of definition of functions in the real numbers.
MATLAB routines already do this, and it helps a lot solving complicated problems.
https://git.dynare.org/Dynare/dynare/-/issues/251SMM: create preprocessor interface, make it compatible with Octave2020-05-28T08:57:07ZSébastien VillemotSMM: create preprocessor interface, make it compatible with OctaveIn particular, the current code is not compatible with Octave since it uses RandStream at several places.
In particular, the current code is not compatible with Octave since it uses RandStream at several places.
https://git.dynare.org/Dynare/dynare/-/issues/248Add tests for the parallelization engine2019-06-19T15:37:42ZSébastien VillemotAdd tests for the parallelization engineMarco RattoMarco Rattohttps://git.dynare.org/Dynare/dynare/-/issues/244Improve on the Dynare FAQ2014-01-28T16:54:11ZSébastien VillemotImprove on the Dynare FAQThere is already a FAQ on www.dynare.org, but it is outdated and incomplete.
Johannes Pfeifer has expressed interest in making a better FAQ.
It should probably become a wiki page, referenced to by a sticky post on the forum.
There is already a FAQ on www.dynare.org, but it is outdated and incomplete.
Johannes Pfeifer has expressed interest in making a better FAQ.
It should probably become a wiki page, referenced to by a sticky post on the forum.
https://git.dynare.org/Dynare/dynare/-/issues/243Publicly distribute the Dynare slides2019-09-09T12:34:39ZSébastien VillemotPublicly distribute the Dynare slidesWe already distribute the slides on the summerschool temporary website, but this is not very visible. We should probably have a more permanent location, and maybe also add them in the Dynare package.
Also, we may consider putting the La...We already distribute the slides on the summerschool temporary website, but this is not very visible. We should probably have a more permanent location, and maybe also add them in the Dynare package.
Also, we may consider putting the LaTeX source in git.
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/239Add the possibility of having intermediate files elsewhere than in current di...2018-11-08T09:54:29ZSébastien VillemotAdd the possibility of having intermediate files elsewhere than in current directoryCurrently Dynare creates all its intermediate files (dynamic, static, ...) in the current directory.
It would be useful to have the possibility of choosing the directory where intermediate files are created.
Requested by Derek Anderson...Currently Dynare creates all its intermediate files (dynamic, static, ...) in the current directory.
It would be useful to have the possibility of choosing the directory where intermediate files are created.
Requested by Derek Anderson from IMF Modeling Unit.
https://git.dynare.org/Dynare/dynare/-/issues/240rewrite getPowerDeriv assignments in temporary terms2021-08-15T19:50:56ZSébastien Villemotrewrite getPowerDeriv assignments in temporary termsFrom Stephane:
In models with power functions of the form x**a (utility functions, production functions, agregation functions, quadratic costs, ...) the evaluation of the jacobian matrix (or higher order derivates) n...From Stephane:
In models with power functions of the form x**a (utility functions, production functions, agregation functions, quadratic costs, ...) the evaluation of the jacobian matrix (or higher order derivates) necessitate potentially a huge number of calls to the routine getPowerDeriv (the name of the routine is explicit enough). In my example (a real business cycle model with perfect foresight) most of the time is spent in this routine, while, if my understanding is correct, this is not necessary because x>0.
I wrote a mex file (see the new branch called mex-!GetPowerDeriv) as a replacement for the matlab routine, unfortunatly the overhead cost is so high that the use of the mex file increases the total time of execution!
In my case I resolved the issue by using option use_dll, but this is not a solution for the majority of our users (they would have to install cygwin/gcc and configure matlab/mex). So my question is: Do we really need to call this routine in all situations ? Would it not be possible to replace calls to this routine by something like:
if (abs(x)>1e-12)
tmp = ANALYTICAL_EXPRESSION_OF_THE_DERIVATIVEx,params;
else
tmp = 0;
end
https://git.dynare.org/Dynare/dynare/-/issues/237Document sbvar command2021-08-17T11:22:57ZSébastien VillemotDocument sbvar commandMichelJuillardMichelJuillard