From 53fbb07f61d9fa52c211865500b647896cf47a5d Mon Sep 17 00:00:00 2001 From: sebastien Date: Tue, 13 Oct 2009 19:09:49 +0000 Subject: [PATCH] Reference manual: updates for the 4.1 release * added Houtan to the list of developers, moved Ondra to the list of past contributors * updated installation instructions * options of "dynare" command: added "nolinemacro" and "onlymacro", updated "savemacro" * mention the possibility of specifying LaTeX names for "var", "varexo", "varexo_det", "parameters" * mention that now leads/lags can be used on exogenous variables * mention that arbitrary expressions can now be specified in the "estimated_params" family of commands * added new commands: "change_type", "model_comparison" * capitalize "MATLAB" throughout the manual * remove obsolete index and quasi-empty chapter pointing to Collard's guide git-svn-id: https://www.dynare.org/svn/dynare/trunk@3040 ac1d8469-bf42-47a9-8791-bf33cf982152 --- doc/manual.xml | 255 +++++++++++++++++++++++++++++++------------------ 1 file changed, 162 insertions(+), 93 deletions(-) diff --git a/doc/manual.xml b/doc/manual.xml index af210d25d..5f7d80860 100644 --- a/doc/manual.xml +++ b/doc/manual.xml @@ -3,7 +3,7 @@ Dynare Manual - Version 4.0.4 + Version 4.1.0 StéphaneAdjemian Université du Mans et CEPREMAP @@ -49,41 +49,13 @@ A copy of the license can be found at: http://www.gnu.org/licenses/fdl.txt -dynare -var -varexo -varexo_det -parameters -model -initval -endval -histval -shocks -periods -simul -check -stoch_simul -estimated_params -estimated_params_init -estimated_params_bounds -varobs -observation_trends -estimation -rplot -dynasave -dynatype -unit_root_vars -optim_weights -osr -osr_params -forecast Introduction What is Dynare ? -Dynare is a pre-processor and a collection of Matlab and GNU Octave routines which solve, simulate and estimate non-linear +Dynare is a pre-processor and a collection of MATLAB and GNU Octave routines which solve, simulate and estimate non-linear models with forward looking variables. It is the result of research carried at CEPREMAP by several people (see , , , and ). @@ -117,7 +89,7 @@ Starting with version 3.0, it is possible to use Dynare to estimate model parame -Currently the development team of Dynare is composed of S. Adjemian, M. Juillard, O. Kamenik, F. Mihoubi, G. Perendia, M. Ratto and S. Villemot. Several parts of Dynare use or have strongly benefited from publicly available programs by G. Anderson, F. Collard, L. Ingber, P. Klein, S. Sakata, F. Schorfheide, C. Sims, P. Soederlind and R. Wouters. +Currently the development team of Dynare is composed of S. Adjemian, H. Bastani, M. Juillard, F. Mihoubi, G. Perendia, M. Ratto and S. Villemot. Several parts of Dynare use or have strongly benefited from publicly available programs by G. Anderson, F. Collard, L. Ingber, O. Kamenik, P. Klein, S. Sakata, F. Schorfheide, C. Sims, P. Soederlind and R. Wouters. @@ -128,12 +100,12 @@ Currently the development team of Dynare is composed of S. Adjemian, M. Juillard Software requirements -Packaged versions of Dynare are available for Windows 98/NT/2000/XP/Vista, Debian GNU/Linux and Ubuntu, on Intel/AMD x86 architectures. -Dynare should work on other systems and architectures, but some compilation steps are necessary in that case. +Packaged versions of Dynare are available for Windows XP/Vista, Debian GNU/Linux and Ubuntu. +Dynare should work on other systems, but some compilation steps are necessary in that case. In order to run Dynare, you need at least one of the following: -Matlab version 6.5 or above; note that no toolbox is needed by Dynare, +MATLAB version 6.5 or above; note that no toolbox is needed by Dynare, GNU Octave version 3.0.0 or above. @@ -141,9 +113,9 @@ Dynare should work on other systems and architectures, but some compilation step Installation of GNU Octave -You can skip this step if you are planning to use only Matlab with Dynare. +You can skip this step if you are planning to use only MATLAB with Dynare. -Please refer to DynareOctave on Dynare Wiki for detailed instructions. +Please refer to Dynare Wiki for detailed instructions. @@ -155,7 +127,7 @@ After installation, Dynare can be used in any directory on your computer. It is On <trademark class="registered">Windows</trademark> -Execute the automated installer called dynare-4.x.y-win32.exe (where 4.x.y is the version number), and follow the instructions. The default installation directory is c:\dynare\4.x.y. +Execute the automated installer called dynare-4.x.y-win.exe (where 4.x.y is the version number), and follow the instructions. The default installation directory is c:\dynare\4.x.y. After installation, this directory will contain several sub-directories, among which matlab, mex and doc. @@ -167,27 +139,27 @@ After installation, Dynare can be used in any directory on your computer. It is On Debian GNU/Linux and Ubuntu -Please refer to InstallOnDebianOrUbuntu on Dynare Wiki for detailed instructions. +Please refer to Dynare Wiki for detailed instructions. -Dynare will be installed under /usr/lib/dynare. Documentation will be under /usr/share/doc/dynare. +Dynare will be installed under /usr/share/dynare and /usr/lib/dynare. Documentation will be under /usr/share/doc/dynare. For other systems You need to download Dynare source code from the Dynare website and unpack it somewhere. -Then you will need to recompile the pre-processor and the dynamic loadable libraries. Please refer to BuildingPreprocessor and BuildingDlls on Dynare Wiki. +Then you will need to recompile the pre-processor and the dynamic loadable libraries. Please refer to Dynare Wiki. Configuration -For <trademark class="registered">Matlab</trademark> +For <trademark class="registered">MATLAB</trademark> You need to add the matlab subdirectory of your Dynare -installation to Matlab path. You have two options for doing that: +installation to MATLAB path. You have two options for doing that: - Using the addpath command in the Matlab command window: + Using the addpath command in the MATLAB command window: Under Windows, assuming that you have installed Dynare at the standard location, and replacing "4.x.y" by correct version number, type: @@ -196,17 +168,17 @@ installation to Matlab path. You have Under Debian GNU/Linux or Ubuntu, type: - addpath /usr/lib/dynare/matlab + addpath /usr/share/dynare/matlab - Matlab will not remember this setting next time you run it, and you will have + MATLAB will not remember this setting next time you run it, and you will have to do it again. Via the menu entries: Select the "Set Path" entry in the "File" menu, then click on "Add Folder...", and select the matlab subdirectory of your Dynare installation. Note that you should not use "Add with Subfolders...". Apply - the settings by clicking on "Save". Note that Matlab will remember this + the settings by clicking on "Save". Note that MATLAB will remember this setting next time you run it. @@ -221,25 +193,21 @@ installation to Octave path, using the addpath at the Octave addpath c:\dynare\4.x.y\matlab -Under Debian GNU/Linux or Ubuntu, type: - - addpath /usr/lib/dynare/matlab - +Under Debian GNU/Linux or Ubuntu, there is no need to use the addpath command; the packaging does it for you. -You will also want to tell to Octave to accept the short syntax (without parentheses and quotes) for the dynare command, by typing: +If you are using an Octave version strictly older than 3.2.0, you will also want to tell to Octave to accept the short syntax (without parentheses and quotes) for the dynare command, by typing: mark_as_command dynare - -If you don't want to type these two commands every time you run Octave, -you can put them in a file called .octaverc in your home directory (under Windows this will generally by c:\Documents and Settings\USERNAME\). This file is run by Octave at every startup. +If you don't want to type this command every time you run Octave, +you can put it in a file called .octaverc in your home directory (under Windows this will generally by c:\Documents and Settings\USERNAME\). This file is run by Octave at every startup. Some words of warning -You should be very careful about the content of you Matlab or Octave path. You can display its content by simply typing path in the command window. +You should be very careful about the content of you MATLAB or Octave path. You can display its content by simply typing path in the command window. -The path should normally contain system directories of Matlab or Octave, and the matlab subdirectory of your Dynare installation. It should not contain any other Dynare-related directory, from another Dynare version of from the version you are using. However, note that Dynare will automatically add one (and only one) of the mex/2007a, mex/2007b, and mex/octave subdirectories, depending on your installation. +The path should normally contain system directories of MATLAB or Octave, and the matlab subdirectory of your Dynare installation. It should not contain any other Dynare-related directory, from another Dynare version of from the version you are using. However, note that Dynare will automatically add one (and only one) of the mex/2007a, mex/2007b, mex/2009a-64bit and mex/octave subdirectories, depending on your installation. You have to be aware that adding other directories to your path can potentially create problems, if some of your M-files have the same names than Dynare files. Your files would then override Dynare files, and make Dynare unusable. @@ -253,13 +221,13 @@ you can put them in a file called .octaverc in your home di In order to give instructions to Dynare, the user has to write a model file whose filename extension must be .mod. This file contains the description of the model and the computing tasks required by the user. Its contents is described in . -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). +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 +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. @@ -280,9 +248,11 @@ second step, the program actually runs the computations. Boths steps are trigger FILENAME[.mod] - + =FILENAME + + @@ -322,11 +292,7 @@ These files may be looked at to understand errors reported at the simulation sta - 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 - - - - Instructs dynare to save the intermediary file which is obtained after macro-processing (see ); the saved output will go in FILENAME-macroexp.mod + 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 @@ -336,6 +302,18 @@ These files may be looked at to understand errors reported at the simulation sta 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 + + [=FILENAME] + Instructs dynare to save the intermediary file which is obtained after macro-processing (see ); the saved output will go in the file specified, or if no file is specified in FILENAME-macroexp.mod + + + + 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. + + + + Instructs the macro-preprocessor to omit line numbering information in the intermediary .mod file created after the maco-processing step. Useful in conjunction with when one wants that to reuse the intermediary .mod file, without having it cluttered by line numbering directives. + @@ -382,7 +360,8 @@ In the description of Dynare commands, the following conventions are observed: MODEL_EXPRESSION indicates a mathematical expression valid in the model description (see and ) VARIABLE_NAME indicates a variable name starting with an alphabetical character and can't contain ()+-*/^=!;:@#. or accentuated characters PARAMETER_NAME indicates a parameter name starting with an alphabetical character and can't contain ()+-*/^=!;:@#. or accentuated characters -FILENAME indicates a file name valid in the underlying operating system (Windows, GNU/Linux, ...) +LATEX_NAME indicates a valid LaTeX expression in math mode (not including the dollar signs) +FILENAME indicates a filename valid in the underlying operating system; it is necessary to put it between double quotes when specifying the extension or if the filename contains a non-alphanumeric character @@ -394,6 +373,7 @@ In the description of Dynare commands, the following conventions are observed: + @@ -411,9 +391,11 @@ In the description of Dynare commands, the following conventions are observed: var VARIABLE_NAME + $LATEX_NAME$ , VARIABLE_NAME + $LATEX_NAME$ ; @@ -421,7 +403,7 @@ In the description of Dynare commands, the following conventions are observed: Description -This required command declares the endogenous variables in the model. See for the syntax of VARIABLE_NAME. +This required command declares the endogenous variables in the model. See for the syntax of VARIABLE_NAME. Optionally it is possible to give a LaTeX name to the variable. var commands can appear several times in the file and Dynare will concatenate them. @@ -450,9 +432,11 @@ var c gnp q1 q2; varexo VARIABLE_NAME + $LATEX_NAME$ , VARIABLE_NAME + $LATEX_NAME$ ; @@ -460,7 +444,7 @@ var c gnp q1 q2; Description -This optional command declares the exogenous variables in the model. See for the syntax of VARIABLE_NAME. +This optional command declares the exogenous variables in the model. See for the syntax of VARIABLE_NAME. Optionally it is possible to give a LaTeX name to the variable. Exogenous variables are required if the user wants to be able to apply shocks to her model. @@ -484,7 +468,7 @@ varexo m gov; varexo_det - declares exogenous deterministic variables in a stochastic model + declares exogenous deterministic variables in a stochastic model @@ -492,9 +476,11 @@ varexo m gov; varexo_det VARIABLE_NAME + $LATEX_NAME$ , VARIABLE_NAME + $LATEX_NAME$ ; @@ -502,7 +488,7 @@ varexo m gov; Description -This optional command declares exogenous deterministic variables in a stochastic model. See for the syntax of VARIABLE_NAME. +This optional command declares exogenous deterministic variables in a stochastic model. See for the syntax of VARIABLE_NAME. Optionally it is possible to give a LaTeX name to the variable. It is possible to mix deterministic and stochastic shocks to build models where agents know from the start of the simulation about future exogenous changes. In that case will compute the rational expectation solution adding future information to the state space (nothing is shown in the output of ) and will compute a simulation conditional on initial conditions and future information. @@ -534,9 +520,11 @@ varexo_det tau; parameters PARAMETER_NAME + $LATEX_NAME$ , PARAMETER_NAME + $LATEX_NAME$ ; @@ -544,7 +532,7 @@ varexo_det tau; Description -This optional command declares parameters used in the model, in variable initialization or in shocks declarations. See for the syntax of PARAMETER_NAME. +This command declares parameters used in the model, in variable initialization or in shocks declarations. See for the syntax of PARAMETER_NAME. Optionally it is possible to give a LaTeX name to the parameter. The parameters must subsequently be assigned values, see . @@ -559,13 +547,72 @@ parameters alpha, bet; + + + + change_type + + + + change_type + modify the type of declared variables/parameters + + + + + change_type + ( + + var + varexo + varexo_det + parameters + + ) + + VARIABLE_NAME + PARAMETER_NAME + + + , + + VARIABLE_NAME + PARAMETER_NAME + + + ; + + + +Description + +Changes the types of the specified variables/parameters to another type: endogenous, exogenous, exogenous deterministic or parameter. + +It is important to understand that this command has a global effect on the .mod file: the type change is effective after, but also before, the change_type command. This command is typically used when flipping some variables for steady state calibration: typically a separate model file is used for calibration, which includes the list of variable declarations with the macro-processor, and flips some variable. + + + +Example + + +var y, w; +parameters alpha, bet; +... +change_type(var) alpha, bet; +change_type(parameters) y, w; + +Here, in the whole model file, alpha and beta will be endogenous and y and w will be parameters. + + + + Expressions Dynare distinguishes between two types of mathematical expressions: those that are used to describe the model, and those that are used outside the model block (e.g. for initializing parameters or variables, or as command options). In this manual, those two types of expressions are respectively denoted by MODEL_EXPRESSION and EXPRESSION. - Unlike Matlab or Octave expressions, Dynare expressions are necessarily scalar ones: they cannot contain matrices or evaluate to matricesNote that arbitrary Matlab or Octave expressions can be put in a .mod file, but those expressions have to be on separate lines, generally at the end of the file for post-processing purposes. They are not interpreted by Dynare, and are simply passed on unmodified to Matlab or Octave. Those constructions are not addresses in this section.. + Unlike MATLAB or Octave expressions, Dynare expressions are necessarily scalar ones: they cannot contain matrices or evaluate to matricesNote that arbitrary MATLAB or Octave expressions can be put in a .mod file, but those expressions have to be on separate lines, generally at the end of the file for post-processing purposes. They are not interpreted by Dynare, and are simply passed on unmodified to MATLAB or Octave. Those constructions are not addresses in this section.. Expressions can be constructed using integers (INTEGER), floating point numbers (DOUBLE), parameter names (PARAMETER_NAME), variable names (VARIABLE_NAME), operators and functions. @@ -583,7 +630,7 @@ parameters alpha, bet; When specifying the leads and lags of endogenous variables, it is important to respect the following convention: in Dynare, the timing of a variable reflects when that variable is decided. A control variable - which by definition is decided in the current period - must have no lead. A predetermined variable - which by definition has been decided in a previous period - must have a lag. A consequence of this is that all stock variables must use the "stock at the end of the period" convention. Please refer to for more details and concrete examples. - Leads and lags are primarily used for endogenous variables. They can be used for exogenous variables under some conditions (TO BE EXPLICITED). They are forbidden for parameters and for local model variables (see ). + Leads and lags are primarily used for endogenous variables, but can be used for exogenous variables. They have no effect on parameters and are forbidden for local model variables (see ). @@ -617,7 +664,7 @@ parameters alpha, bet; In a MODEL_EXPRESSION, no other function is allowed.This is due to the fact that the Dynare preprocessor performs a symbolical derivation of all model equations, and therefore needs to know the analytical derivatives of all the equations in the model equations. In the future, we should add support for other usual functions, and implement an interface to let the user define custom functions, for which he would provide the analytical derivatives. - In an EXPRESSION, it is possible to use any arbitrary Matlab or Octave function, provided that this function has scalar arguments and return value. + In an EXPRESSION, it is possible to use any arbitrary MATLAB or Octave function, provided that this function has scalar arguments and return value. @@ -707,7 +754,7 @@ Inside the model block, Dynare allows the creation of model-local vari - Instructs the preprocessor to create dynamic loadable libraries (DLL) containing the model equations and derivatives, instead of writing those in M-files. You need to having a working compilation environment (i.e. the mex command of Matlab or Octave must be operational). Using this option can result in faster simulations or estimations, at the expense of some initial compilation time.In particular, for big models, the compilation step can be very time-consuming, and use of this option may be counter-productive in those cases. + Instructs the preprocessor to create dynamic loadable libraries (DLL) containing the model equations and derivatives, instead of writing those in M-files. You need to having a working compilation environment (i.e. the mex command of MATLAB or Octave must be operational). Using this option can result in faster simulations or estimations, at the expense of some initial compilation time.In particular, for big models, the compilation step can be very time-consuming, and use of this option may be counter-productive in those cases. @@ -1346,7 +1393,7 @@ Dynare has special commands for the computation of the static equilibrium of the = INTEGER Determines the non-linear solver to use. Possible values for the option are: - 0: uses Matlab Optimization Toolbox FSOLVE + 0: uses MATLAB Optimization Toolbox FSOLVE 1: uses Dynare's own nonlinear equation solver 2: splits the model into recursive blocks and solves each block in turn 3: Chris Sims' solver @@ -1378,7 +1425,7 @@ Computes the equilibrium value of the endogenous variables for the value of the For complicated models, finding good numerical initial values for the endogenous variables is the trickiest part of finding the equilibrium of that model. Often, it is better to start with a smaller model and add new variables one by one. -If you know how to compute the steady state for your model, you can provide a Matlab function doing the computation instead of using steady. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. +If you know how to compute the steady state for your model, you can provide a MATLAB function doing the computation instead of using steady. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. @@ -1680,7 +1727,7 @@ The simulated endogenous variables are available in global matrix oo_.e stoch_simul computes a Taylor approximation of the decision and transition functions for the model, impulse response functions and various descriptive statistics (moments, variance decomposition, correlation and autocorrelation coefficients). For correlated shocks, the variance decomposition is computed as in the VAR literature through a Cholesky decomposition of the covariance matrix of the exogenous variables. When the shocks are correlated, the variance decomposition depends upon the order of the variables in the command. -The Taylor approximation is computed around the steady state. If you know how to compute the steady state for your model, you can provide a Matlab function doing the computation instead of using the nonlinear solver. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. +The Taylor approximation is computed around the steady state. If you know how to compute the steady state for your model, you can provide a MATLAB function doing the computation instead of using the nonlinear solver. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. The IRFs are computed as the difference between the trajectory of a variable following a shock at the beginning of period 1 and its steady state value. @@ -1753,14 +1800,14 @@ The state variables of the model are purely predetermined variables and variable - Simulated variables, when they have been computed, are available in Matlab + Simulated variables, when they have been computed, are available in MATLAB vectors with the same name as the endogenous variables. They are also available in the oo_.endo_simul matrix. The series are arranged by row, in declaration order of the variable names Impulse responses, when they have been computed, are available in oo_.irfs, with the following naming convention: VARIABLE_NAME_SHOCK_NAME. -(DEPRECATED) They are currently also available in Matlab vectors in the global workspace, however they will disappear there in a future version. +(DEPRECATED) They are currently also available in MATLAB vectors in the global workspace, however they will disappear there in a future version. Example: @@ -1821,6 +1868,7 @@ Note that in order to avoid stochastic singularity, you must have at least as ma + (deprecated) @@ -2060,7 +2108,7 @@ Each line corresponds to an estimated parameter and follows this syntax: -INITIAL_VALUE, LOWER_BOUND, UPPER_BOUND, PRIOR_MEAN, PRIOR_STANDARD_ERROR, PRIOR_3RD_PARAMETER, PRIOR_4TH_PARAMETER and SCALE_PARAMETER must be positive or negative INTEGER or DOUBLE. Some of them can be empty, in which Dynare will select a default value depending on the context and the prior shape. +INITIAL_VALUE, LOWER_BOUND, UPPER_BOUND, PRIOR_MEAN, PRIOR_STANDARD_ERROR, PRIOR_3RD_PARAMETER, PRIOR_4TH_PARAMETER and SCALE_PARAMETER can be any valid EXPRESSION. Some of them can be empty, in which Dynare will select a default value depending on the context and the prior shape. At minimum, one must specify the name of the parameter and an initial guess. That will trigger unconstrained maximum likelihood estimation. @@ -2312,13 +2360,13 @@ end; Specifies the optimizer for the mode computation: 0: the mode isn't computed. mode_file must be specified - 1: uses Matlab's fmincon + 1: uses MATLAB's fmincon 2: value no longer used - 3: uses Matlab's fminunc + 3: uses MATLAB's fminunc 4: uses Chris Sim's csminwel 5: uses a routine by Marco Ratto 6: uses a simulated annealing-like algorithm - 7: uses Matlab's fminsearch (a simplex based routine) + 7: uses MATLAB's fminsearch (a simplex based routine) Default value is 4. @@ -2337,7 +2385,7 @@ end; = (fmincon options) - Can be used to set options for fmincon, the optimizing function of Matlab Optimizaiton toolbox. Use Matlab's syntax for these options. Default: ('display','iter','LargeScale','off','MaxFunEvals',100000,'TolFun',1e-8,'TolX',1e-6) + Can be used to set options for fmincon, the optimizing function of MATLAB Optimizaiton toolbox. Use MATLAB's syntax for these options. Default: ('display','iter','LargeScale','off','MaxFunEvals',100000,'TolFun',1e-8,'TolX',1e-6) @@ -2535,7 +2583,7 @@ oo_.posterior_hpdsup.measurement_errors_corr.gdp_conso Note on steady state computation -If you know how to compute the steady state for your model, you can provide a Matlab function doing the computation instead of using steady. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. +If you know how to compute the steady state for your model, you can provide a MATLAB function doing the computation instead of using steady. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. @@ -2638,6 +2686,33 @@ oo_.posterior_hpdsup.measurement_errors_corr.gdp_conso + + + model_comparison + + + + model_comparison + Bayesian model comparison + + + + + model_comparison + ( = laplacemodifiedharmonicmean) + + FILENAME(DOUBLE) + , FILENAME(DOUBLE) + + ; + + + + Description + This function computes odds ratios and estimate a posterior density over a colletion of models. The priors over models can be specified as the DOUBLE values, otherwise a uniform prior is assumed. + + + unit_root_vars @@ -2669,7 +2744,7 @@ oo_.posterior_hpdsup.measurement_errors_corr.gdp_conso When unit_root_vars is used the option of has no effect. -When there are nonstationary variables in a model, there is no unique deterministic steady state. The user must supply a Matlab function that computes the steady state values of the stationary variables in the model and returns dummy values for the nonstationary ones. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. +When there are nonstationary variables in a model, there is no unique deterministic steady state. The user must supply a MATLAB function that computes the steady state values of the stationary variables in the model and returns dummy values for the nonstationary ones. The function should be called with the name of the .mod file followed by _steadystate. See fs2000a_steadystate.m in examples/fs2000 directory. Note that the nonstationary variables in the model must be integrated processes(their first difference or k-difference must be stationary). @@ -2972,7 +3047,7 @@ Plots the simulated path of one or several variables. dynasave saves the listed variables in a binary file named FILENAME. If no VARIABLE_NAME are listed, all endogenous variables are saved. -In Matlab, variables saved with the dynasave command can be retrieved by the Matlab command load -mat FILENAME. +In MATLAB, variables saved with the dynasave command can be retrieved by the MATLAB command load -mat FILENAME. @@ -3214,12 +3289,6 @@ In Matlab, variables saved with the -Examples - -Fabrice Collard (GREMAQ, University of Toulouse) has written a guide to stochastic simulations with Dynare entitled "Dynare in Practice" which is in guide.pdf. - - -