dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2016-06-10T12:44:33Zhttps://git.dynare.org/Dynare/dynare/-/issues/347Use dynSeries in Dynare.2016-06-10T12:44:33ZStéphane Adjemianstepan@adjemian.euUse dynSeries in Dynare.Use dynSeries objects for the dataset considered for estimation and for some of the outputs (IRFs, forecasts, ...) stored in oo_. See branch [use-dynSeries](https://github.com/DynareTeam/dynare/tree/use-dynSeries).
Use dynSeries objects for the dataset considered for estimation and for some of the outputs (IRFs, forecasts, ...) stored in oo_. See branch [use-dynSeries](https://github.com/DynareTeam/dynare/tree/use-dynSeries).
4.5Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/346Overload numel function in dynSeries and dynDates classes2013-03-28T11:31:43ZStéphane Adjemianstepan@adjemian.euOverload numel function in dynSeries and dynDates classesIf ts is a dynSeries object then numel(ts) should return the number of variables (ts.vobs). If dd is a dynDates object then numel(dd) should return the number of dates (dd.ndat).
If ts is a dynSeries object then numel(ts) should return the number of variables (ts.vobs). If dd is a dynDates object then numel(dd) should return the number of dates (dd.ndat).
4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/348Add the possibility to instantiate dynSeries objects from an xls file.2013-09-11T15:26:00ZStéphane Adjemianstepan@adjemian.euAdd the possibility to instantiate dynSeries objects from an xls file.This feature is necessary to replace all the existing code related to the datasets by the dynSeries class.
This feature is necessary to replace all the existing code related to the datasets by the dynSeries class.
Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/342Better documentation of parser error messages (line and column numbers)2013-05-31T17:28:42ZJohannes PfeiferBetter documentation of parser error messages (line and column numbers)Currently, we have error messages like this:
`ERROR: final.mod:201.1-3: syntax error, unexpected NAME`
The reason usually is that a semicolon is missing in the previous line, but people only look in the current line. If the error starts...Currently, we have error messages like this:
`ERROR: final.mod:201.1-3: syntax error, unexpected NAME`
The reason usually is that a semicolon is missing in the previous line, but people only look in the current line. If the error starts at 1, we might want to change the error message to
`ERROR: final.mod:201.1-3: syntax error, unexpected NAME. Please also check whether the previous line was terminated correctly with a semicolon.`
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/341Block certain user-specified names in the preprocessor2015-07-27T19:51:38ZJohannes PfeiferBlock certain user-specified names in the preprocessorAllowing for a variable names like i may generate spurious crashes, particularly when used in conjunction with a steady state file as i is both the imaginary number and often the index variable of a loop.
A similar case happens when some...Allowing for a variable names like i may generate spurious crashes, particularly when used in conjunction with a steady state file as i is both the imaginary number and often the index variable of a loop.
A similar case happens when someone names his data-file data or when he uses the mod-file name for the data-file. If the datafile for bkk.mod is named bkk.xls and the user only specifies data_file=bkk, Dynare will enter an infinite loop by calling bkk.m over and over again.
https://git.dynare.org/Dynare/dynare/-/issues/338Clarify and potentially disentangle role played by conf_sig2019-11-21T08:36:43ZJohannes PfeiferClarify and potentially disentangle role played by conf_sigAccording to the manual, conf_sig by default is 0.9 for forecast, but after global_initialization, it is 0.6. conditional_forecast has an option with the same name and default 0.8 according to the manual.
According to the manual, conf_sig by default is 0.9 for forecast, but after global_initialization, it is 0.6. conditional_forecast has an option with the same name and default 0.8 according to the manual.
https://git.dynare.org/Dynare/dynare/-/issues/337Update manual section 5: The Configuration File2016-05-30T17:58:15ZJohannes PfeiferUpdate manual section 5: The Configuration FileThe manual is highly confusing and seems outdated compared to the Wiki
http://www.dynare.org/DynareWiki/ParallelDynare
For example, the configuration file is case sensitive, but the manual uses the wrong COMPUTER NAME instead of the co...The manual is highly confusing and seems outdated compared to the Wiki
http://www.dynare.org/DynareWiki/ParallelDynare
For example, the configuration file is case sensitive, but the manual uses the wrong COMPUTER NAME instead of the correct ComputerName as indicate by the Wiki. Moreover, a link to the Wiki might be helpful.
4.5Johannes PfeiferJohannes Pfeiferhttps://git.dynare.org/Dynare/dynare/-/issues/339Clarify difference between Bayesian HPDI and classical confidence bands in ma...2021-08-17T10:24:01ZJohannes PfeiferClarify difference between Bayesian HPDI and classical confidence bands in manualMention in manual that ML gives CIs and not HPDIs. More fundamentally, I am not sure whether it is a good idea to store CIs after ML in fields named HPDinf and HPDsup.Mention in manual that ML gives CIs and not HPDIs. More fundamentally, I am not sure whether it is a good idea to store CIs after ML in fields named HPDinf and HPDsup.https://git.dynare.org/Dynare/dynare/-/issues/336Add option for easy selection of all endogeneous variables and all observable...2014-02-04T13:49:11ZJohannes PfeiferAdd option for easy selection of all endogeneous variables and all observables to estimation.See http://www.dynare.org/phpBB3/viewtopic.php?f=2&t=2026&start=0
See http://www.dynare.org/phpBB3/viewtopic.php?f=2&t=2026&start=0
https://git.dynare.org/Dynare/dynare/-/issues/335allow functions returning several values in steady_state_model2013-04-05T09:52:02ZMichelJuillardallow functions returning several values in steady_state_modelThis is necessary when one must solve more than a single equation numerically. The current syntax permits to return a variable being a vector, but there is no syntax to access a single element of this vector. An alternative would be to a...This is necessary when one must solve more than a single equation numerically. The current syntax permits to return a variable being a vector, but there is no syntax to access a single element of this vector. An alternative would be to allow a function to return a list of argument between [ ]as in Matlab syntax
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/334allow for nonzero exogenous variables in steady_state_model2013-04-05T13:24:10ZMichelJuillardallow for nonzero exogenous variables in steady_state_modelThis is necessary for using steady_state_model with deterministic models.
One possibility is add exogenous variables to the output arguments of the Matlab function. Another is to directly set oo_.exo_steady_state (and exo_det_steady_state)
This is necessary for using steady_state_model with deterministic models.
One possibility is add exogenous variables to the output arguments of the Matlab function. Another is to directly set oo_.exo_steady_state (and exo_det_steady_state)
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/333Add regular expressions in @dynSeries/subsagn2013-03-28T11:31:43ZStéphane Adjemianstepan@adjemian.euAdd regular expressions in @dynSeries/subsagnWe already have the possibility to use regular expressions in @dynSeries/subsref. The code should be factorized and reused in @dynSeries/subsagn. This would allow syntax like:
ts{GROWTH_GDP_@US,JP,FR,GB@} = ts{GDP_@US,JP,FR,GB@}.ygrowth...We already have the possibility to use regular expressions in @dynSeries/subsref. The code should be factorized and reused in @dynSeries/subsagn. This would allow syntax like:
ts{GROWTH_GDP_@US,JP,FR,GB@} = ts{GDP_@US,JP,FR,GB@}.ygrowth
where ts is a dynSeries object.
4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/332Add functionality to compute function on posterior2015-10-12T05:18:33ZJohannes PfeiferAdd functionality to compute function on posteriorCurrently, it is very hard to compute a user defined function on the posterior draws. A user asked me if we could add a functionality where the user specifies a function name which is executed on each posterior draw when we compute poste...Currently, it is very hard to compute a user defined function on the posterior draws. A user asked me if we could add a functionality where the user specifies a function name which is executed on each posterior draw when we compute posterior moments. For such a function call, we would need to clearly specify the interface. We might want to provide M_, oo_, bayestopt_, estim_params_ and the current parameter draw as generic inputs (and nothing else). The tricky part consists of specifying the output arguments and making sure we can save them. One way would be to only accept one output argument and save it to the ii element of a cell array. By putting multiple outputs into a structure, the user could still effectively save multiple outputs while keeping a clearly specified interface for us.
Upon going over all draws, we would just save the cell array to the disk. It would be up to the user to make sense of the saved stuff.
4.5https://git.dynare.org/Dynare/dynare/-/issues/331Add reset option to shocks-block2015-09-07T10:08:50ZJohannes PfeiferAdd reset option to shocks-blockCurrently the only way to set a different covariance matrix of structural shocks and measurement errors is to manually set all elements that differ from the previous shocks-statement. It would be nice to have something like
```
shocks(r...Currently the only way to set a different covariance matrix of structural shocks and measurement errors is to manually set all elements that differ from the previous shocks-statement. It would be nice to have something like
```
shocks(reset);
var e; stderr 0.9;
end;
```
that sets all elements of the M_.Sigma_e and M_.H to 0 before filling it again with the entries of the shocks-block.
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/326Change color scheme of figures to be readable on monochrome printouts2019-06-19T15:37:41ZJohannes PfeiferChange color scheme of figures to be readable on monochrome printoutsMore information will be provided soon.
More information will be provided soon.
https://git.dynare.org/Dynare/dynare/-/issues/330ReshapeMatFiles2016-06-14T20:57:38ZMarco RattoReshapeMatFilesReshapeMatFiles is currently used only for posterior IRF's. For large models it is a huge bottle-neck which is probably useless. The approach followed in prior_posterior_statistics.m is to use the pm3 utility that takes the data needed f...ReshapeMatFiles is currently used only for posterior IRF's. For large models it is a huge bottle-neck which is probably useless. The approach followed in prior_posterior_statistics.m is to use the pm3 utility that takes the data needed for plots from the non-reshaped files. Such a procedure is in the end much less time consuming than the ReshapeMatFile.
The current pm3 utility is not easily extended for irfs (matrices are 4-dimensional for irf's).
However I tried to write a pm4 utility for 4-D matrices which looks interesting.
How about removing the call in posteriorIRF to:
ReshapeMatFile
posteriorIRF_core2 (the plot utility for bayesian irf's which uses the reshaped files)
add making a new call to a pm4.m utility that replicates the behaviour of pm3 to 4-D matrices?
Marco RattoMarco Rattohttps://git.dynare.org/Dynare/dynare/-/issues/324Document kalman_algo and kalman_tol in manual2013-05-18T17:49:45ZJohannes PfeiferDocument kalman_algo and kalman_tol in manualhttps://git.dynare.org/Dynare/dynare/-/issues/323Use of relative filenames creates problems in Windows in pathological cases2013-04-30T12:59:22ZJohannes PfeiferUse of relative filenames creates problems in Windows in pathological casesI have a very long pathname for one mod-file. When using a purely relative filename in check_`posterior_analysis_data.m` like
``` matlab
name_of_the_last_post_data_file = ...
[ './' M_.dname ...
'/metropolis/' ...
...I have a very long pathname for one mod-file. When using a purely relative filename in check_`posterior_analysis_data.m` like
``` matlab
name_of_the_last_post_data_file = ...
[ './' M_.dname ...
'/metropolis/' ...
M_.fname '_' ...
generic_post_data_file_name ...
int2str(number_of_the_last_post_data_file) ...
'.mat' ];
pdfdate = get_date_of_a_file(name_of_the_last_post_data_file);
```
I get an error that the file cannot be found, although it is there. Matlab's help says
> If you get unexpected results when working with long path names, use absolute instead >of relative path names.
Hence, I added a `pwd` instead of the dot to the path-name and the above code runs without problems. Is there a particular reason for using relative names?
Transitioning to absolute names using `pwd` seems more robust and is recommended by Matlab. Thus, I would suggest to use absolute path names in the future and adding a `pwd` to existing relative path names. Such a change could be done gradually without disrupting any functionality and coexistence of old and new code is also no problem.
However, I can't speak for Linux/Mac and Octave. What do you think?
https://git.dynare.org/Dynare/dynare/-/issues/321Add preprocessor option for endogenous priors2013-03-18T12:45:30ZJohannes PfeiferAdd preprocessor option for endogenous priorsRequired is a token `endogenous prior` in the `estimation` command that sets `options_.endogenous_prior` to 1
Required is a token `endogenous prior` in the `estimation` command that sets `options_.endogenous_prior` to 1
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/320mode check2013-05-24T10:14:16ZMarco Rattomode checkI would like to allow the check plots routine to plot asymmetric plots around the mean. This would fix a couple of issues:
1) when the posterior mode goes near or at the boundary, currently the plots display the objective function for ve...I would like to allow the check plots routine to plot asymmetric plots around the mean. This would fix a couple of issues:
1) when the posterior mode goes near or at the boundary, currently the plots display the objective function for very narrow or null intervals;
2) using very large (or inf) values for mode_check_neighborhood_size, would allow to plot the objective function for the entire domain, which may possibly allow to visualize alternative local optima faraway from the current one;