#218: Remove set_stationary_variables_list.m
-------------------------+--------------------------------------------------
Reporter: sebastien | Owner: stepan
Type: enhancement | Status: new
Priority: minor | Milestone: 4.3
Component: Estimation | Version:
Keywords: |
-------------------------+--------------------------------------------------
This function is basically useless now that unit_root_vars has been
removed.
It is however still called from several places.
--
Ticket URL: <https://www.dynare.org/trac/ticket/218>
Dynare <http://www.dynare.org>
The Dynare project
#86: check matrix power used in forecast
--------------------------+-------------------------------------------------
Reporter: michel | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
taking large matrix power in forecast step of the Kalman smoother routines
is expensive, but probably more accurate than recursive multiplications.
- investigate more accuracy issue
- factorise matrix decomposition for matrix power
--
Ticket URL: <https://www.dynare.org/trac/ticket/86>
Dynare <http://www.dynare.org>
The Dynare project
#83: persistent variables must be cleared at the beginning of a Dynare run
--------------------------+-------------------------------------------------
Reporter: michel | Owner: michel
Type: bug | Status: new
Priority: minor | Milestone:
Component: Core M-files | Version: 4.1.0
Keywords: |
--------------------------+-------------------------------------------------
persistent variables in *.m files trigger hard to understand errors if the
user run successively two different *.mod files with 'noclearall' option.
Whenever a function uses persistent variables, there should be an explicit
initialize option and not rely on empty persistent variables as, for
example, priordens.m currently does.
--
Ticket URL: <https://www.dynare.org/trac/ticket/83>
Dynare <http://www.dynare.org>
The Dynare project
#112: Metropolis: add the possibility for the user to give an arbitrary matrix
for the variance of the jump proposal
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner:
Type: feature | Status: new
Priority: major | Milestone: 4.2
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
Feature suggested by Fabio Canova at the Dynare Conference 2010.
--
Ticket URL: <https://www.dynare.org/trac/ticket/112>
Dynare <http://www.dynare.org>
The Dynare project
#164: consider using bvar provided by Zha and Waggoner instead of our own
--------------------------+-------------------------------------------------
Reporter: houtanb | Owner:
Type: feature | Status: new
Priority: major | Milestone: 4.3
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
Their code provides a superset of ours.
--
Ticket URL: <https://www.dynare.org/trac/ticket/164>
Dynare <http://www.dynare.org>
The Dynare project
#184: Auxiliary variables for leads.
--------------------------+-------------------------------------------------
Reporter: stepan | Owner: houtanb
Type: enhancement | Status: new
Priority: major | Milestone: 4.3
Component: Preprocessor | Version:
Keywords: |
--------------------------+-------------------------------------------------
The last loop in add_auxiliary_variables is highly inefficient. The the
residuals of the static model are evaluated (many times) to compute the
the steady state levels of the auxiliary variables. But in the
preprocessing stage, the expressions of the auxiliary variables (in terms
of the endogenous variables) are known. The preprocessor should write a
routine defining the auxiliary variables as a function of the endogenous
variables. Depending on the current options, this routine may be a matlab
function, a mex or bytecode. With such a function we won't need to infer
the steady state of the auxiliaries from the residuals of the static
model...
--
Ticket URL: <https://www.dynare.org/trac/ticket/184>
Dynare <http://www.dynare.org>
The Dynare project
#181: Display a summary of warnings at the end of Dynare run
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner:
Type: feature | Status: new
Priority: minor | Milestone: 4.3
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
At the end of a run, display a message if a warning was emitted (either by
the preprocessor, or by MATLAB/Octave code).
Some harmless warnings should probably be filtered out.
--
Ticket URL: <https://www.dynare.org/trac/ticket/181>
Dynare <http://www.dynare.org>
The Dynare project
#172: improve derivation engine for derivatives of STEADY_STATE wrt parameters
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner: sebastien
Type: enhancement | Status: new
Priority: major | Milestone: 4.3
Component: Preprocessor | Version:
Keywords: |
--------------------------+-------------------------------------------------
Currently the derivatives of STEADY_STATE operator wrt to parameters are
not handled in an efficient way, because the preprocessor does not exploit
the a priori information for identifying null derivatives. This results in
huge files for not so complicated models, which cannot be exploited by
identification routines.
The proposal is to implement an algorithm in the preprocessor for
identifying null derivatives ex ante:
- Create a non-directed graph whose nodes are the endogenous variables and
the parameters
- For each pair of nodes, add an edge between the two if there is an
equation in the static model containing both corresponding symbols
(endogenous/parameters)
- For each endogenous, its derivative wrt a parameter is always zero if
there is no path between the node representing the endogenous and the node
representing the parameter.
--
Ticket URL: <https://www.dynare.org/trac/ticket/172>
Dynare <http://www.dynare.org>
The Dynare project
#116: IRF: give the possibility to choose the starting point (at least at order 2
and above)
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner:
Type: feature | Status: new
Priority: major | Milestone: 4.2
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
In particular, give the possibility to start from the stochastic steady
state
--
Ticket URL: <https://www.dynare.org/trac/ticket/116>
Dynare <http://www.dynare.org>
The Dynare project
#115: IRF: add the possibility to change the size of the shocks in the
computations
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner:
Type: feature | Status: new
Priority: major | Milestone: 4.2
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
At order 1, it is equivalent to changing the standard deviation of the
shocks and adding the corresponding inverse transformation in the
equations.
But at orders 2 and above, the equivalence does not hold.
--
Ticket URL: <https://www.dynare.org/trac/ticket/115>
Dynare <http://www.dynare.org>
The Dynare project