stepan
/
dynare
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Moved the location of various generated files on the filesystem. 

Manually cherry-picked from a1b8bd39b2.
time-shift
Stéphane Adjemian (Charybdis) 2019-02-18 14:55:38 +01:00
parent e98d294baa
commit 7263f2e19a
Signed by untrusted user who does not match committer: stepan
GPG Key ID: A6D44CB9C64CE77B
1 changed files with 22 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
src/source/running-dynare.rst
View File

@ -39,11 +39,11 @@ by the ``dynare`` command.
file``. By default (unless ``use_dll`` option has been given to file``. By default (unless ``use_dll`` option has been given to
``model``), the preprocessor creates three intermediary files: ``model``), the preprocessor creates three intermediary files:
- ``filename.m`` - ``+FILENAME/driver.m``
Contains variable declarations, and computing tasks. Contains variable declarations, and computing tasks.
- ``FILENAME_dynamic.m`` - ``+FILENAME/dynamic.m``
Contains the dynamic model equations. Note that Dynare might Contains the dynamic model equations. Note that Dynare might
introduce auxiliary equations and variables (see introduce auxiliary equations and variables (see
@ -68,7 +68,7 @@ by the ``dynare`` command.
be 15. Then the 15th column of the Jacobian is the derivative be 15. Then the 15th column of the Jacobian is the derivative
with respect to ``c(+1)``. with respect to ``c(+1)``.
- ``FILENAME_static.m`` - ``+FILENAME/static.m``
Contains the long run static model equations. Note that Dynare Contains the long run static model equations. Note that Dynare
might introduce auxiliary equations and variables (see might introduce auxiliary equations and variables (see
@ -83,16 +83,26 @@ by the ``dynare`` command.
These files may be looked at to understand errors reported at the These files may be looked at to understand errors reported at the
simulation stage. simulation stage.
``dynare`` will then run the computing tasks by executing ``FILENAME.m``. ``dynare`` will then run the computing tasks by executing
``+FILENAME/driver.m``. If a user needs to rerun the computing
tasks without calling the preprocessor (or without calling the
:mcomm:`dynare` command), for
instance because he has modified the script, he just have to type
the following on the command line:
A few words of warning are warranted here: the filename of the .. code-block:: matlab
``.mod`` file should be chosen in such a way that the generated
``.m`` files described above do not conflict with ``.m`` files >> FILENAME.driver
provided by MATLAB/Octave or by Dynare. Not respecting this rule
could cause crashes or unexpected behaviour. In particular, it A few words of warning are warranted here: under Octave the
means that the ``.mod`` file cannot be given the name of a filename of the ``.mod`` file should be chosen in such a way that
MATLAB/Octave or Dynare command. Under Octave, it also means that the generated ``.m`` files described above do not conflict with
the ``.mod`` file cannot be named ``test.mod``. ``.m`` files provided by Octave or by Dynare. Not
respecting this rule could cause crashes or unexpected
behaviour. In particular, it means that the ``.mod`` file cannot
be given the name of an Octave or Dynare command. For instance, under
Octave, it also means that the ``.mod`` file cannot be named
``test.mod`` or ``example.mod``.
*Options* *Options*