December 2011 - Dev - dynare.org

[Trac] #133: datafile option in simul
by Trac Dynare 15 Jun '12

15 Jun '12

#133: datafile option in simul --------------------------+------------------------------------------------- Reporter: michel | Owner: ferhat Type: enhancement | Status: new Priority: major | Milestone: 4.3 Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- this option is very similar to initval_file but it requires two different files for endogenous and exogenous variables. The entry in the manual doesn't describe the required files. It may be interesting to use it for loading only trajectories for the exogenous variables. -- Ticket URL: <https://www.dynare.org/trac/ticket/133> Dynare <http://www.dynare.org> The Dynare project

1 1

[Trac] #106: Document prior distributions
by Trac Dynare 15 Jun '12

15 Jun '12

#106: Document prior distributions ---------------------------+------------------------------------------------ Reporter: sebastien | Owner: stepan Type: enhancement | Status: new Priority: major | Milestone: 4.2 Component: Documentation | Version: Keywords: | ---------------------------+------------------------------------------------ The document from Stéphane is probably the one to use. It should be added to the doc/ subdirectory, then to the build-system and to the packaging. -- Ticket URL: <https://www.dynare.org/trac/ticket/106> Dynare <http://www.dynare.org> The Dynare project

1 2

[Trac] #59: add errors to print_info.m
by Trac Dynare 14 Jun '12

14 Jun '12

#59: add errors to print_info.m --------------------------+------------------------------------------------- Reporter: michel | Owner: Type: bug | Status: new Priority: critical | Milestone: Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- info(1) == 43 (covariance matrix of shocks is not positive definite) should be added to print_info.m We need to check that all error numbers that can be present in info(1) are taken care of. We need to check with grep info *.m -- Ticket URL: <https://www.dynare.org/trac/ticket/59> Dynare <http://www.dynare.org> The Dynare project

1 7

[Trac] #228: document functions for which we have changed the calling sequence in unstable
by Trac Dynare 11 Jun '12

11 Jun '12

#228: document functions for which we have changed the calling sequence in unstable ---------------------------+------------------------------------------------ Reporter: michel | Owner: Type: feature | Status: new Priority: major | Milestone: 4.3 Component: Documentation | Version: Keywords: | ---------------------------+------------------------------------------------ The changes that we have made to several functions in unstable will break the code of people who are calling these functions directly. This will make a big mess when we release 4.3 We need to document those changes on the wiki -- Ticket URL: <https://www.dynare.org/trac/ticket/228> Dynare <http://www.dynare.org> The Dynare project

1 5

[Trac] #152: Extended path solution method
by Trac Dynare 08 Jun '12

08 Jun '12

#152: Extended path solution method --------------------------+------------------------------------------------- Reporter: sebastien | Owner: Type: feature | Status: new Priority: major | Milestone: 4.3 Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- Some code already exists, it is mainly a matter of creating an interface. -- Ticket URL: <https://www.dynare.org/trac/ticket/152> Dynare <http://www.dynare.org> The Dynare project

1 4

[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