Dev March 2012

dev@dynare.org

7 participants
152 discussions

[Trac] #148: Block decomposed version of decision rules
by Trac Dynare 08 Jun '12

08 Jun '12

#148: Block decomposed version of decision rules --------------------------+------------------------------------------------- Reporter: sebastien | Owner: ferhat Type: feature | Status: new Priority: major | Milestone: 4.3 Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- -- Ticket URL: <https://www.dynare.org/trac/ticket/148> Dynare <http://www.dynare.org> The Dynare project

1 3

[Trac] #216: Behaviour of "nograph" option is not consistent
by Trac Dynare 07 Jun '12

07 Jun '12

#216: Behaviour of "nograph" option is not consistent --------------------------+------------------------------------------------- Reporter: sebastien | Owner: Type: enhancement | Status: new Priority: major | Milestone: 4.3 Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- The reference manual says that with the "nograph" options, Dynare "doesn't do the graphs". This options indeed prevents Dynare from displaying graphs, but it still creates PDF/EPS files in some parts of the code (but not). For example, stoch_simul+nograph won't create PDF/EPS files for IRFs, but estimation+nograph will still create some PDF/EPS files. This is inconsistent. Moreover, some users would like to have the possibility of not saving the graphs (http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=3362) I think we should either decide that "nograph" means "do not display nor save graphs", or create a new option like "nographsave" which would allow full flexibility with regard to displaying/saving graphs. -- Ticket URL: <https://www.dynare.org/trac/ticket/216> Dynare <http://www.dynare.org> The Dynare project

1 6

[Trac] #199: the output of option forecast in estimation is incorrect in the Reference Manual
by Trac Dynare 07 Jun '12

07 Jun '12

#199: the output of option forecast in estimation is incorrect in the Reference Manual ---------------------------+------------------------------------------------ Reporter: michel | Owner: Type: bug | Status: new Priority: major | Milestone: 4.3 Component: Documentation | Version: Keywords: | ---------------------------+------------------------------------------------ If the forecast takes place after computing the posterior mode, the output is indeed saved in oo_.forecast (as correctly described in the manual) But, if the forecast takes place after Metropolis iteration and is really the posterior distribution of forecasts, the output is saved in oo_.MeanForecast and oo_.PointForecast -- Ticket URL: <https://www.dynare.org/trac/ticket/199> Dynare <http://www.dynare.org> The Dynare project

1 7

[Trac] #136: complete implementation of "shock_decomposition"
by Trac Dynare 07 Jun '12

07 Jun '12

#136: complete implementation of "shock_decomposition" --------------------------+------------------------------------------------- Reporter: michel | Owner: michel Type: enhancement | Status: new Priority: major | Milestone: 4.2 Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- add options for grouping shocks together and for choosing the set of parameters to be used -- Ticket URL: <https://www.dynare.org/trac/ticket/136> Dynare <http://www.dynare.org> The Dynare project

1 3

[Trac] #166: fix computation of the planner objective under Ramsey policy
by Trac Dynare 07 Jun '12

07 Jun '12

#166: fix computation of the planner objective under Ramsey policy --------------------------+------------------------------------------------- Reporter: sebastien | Owner: michel Type: bug | Status: new Priority: major | Milestone: Component: Core M-files | Version: 4.2.0 Keywords: | --------------------------+------------------------------------------------- The call to "evaluate_planner_objective" was commented out in f36247ceedb73ebab6be0bbc736fc6f5ce3f3bb1. -- Ticket URL: <https://www.dynare.org/trac/ticket/166> Dynare <http://www.dynare.org> The Dynare project

1 3

[Trac] #58: Implement constrained parameters for osr
by Trac Dynare 07 Jun '12

07 Jun '12

#58: Implement constrained parameters for osr --------------------------+------------------------------------------------- Reporter: sebastien | Owner: michel Type: feature | Status: new Priority: major | Milestone: 4.1 Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- -- Ticket URL: <https://www.dynare.org/trac/ticket/58> Dynare <http://www.dynare.org> The Dynare project

1 4

[Trac] #77: provide all solve_algo for all representations of the model
by Trac Dynare 06 Jun '12

06 Jun '12

#77: provide all solve_algo for all representations of the model --------------------------+------------------------------------------------- Reporter: ferhat | Owner: ferhat Type: enhancement | Status: new Priority: major | Milestone: 4.2 Component: Preprocessor | Version: Keywords: | --------------------------+------------------------------------------------- For the moment, only some combinations of block, bytecode and stack_solve_algo are available. Allow for the possibility to use all the algorithms for all model representation. -- Ticket URL: <https://www.dynare.org/trac/ticket/77> Dynare <http://www.dynare.org> The Dynare project

1 3

[Trac] #220: add a homotopy mode for simul() and for steady with endval
by Trac Dynare 06 Jun '12

06 Jun '12

#220: add a homotopy mode for simul() and for steady with endval -----------------------+---------------------------------------------------- Reporter: sebastien | Owner: Type: feature | Status: new Priority: major | Milestone: 4.3 Component: General | Version: Keywords: | -----------------------+---------------------------------------------------- Currently homotopy only exist for steady with initval. These features would be useful for GIMF at the IMF. -- Ticket URL: <https://www.dynare.org/trac/ticket/220> Dynare <http://www.dynare.org> The Dynare project

1 2

[Trac] #85: Estimation is not deterministic: a seed should be explictly given to random number generator
by Trac Dynare 06 Jun '12

06 Jun '12

#85: Estimation is not deterministic: a seed should be explictly given to random number generator --------------------------+------------------------------------------------- Reporter: sebastien | Owner: Type: bug | Status: new Priority: major | Milestone: Component: Core M-files | Version: 4.1.0 Keywords: | --------------------------+------------------------------------------------- Currently MOD files doing estimation are not deterministic: different runs of the same MOD files don't give the same results, since the seed for random number generator is not the same accross runs. The easy way to fix that is to set the seed in dynare.m. There would be a default value for the seed, or it could be changed through an option/command. A more subtle way would be to have a seed reset at the top of every major function (estimation, stoch_simul). We need to decide which way is the best. -- Ticket URL: <https://www.dynare.org/trac/ticket/85> Dynare <http://www.dynare.org> The Dynare project

5 15

[Trac] #202: conditional_variance_decomposition option fails with estimation
by Trac Dynare 06 Jun '12

06 Jun '12

#202: conditional_variance_decomposition option fails with estimation --------------------------+------------------------------------------------- Reporter: sebastien | Owner: Type: bug | Status: new Priority: major | Milestone: Component: Core M-files | Version: 4.2.1 Keywords: | --------------------------+------------------------------------------------- It looks for the M_.sigma_e_is_diagonal flag, which is only added by the preprocessor if the "shocks" block is present, based on the contents of that block. In an estimation context, this field is therefore not necessarily present. Maybe the fix is to generate the flag in the preprocessor using the contents of estimated_params. Comments please. -- Ticket URL: <https://www.dynare.org/trac/ticket/202> Dynare <http://www.dynare.org> The Dynare project

1 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Dev March 2012