dynare — executes Dynare
dynare
FILENAME[.mod]
[noclearall] [debug] [notmpterms] [savemacro [=FILENAME]] [onlymacro] [nolinemacro] [warn_uninit] [cygwin] [msvc]
dynare executes instruction included in FILENAME.mod.
This user-supplied file contains the model and the processing instructions, as described in Chapter 4, 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:
FILENAME.mContains variable declarations, and computing tasks
FILENAME_dynamic.mContains the dynamic model equations
FILENAME_static.mContains the long run static model equations
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.
noclearallBy 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
debugInstructs the preprocessor to write some debugging information about the scanning and parsing of the .mod file
notmptermsInstructs 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 14, “Macro-processing language”); the saved output will go in the file specified, or if no file is specified in FILENAME-macroexp.mod
onlymacroInstructs 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.
nolinemacroInstructs 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.
warn_uninitDisplay a warning for each variable or parameter which is not initialized. Initialization should be done through Section 3, “Parameter initialization” or load_params_and_steady_state for parameters, or through initval, endval or load_params_and_steady_state for endogenous and exogenous.
cygwinTells Dynare that your MATLAB® is configured for compiling MEX files with Cygwin (see Section 1, “Software requirements”). This option is only available under Windows, and is used in conjunction with use_dll.
msvcTells Dynare that your MATLAB® is configured for compiling MEX files with Microsoft Visual C++ (see Section 1, “Software requirements”). This option is only available under Windows, and is used in conjunction with use_dll.
Depending on the computing tasks requested in the .mod file, executing command dynare will leave in the workspace variables containing results available for further processing. More details are given under the relevant computing tasks.
The M_, oo_ and options_ structures are also saved in a file called FILENAME_results.mat.