[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Once the model file is written, Dynare is invoked using the
dynare
command at the MATLAB or Octave prompt (with the filename
of the ‘.mod’ given as argument).
In practice, the handling of the model file is done in two steps: in the
first one, the model and the processing instructions written by the user
in a model file are interpreted and the proper MATLAB or GNU
Octave instructions are generated; in the second step, the program
actually runs the computations. Boths steps are triggered automatically
by the dynare
command.
Description
This command launches Dynare and executes the instructions included in ‘FILENAME.mod’. This user-supplied file contains the model and the processing instructions, as described in The Model file.
dynare
begins by launching the preprocessor on the ‘.mod’
file. By default (unless use_dll
option has been given to
model
), the preprocessor creates three intermediary files:
Contains variable declarations, and computing tasks
Contains the dynamic model equations. Note that Dynare might introduce auxiliary equations and variables (see section Auxiliary variables). Outputs are the residuals of the dynamic model equations in the order the equations were declared and the Jacobian of the dynamic model equations. For higher order approximations also the Hessian and the third-order derivates are provided. When computing the Jacobian of the dynamic model, the order of the endogenous variables in the columns is stored in M_.lead_lag_incidence
. The rows of this matrix represent time periods: the first row denotes a lagged (time t-1) variable, the second row a contemporaneous (time t) variable, and the third row a leaded (time t+1) variable. The colums of the matrix represent the endogenous variables in their order of declaration. A zero in the matrix means that this endogenous does not appear in the model in this time period. The value in the M_.lead_lag_incidence
matrix corresponds to the column of that variable in the Jacobian of the dynamic model. Example: Let the second declared variable be c
and the (3,2)
entry of M_.lead_lag_incidence
be 15
. Then the 15
th column of the Jacobian is the derivative with respect to y(+1)
.
Contains the long run static model equations. Note that Dynare might introduce auxiliary equations and variables (see section Auxiliary variables). Outputs are the residuals of the static model equations in the order the equations were declared and the Jacobian of the static equations. Entry (i,j)
of the Jacobian represents the derivative of the i
th static model equation with respect to the j
th model variable in declaration order.
These files may be looked at to understand errors reported at the simulation stage.
dynare
will then run the computing tasks by executing ‘FILENAME.m’.
Options
noclearall
By default, dynare
will issue a clear all
command to
MATLAB or Octave, thereby deleting all workspace variables; this options
instructs dynare
not to clear the workspace
debug
Instructs the preprocessor to write some debugging information about the scanning and parsing of the ‘.mod’ file
notmpterms
Instructs the preprocessor to omit temporary terms in the static and dynamic files; this generally decreases performance, but is used for debugging purposes since it makes the static and dynamic files more readable
savemacro[=FILENAME]
Instructs dynare
to save the intermediary file which is obtained
after macro-processing (see section Macro-processing language); the saved
output will go in the file specified, or if no file is specified in
‘FILENAME-macroexp.mod’
onlymacro
Instructs the preprocessor to only perform the macro-processing step, and stop just after. Mainly useful for debugging purposes or for using the macro-processor independently of the rest of Dynare toolbox.
nolinemacro
Instructs the macro-preprocessor to omit line numbering information in
the intermediary ‘.mod’ file created after the maco-processing
step. Useful in conjunction with savemacro
when one wants that to
reuse the intermediary ‘.mod’ file, without having it cluttered by
line numbering directives.
nolog
Instructs Dynare to no create a logfile of this run in ‘FILENAME.log’. The default is to create the logfile.
nowarn
Suppresses all warnings.
warn_uninit
Display a warning for each variable or parameter which is not initialized. See section Parameter initialization, or load_params_and_steady_state for initialization of parameters. See section Initial and terminal conditions, or load_params_and_steady_state for initialization of endogenous and exogenous variables.
console
Activate console mode. In addition to the behavior of
nodisplay
, Dynare will not use graphical waitbars for long
computations.
nograph
Activate the nograph
option (see nograph), so that Dynare will not produce any
graph
nointeractive
Instructs Dynare to not request user input
cygwin
Tells Dynare that your MATLAB is configured for compiling MEX files with
Cygwin (see section Software requirements). This option is only available
under Windows, and is used in conjunction with use_dll
.
msvc
Tells Dynare that your MATLAB is configured for compiling MEX files with
Microsoft Visual C++ (see section Software requirements). This option is
only available under Windows, and is used in conjunction with
use_dll
.
parallel[=CLUSTER_NAME]
Tells Dynare to perform computations in parallel. If CLUSTER_NAME is passed, Dynare will use the specified cluster to perform parallel computations. Otherwise, Dynare will use the first cluster specified in the configuration file. See section The Configuration File, for more information about the configuration file.
conffile=FILENAME
Specifies the location of the configuration file if it differs from the default. See section The Configuration File, for more information about the configuration file and its default location.
parallel_slave_open_mode
Instructs Dynare to leave the connection to the slave node open after computation is complete, closing this connection only when Dynare finishes processing.
parallel_test
Tests the parallel setup specified in the configuration file without executing the ‘.mod’ file. See section The Configuration File, for more information about the configuration file.
-DMACRO_VARIABLE=MACRO_EXPRESSION
Defines a macro-variable from the command line (the same effect as using
the Macro directive @#define
in a model file, see section Macro-processing language).
nostrict
Allows Dynare to issue a warning and continue processing when
initval
or endval
Output
Depending on the computing tasks requested in the ‘.mod’ file,
executing the dynare
command will leave variables containing
results in the workspace available for further processing. More
details are given under the relevant computing tasks.
The M_
, oo_
, and options_
structures are saved in
a file called ‘FILENAME_results.mat’. If they exist,
estim_params_
, bayestopt_
, dataset_
, and
estimation_info
are saved in the same file.
Example
dynare ramst dynare ramst.mod savemacro |
The output of Dynare is left into three main variables in the MATLAB/Octave workspace:
Structure containing various informations about the model.
Structure contains the values of the various options used by Dynare during the computation.
Structure containing the various results of the computations.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] |
This document was generated on December 16, 2013 using texi2html 1.82.