#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
#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
#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
#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
#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
#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
#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