capitalize Cepremap and Matlab, uncapitalize DYNARE

parent 982d6b9d
......@@ -190,7 +190,7 @@ fixed in version 4.5.4:
- Estimation with missing values was crashing if the `prefilter` option was used.
- Added a workaround for a difference in behaviour between Octave and Matlab regarding the creation
- Added a workaround for a difference in behaviour between Octave and MATLAB regarding the creation
of function handles for functions that do not exist in the path. With Octave 4.2.1, steady state
files did not work if no auxiliary variables were created.
......@@ -315,7 +315,7 @@ fixed in version 4.5.2:
- Fixed crash with optimizer 5 when not used with DSGE model at order 1.
- Fixed mex file used for third order approximation (was crashing on
Matlab/Windows 7).
MATLAB/Windows 7).
......@@ -658,7 +658,7 @@ Here is the list of major user-visible changes:
- Command line
+ New option `onlyclearglobals` (do not clear JIT compiled functions
with recent versions of Matlab),
with recent versions of MATLAB),
+ New option `minimal_workspace` to use fewer variables in the
current workspace,
......@@ -689,7 +689,7 @@ Here is the list of major user-visible changes:
+ `mode_compute=101` Uses SOLVEOPT as described by Kuntsevich and
Kappel (1997),
+ `mode_compute=102` Uses `simulannealbnd` from Matlab's Global
+ `mode_compute=102` Uses `simulannealbnd` from MATLAB's Global
Optimization Toolbox (if available),
+ New option `silent_optimizer` to shut off output from mode
......@@ -724,7 +724,7 @@ Here is the list of major user-visible changes:
+ Introduces new path management to avoid conflicts with other
toolboxes,
+ Full compatibility with Matlab 2014b's new graphic interface,
+ Full compatibility with MATLAB 2014b's new graphic interface,
+ When using `model(linear)`, Dynare automatically checks
whether the model is truly linear,
......@@ -924,7 +924,7 @@ Here is the list of major user-visible changes:
was not consistent with the reference manual,
+ When the initialization of an MCMC run failed, the metropolis.log file was
locked, requiring a restart of Matlab to restart estimation,
locked, requiring a restart of MATLAB to restart estimation,
+ If the posterior mode was right at the corner of the prior bounds, the
initialization of the MCMC erroneously crashed,
......@@ -1140,7 +1140,7 @@ Here is the list of major user-visible changes:
- A bug when external functions were used in model local variables
that were contained in equations that required auxiliary
variable/equations led to crashes of Matlab.
variable/equations led to crashes of MATLAB.
- Sampling from the prior distribution for an inverse gamma II
distribution when `prior_trunc>0` could result in incorrect
......
......@@ -79,7 +79,7 @@ p.footer {
</ul>
</div>
<h2>AIM Solver Subsystem<a name="1"></a></h2>
<p>The AIM subsystem in the AIM subdirectory of the main Dynare matlab directory contains Matlab functions necessary for using
<p>The AIM subsystem in the AIM subdirectory of the main Dynare matlab directory contains MATLAB functions necessary for using
Gary Anderson's AIM 1st order solver as an alternative to Dynare's default mjdgges solver (see <a href="http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html">http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html</a> ).
</p>
<p>It cosists of:</p>
......@@ -92,7 +92,7 @@ p.footer {
</div>
<div>
<ul>
<li>A subset of Matlab routines from Gary Anderson's own AIM package needed to compute and solve system passed on and returned
<li>A subset of MATLAB routines from Gary Anderson's own AIM package needed to compute and solve system passed on and returned
by dynAIMsolver1 whose names start with SP.. of which <b>SPAmalg.m</b> is the main driver:
</li>
</ul>
......@@ -215,7 +215,7 @@ p.footer {
can produce ~ one order closer results to the Dynare solutiion
then when if plain jacobia_ is passed,
i.e. diff &lt; e-14 for aa and diff &lt; *e-13 for jacobia_ if Q' is used.</pre><p>GP July 2008</p>
<p>part of DYNARE, copyright Dynare Team (1996-2008) Gnu Public License.</p>
<p>part of Dynare, copyright Dynare Team (1996-2008) Gnu Public License.</p>
<p class="footer"><br>
Published with MATLAB&reg; 7.1<br></p>
</div>
......@@ -225,7 +225,7 @@ p.footer {
%% AIM Solver Subsystem
% The AIM subsystem in the AIM subdirectory of the main Dynare matlab
% directory contains Matlab functions necessary for using
% directory contains MATLAB functions necessary for using
% Gary Anderson's AIM 1st order solver as an alternative to Dynare's default mjdgges solver (see http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html ).
%
% It cosists of:
......@@ -236,7 +236,7 @@ p.footer {
% gu=dr.hgu from the AIM outputs. ("1" in the title is for 1st order
% solver).
%
% * A subset of Matlab routines from Gary Anderson's own AIM package needed to compute
% * A subset of MATLAB routines from Gary Anderson's own AIM package needed to compute
% and solve system passed on and returned by dynAIMsolver1 whose names start with SP..
% of which *SPAmalg.m* is the main driver:
%
......@@ -394,10 +394,10 @@ p.footer {
%
% GP July 2008
%
% part of DYNARE, copyright Dynare Team (1996-2008)
% part of Dynare, copyright Dynare Team (1996-2008)
% Gnu Public License.
##### SOURCE END #####
-->
</body>
</html>
\ No newline at end of file
</html>
......@@ -111,7 +111,7 @@ demia/Economics/Dynare%20DSGE/V4/doc/AIM/Dynare%20AIM%20use%20Doc.html#11=
<H2>AIM Solver Subsystem<A name=3D1></A></H2>
<P>The AIM subsystem in the AIM subdirectory of the main Dynare matlab =
directory=20
contains Matlab functions necessary for using Gary Anderson's AIM 1st =
contains MATLAB functions necessary for using Gary Anderson's AIM 1st =
order=20
solver as an alternative to Dynare's default mjdgges solver (see <A=20
href=3D"http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html">http:/=
......@@ -129,7 +129,7 @@ AIM outputs.=20
("1" in the title is for 1st order solver). </LI></UL></DIV>
<DIV>
<UL>
<LI>A subset of Matlab routines from Gary Anderson's own AIM package =
<LI>A subset of MATLAB routines from Gary Anderson's own AIM package =
needed to=20
compute and solve system passed on and returned by dynAIMsolver1 whose =
names=20
......@@ -328,7 +328,7 @@ forward looking models, passing into dynAIMsolver aa =3D{Q'|1}*jacobia_
i.e. diff &lt; e-14 for aa and diff &lt; *e-13 for jacobia_ if Q' =
is used.</PRE>
<P>GP July 2008</P>
<P>part of DYNARE, copyright Dynare Team (1996-2008) Gnu Public =
<P>part of Dynare, copyright Dynare Team (1996-2008) Gnu Public =
License.</P>
<P class=3Dfooter><BR>Published with MATLAB=C2=AE 7.1<BR></P></DIV><!--=0A=
##### SOURCE BEGIN #####=0A=
......@@ -336,7 +336,7 @@ License.</P>
%% AIM Solver Subsystem
% The AIM subsystem in the AIM subdirectory of the main Dynare matlab
% directory contains Matlab functions necessary for using
% directory contains MATLAB functions necessary for using
% Gary Anderson's AIM 1st order solver as an alternative to Dynare's =
default mjdgges solver (see =
http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html ).=20
......@@ -351,7 +351,7 @@ subsystem.=20
% gu=3Ddr.hgu from the AIM outputs. ("1" in the title is for 1st order
% solver).
%
% * A subset of Matlab routines from Gary Anderson's own AIM package =
% * A subset of MATLAB routines from Gary Anderson's own AIM package =
needed to compute
% and solve system passed on and returned by dynAIMsolver1 whose names =
start with SP..=20
......@@ -544,7 +544,7 @@ used. =20
%
% GP July 2008 =20
%
% part of DYNARE, copyright Dynare Team (1996-2008)
% part of Dynare, copyright Dynare Team (1996-2008)
% Gnu Public License.
=0A=
##### SOURCE END #####=0A=
......
......@@ -30,7 +30,7 @@
\subsection*{AIM Solver Subsystem}
\begin{par}
The AIM subsystem in the AIM subdirectory of the main Dynare matlab directory contains Matlab functions necessary for using Gary Anderson's AIM 1st order solver as an alternative to Dynare's default mjdgges solver (see \begin{verbatim}http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html\end{verbatim} ).
The AIM subsystem in the AIM subdirectory of the main Dynare matlab directory contains MATLAB functions necessary for using Gary Anderson's AIM 1st order solver as an alternative to Dynare's default mjdgges solver (see \begin{verbatim}http://www.federalreserve.gov/Pubs/oss/oss4/aimindex.html\end{verbatim} ).
\end{par} \vspace{1em}
\begin{par}
It cosists of:
......@@ -41,7 +41,7 @@ It cosists of:
\end{itemize}
\begin{itemize}
\setlength{\itemsep}{-1ex}
\item A subset of Matlab routines from Gary Anderson's own AIM package needed to compute and solve system passed on and returned by dynAIMsolver1 whose names start with SP.. of which \textbf{SPAmalg.m} is the main driver:
\item A subset of MATLAB routines from Gary Anderson's own AIM package needed to compute and solve system passed on and returned by dynAIMsolver1 whose names start with SP.. of which \textbf{SPAmalg.m} is the main driver:
\end{itemize}
\begin{itemize}
\setlength{\itemsep}{-1ex}
......@@ -235,7 +235,7 @@ Dynare use:
GP July 2008
\end{par} \vspace{1em}
\begin{par}
part of DYNARE, copyright Dynare Team (1996-2008) Gnu Public License.
part of Dynare, copyright Dynare Team (1996-2008) Gnu Public License.
\end{par} \vspace{1em}
......
......@@ -68,9 +68,9 @@
\myitem Compatible with all setups that are supported by Dynare
\begin{itemize}
\myitem Windows, Mac OS X, Linux
\myitem Matlab 7.5 (R2007b) or later, Octave
\myitem MATLAB 7.5 (R2007b) or later, Octave
\end{itemize}
\myitem Must run \texttt{dynare} or \texttt{dynare\_config} at least once in the current Matlab/Octave session before use
\myitem Must run \texttt{dynare} or \texttt{dynare\_config} at least once in the current MATLAB/Octave session before use
\myitem More complete information is included in the Dynare manual
\end{itemize}
\end{frame}
......@@ -80,7 +80,7 @@
\begin{frame}[fragile,t]
\frametitle{A Programming Note (1/3)}
\begin{itemize}
\myitem Time series and dates (and reporting) are implemented as Matlab/Octave classes
\myitem Time series and dates (and reporting) are implemented as MATLAB/Octave classes
\myitem Inplace modification of instantiated objects not supported. Let me explain \dots
\begin{itemize}
\myitem A class is a template for defining objects, defining their member
......@@ -115,7 +115,7 @@ X =
\frametitle{A Programming Note (2/3)}
\begin{itemize}
\item[] \begin{itemize}
\myitem But! For Matlab/Octave's implementation of classes this is not the
\myitem But! For MATLAB/Octave's implementation of classes this is not the
case as it does not support inplace modification
\begin{verbatim}
>> X.multiplyByTwo()
......@@ -183,7 +183,7 @@ X =
\begin{frame}[fragile,t]
\frametitle{Creating a new \texttt{dates} object in Matlab/Octave}
\frametitle{Creating a new \texttt{dates} object in MATLAB/Octave}
\begin{itemize}
\myitem{A single date}
\begin{alltt}
......@@ -429,7 +429,7 @@ would be transformed into
\begin{frame}[fragile,t]
\frametitle{Creating a new \texttt{dseries} object (2/2)}
Load series from CSV/spreadsheet (\texttt{.csv, .xls}) or Matlab file (\texttt{.m, .mat})
Load series from CSV/spreadsheet (\texttt{.csv, .xls}) or MATLAB file (\texttt{.m, .mat})
\begin{itemize}
\myitem Syntax:
\begin{alltt}
......@@ -646,7 +646,7 @@ the time range of \verb+vs+ will be the union of \verb+ts.dates+ and
\begin{itemize}
\myitem You can easily modify the Ti$k$Z graph if the option you want is not in Dynare
\end{itemize}
\myitem Works with Matlab \& Octave
\myitem Works with MATLAB \& Octave
\myitem Works much faster than similar softawre
\myitem NB: Must install a \LaTeX\ distribution to compile reports
\begin{itemize}
......
......@@ -203,18 +203,18 @@ institutions who cannot afford, or do not want to pay for, MATLAB and
are willing to bear the concomitant performance loss.
The development of Dynare is mainly done at
@uref{http://www.cepremap.ens.fr, Cepremap} by a core team of
@uref{http://www.cepremap.ens.fr, CEPREMAP} by a core team of
researchers who devote part of their time to software
development. Currently the development team of Dynare is composed of
Stéphane Adjemian (Université du Maine, Gains and Cepremap), Houtan
Bastani (Cepremap), Michel Juillard (Banque de France), Frédéric
Karamé (Université d'Évry, Epee and Cepremap), Junior Maih (Norges
Bank), Ferhat Mihoubi (Université d'Évry, Epee and Cepremap), George
Perendia, Marco Ratto (JRC) and Sébastien Villemot (Cepremap and Paris
School of Economics). Financial support is provided by Cepremap,
Stéphane Adjemian (Université du Maine, Gains and CEPREMAP), Houtan
Bastani (CEPREMAP), Michel Juillard (Banque de France), Frédéric
Karamé (Université d'Évry, Epee and CEPREMAP), Junior Maih (Norges
Bank), Ferhat Mihoubi (Université d'Évry, Epee and CEPREMAP), George
Perendia, Marco Ratto (JRC) and Sébastien Villemot (CEPREMAP and Paris
School of Economics). Financial support is provided by CEPREMAP,
Banque de France and DSGE-net (an international research network for
DSGE modeling). Increasingly, the developer base is expanding, as
tools developed by researchers outside of Cepremap are integrated into
tools developed by researchers outside of CEPREMAP are integrated into
Dynare.
Interaction between developers and users of Dynare is central to the
......
......@@ -55,9 +55,9 @@ Dynare misc commands
.. matcomm:: internals FLAG ROUTINENAME[.m]|MODFILENAME
|br| Depending on the value of ``FLAG``, the ``internals`` command
can be used to run unitary tests specific to a Matlab/Octave
can be used to run unitary tests specific to a MATLAB/Octave
routine (if available), to display documentation about a
Matlab/Octave routine, or to extract some informations about the
MATLAB/Octave routine, or to extract some informations about the
state of Dynare.
*Flags*
......@@ -93,7 +93,7 @@ Dynare misc commands
>> internals --doc ../matlab/fr/ROUTINENAME
At this time, will work properly for only a small number
of routines. At the top of the (available) Matlab/Octave
of routines. At the top of the (available) MATLAB/Octave
routines a commented block for the internal documentation
is written in the GNU texinfo documentation format. This
block is processed by calling texinfo from
......@@ -114,7 +114,7 @@ Dynare misc commands
``--load-mh-history``
|br| Loads into the Matlab/Octaves workspace informations
|br| Loads into the MATLAB/Octaves workspace informations
about the previously saved MCMC draws generated by a ``.mod``
file named MODFILENAME.
......
......@@ -67,7 +67,7 @@ be under ``/usr/share/doc/dynare-doc``.
On macOS
--------
To install Dynare for use with Matlab, execute the automated installer
To install Dynare for use with MATLAB, execute the automated installer
called ``dynare-4.x.y.pkg`` (where *4.x.y* is the version number), and
follow the instructions. The default installation directory is
``/Applications/Dynare/4.x.y`` (please refer to the `Dynare wiki`_ for
......
......@@ -63,15 +63,15 @@ to bear the concomitant performance loss.
The development of Dynare is mainly done at `CEPREMAP`_ by a core team
of researchers who devote part of their time to software
development. Currently the development team of Dynare is composed of
Stéphane Adjemian (Université du Maine, Gains and Cepremap), Houtan
Bastani (Cepremap), Michel Juillard (Banque de France), Frédéric
Karamé (Université du Maine, Gains and Cepremap), Junior Maih (Norges
Stéphane Adjemian (Université du Maine, Gains and CEPREMAP), Houtan
Bastani (CEPREMAP), Michel Juillard (Banque de France), Frédéric
Karamé (Université du Maine, Gains and CEPREMAP), Junior Maih (Norges
Bank), Ferhat Mihoubi (Université Paris-Est Créteil, Érudite and
Cepremap), Johannes Pfeifer (University of Cologne), Marco Ratto
CEPREMAP), Johannes Pfeifer (University of Cologne), Marco Ratto
(European Commission, Joint Research Centre - JRC) and Sébastien
Villemot (Cepremap). Increasingly, the developer base is expanding, as
tools developed by researchers outside of Cepremap are integrated into
Dynare. Financial support is provided by Cepremap, Banque de France
Villemot (CEPREMAP). Increasingly, the developer base is expanding, as
tools developed by researchers outside of CEPREMAP are integrated into
Dynare. Financial support is provided by CEPREMAP, Banque de France
and DSGE-net (an international research network for DSGE modeling).
Interaction between developers and users of Dynare is central to the
......
......@@ -40,7 +40,7 @@ added to this ``Page`` until another ``Page`` is added to the report
at the end of the section.
Options to methods are passed differently than those to Dynare
commands. They take the form of named options to Matlab functions
commands. They take the form of named options to MATLAB functions
where the arguments come in pairs
(e.g. ``function_name(`option_1_name', `option_1_value',
`option_2_name', `option_2_value', ...)``, where ``option_X_name`` is
......@@ -821,7 +821,7 @@ and a clarifying example.
.. option:: showReport, BOOLEAN
Open the compiled report (works on Windows and macOS on
Matlab). Default: ``true``.
MATLAB). Default: ``true``.
*Example*
......
......@@ -111,7 +111,7 @@ by the ``dynare`` command.
By default, ``dynare`` will issue a ``clear all`` command to
MATLAB (<R2015b) or Octave, thereby deleting all workspace
variables and functions; this option instructs ``dynare`` not
to clear the workspace. Note that starting with Matlab 2015b
to clear the workspace. Note that starting with MATLAB 2015b
``dynare`` only deletes the global variables and the functions
using persistent variables, in order to benefit from the JIT
(Just In Time) compilation. In this case the option instructs
......@@ -265,13 +265,13 @@ by the ``dynare`` command.
.. option:: nopathchange
By default Dynare will change Matlab/Octaves path if
By default Dynare will change MATLAB/Octaves path if
``dynare/matlab`` directory is not on top and if Dynares
routines are overriden by routines provided in other
toolboxes. If one wishes to override Dynares routines, the
``nopathchange`` options can be used. Alternatively, the path
can be temporarly modified by the user at the top of the
``.mod`` file (using Matlab/Octaves ``addpath`` command).
``.mod`` file (using MATLAB/Octaves ``addpath`` command).
.. option:: nopreprocessoroutput
......@@ -287,7 +287,7 @@ by the ``dynare`` command.
.. option:: matlabroot=<<path>>
The path to the Matlab installation for use with
The path to the MATLAB installation for use with
:opt:`use_dll`. Dynare is able to set this automatically,
so you should not need to set it yourself.
......@@ -505,7 +505,7 @@ parser would continue processing.
It is also helpful to keep in mind that any piece of code that does not violate
Dynare syntax, but at the same time is not recognized by the parser, is interpreted
as native Matlab code. This code will be directly passed to the ``driver`` script.
as native MATLAB code. This code will be directly passed to the ``driver`` script.
Investigating ``driver.m`` file then helps with debugging. Such problems most often
occur when defined variable or parameter names have been misspelled so that Dynare's
parser is unable to recognize them.
......@@ -337,12 +337,12 @@ set up Dynare for parallel execution.
Key+Pause to open the System Configuration, then go to Advanced
-> Environment Variables -> Path).
5. Restart your computer to make the path change effective.
6. Open Matlab and type into the command window::
6. Open MATLAB and type into the command window::
!psexec
This executes the ``psexec.exe`` from PSTools on your system
and shows whether Dynare will be able to locate it. If Matlab
and shows whether Dynare will be able to locate it. If MATLAB
complains at this stage, you did not correctly set your Windows
system path for the ``PSTools`` folder.
7. If ``psexec.exe`` was located in the previous step, a popup
......@@ -380,7 +380,7 @@ set up Dynare for parallel execution.
ComputerName=localhost
#cores to be included from this node
CPUnbr=[1:2]
#path to matlab.exe; on Windows, theMatlab bin folder is in the system path
#path to matlab.exe; on Windows, the MATLAB bin folder is in the system path
#so we only need to provide the name of the exe file
MatlabOctavePath=matlab
#Dynare path you are using
......
......@@ -21,7 +21,7 @@ are terminated by ``end;``.
If Dynare encounters an unknown expression at the beginning of a line
or after a semicolon, it will parse the rest of that line as native
Matlab code, even if there are more statements separated by semicolons
MATLAB code, even if there are more statements separated by semicolons
present. To prevent cryptic error messages, it is strongly recommended
to always only put one statement/command into each line and start a
new line after each semicolon. [#feol]_
......@@ -83,7 +83,7 @@ functions that may be called by Dynare or user-defined steady state
files, it is recommended to avoid using the name of MATLAB
functions. In particular when working with steady state files, do not
use correctly-spelled greek names like `alpha`, because there are
Matlab functions of the same name. Rather go for ``alppha`` or
MATLAB functions of the same name. Rather go for ``alppha`` or
``alph``. Lastly, please do not name a variable or parameter
``i``. This may interfere with the imaginary number i and the index in
many loops. Rather, name investment ``invest``. Using ``inv`` is also
......@@ -2168,7 +2168,7 @@ Finding the steady state with Dynare nonlinear solver
to download the solvers most current version yourself
from `http://pages.cs.wisc.edu/~ferris/path.html
<http://pages.cs.wisc.edu/~ferris/path.html>`__ and
place it in Matlabs search path.
place it in MATLABs search path.
|br| Default value is ``4``.
......@@ -4984,7 +4984,7 @@ block decomposition of the model (see :opt:`block`).
Triggers three types of Hessian
computations. ``0``: outer product gradient; ``1``:
default DYNARE Hessian routine; ``2``: ’mixed’
default Dynare Hessian routine; ``2``: ’mixed’
outer product gradient, where diagonal elements are
obtained using second order derivation formula and
outer product is used for correlation
......@@ -4992,7 +4992,7 @@ block decomposition of the model (see :opt:`block`).
univariate filters, to ensure using maximum number
of individual densities and a positive definite
Hessian. Both {0} and {2} are quicker than default
DYNARE numeric Hessian, but provide decent starting
Dynare numeric Hessian, but provide decent starting
values for Metropolis for large models (option {2}
being more accurate than {0}). Default: ``1``.
......@@ -6915,7 +6915,7 @@ Shock Decomposition
.. option:: colormap = STRING
Controls the ``colormap`` used for the shocks decomposition
graphs. See colormap in Matlab/Octave manual for valid
graphs. See colormap in MATLAB/Octave manual for valid
arguments.
.. option:: nograph
......@@ -7794,7 +7794,7 @@ variables. This shocks are described using the function
for a perfectly anticipated shock. The fourth argument indicates
the period of the shock using a dates class (see :ref:`dates class
members <dates-members>`). The last argument is the shock path
indicated as a Matlab vector of double. This function return the
indicated as a MATLAB vector of double. This function return the
handle of the updated forecast scenario.
The forecast scenario can also contain a constrained path on an
......@@ -7817,7 +7817,7 @@ is described with the function ``flip_plan``:
argument indicates the period where the path of the endogenous
variable is constrained using a dates class (see :ref:`dates class
members <dates-members>`). The last argument contains the
constrained path as a Matlab vector of double. This function
constrained path as a MATLAB vector of double. This function
return the handle of the updated forecast scenario.
Once the forecast scenario if fully described, the forecast is
......@@ -9037,7 +9037,7 @@ Types of analysis and output files
The sensitivity analysis toolbox includes several types of
analyses. Sensitivity analysis results are saved locally in
``<mod_file>/gsa``, where ``<mod_file>.mod`` is the name of the DYNARE
``<mod_file>/gsa``, where ``<mod_file>.mod`` is the name of the Dynare
model file.
Sampling
......
This diff is collapsed.
......@@ -969,7 +969,7 @@ On the other hand, under the parallel implementation, a parallel monitoring plot
\section{Parallel DYNARE: testing}
We checked the new parallel platform for DYNARE performing a number of tests, using different models and computer architectures. We present here all tests performed with Windows Xp/Matlab. However, similar tests were performed successfully under Linux/Ubuntu environment.
We checked the new parallel platform for DYNARE performing a number of tests, using different models and computer architectures. We present here all tests performed with Windows XP/MATLAB. However, similar tests were performed successfully under Linux/Ubuntu environment.
In the Bayesian estimation of DSGE models with DYNARE, most of the computing time is devoted to the posterior parameter estimation with the Metropolis algorithm. The first and second tests are therefore focused on the parallelization of the Random Walking Metropolis Hastings algorithm (Sections \ref{s:test1}-\ref{s:test2}). In addition, further tests (Sections \ref{s:test3}-\ref{s:test4}) are devoted to test all the parallelized functions in DYNARE. Finally, we compare the two parallel implementations of the Metropolis Hastings algorithms, available in DYNARE: the Independent and the Random Walk (Section \ref{s:test5}).
\subsection{Test 1.}\label{s:test1}
......
......@@ -128,7 +128,7 @@ which IRFs are calculated
<TR><TD><TD><TD> <TD>Added --order command line switch
<TR><TD><TD><TD> <TD>Added writing two Matlab files for steady state
<TR><TD><TD><TD> <TD>Added writing two MATLAB files for steady state
calcs
<TR><TD><TD><TD> <TD>Implemented optimal policy using keyword
......@@ -216,8 +216,8 @@ file.
resulting in an exception. The error occurred if a variable appeared
at time t-1 or t+1 and not at t.
<TR><TD><TD><TD> <TD>Added Matlab interface, which allows simulation
of a decision rule in Matlab.
<TR><TD><TD><TD> <TD>Added MATLAB interface, which allows simulation
of a decision rule in MATLAB.
<TR><TD><TD><TD> <TD>Got rid of Matrix Template Library.
......
......@@ -60,12 +60,12 @@ considerable memory improvement.</TD>
<TR>
<TD></TD>
<TD></TD>
<TD>MEX interface now links with LAPACK library from Matlab.</TD>
<TD>MEX interface now links with LAPACK library from MATLAB.</TD>
</TR>
<TR>
<TD></TD>
<TD></TD>
<TD>Added a hack to MEX library loading in order to avoid Matlab crash in Wins.</TD>
<TD>Added a hack to MEX library loading in order to avoid MATLAB crash in Wins.</TD>
</TR>
<TR>
<TD>rel-2</TD>
......
......@@ -155,13 +155,13 @@ dynare++ example1.mod
}
When the program is finished, it produces two output files: a journal
file {\tt example1.jnl} and a Matlab MAT-4 {\tt example1.mat}. The
file {\tt example1.jnl} and a MATLAB MAT-4 {\tt example1.mat}. The
journal file contains information about time, memory and processor
resources needed for all steps of solution. The output file is more
interesting. It contains various simulation results. It can be loaded
into Matlab or Scilab and examined.%
\footnote{For Matlab {\tt load example1.mat}, for Scilab {\tt
mtlb\_load example1.mat}} The following examples are done in Matlab,
into MATLAB or Scilab and examined.%
\footnote{For MATLAB {\tt load example1.mat}, for Scilab {\tt
mtlb\_load example1.mat}} The following examples are done in MATLAB,
everything would be very similar in Scilab.
Let us first examine the contents of the MAT file:
......@@ -189,7 +189,7 @@ dyn_i_NU dyn_nforw
All the variables coming from one MAT file have a common prefix. In
this case it is {\tt dyn}, which is Dynare++ default. The prefix can
be changed, so that the multiple results could be loaded into one Matlab
be changed, so that the multiple results could be loaded into one MATLAB
session.
In the default setup, Dynare++ solves the Taylor approximation to the
......@@ -431,7 +431,7 @@ vcov = [
}
After this model file has been run, we can load the resulting MAT-file
into the Matlab (or Scilab) and examine its contents:
into the MATLAB (or Scilab) and examine its contents:
{\small
\begin{verbatim}
>> load kp1980_2.mat
......@@ -856,9 +856,9 @@ if they are set in the {\tt initval} section. In other words, if a
multiplier has been given a value in the {\tt initval} section, then
the value is used, otherwise the calculated value is taken.
For even more difficult problems, Dynare++ generates two Matlab files
For even more difficult problems, Dynare++ generates two MATLAB files
calculating a residual of the static system and its derivative. These
can be used in Matlab's {\tt fsolve} or other algorithm to get an
can be used in MATLAB's {\tt fsolve} or other algorithm to get an
exact solution of the deterministic steady state. See
\ref{output_matlab_scripts} for more details.
......@@ -924,7 +924,7 @@ This section deals with Dynare++ input. The first subsection
\ref{dynpp_opts} provides a list of command line options, next
subsection \ref{dynpp_mod} deals with a format of Dynare++ model file,
and the last subsection discusses incompatibilities between Dynare
Matlab and Dynare++.
MATLAB and Dynare++.
\subsection{Command Line Options}
\label{dynpp_opts}
......@@ -1143,7 +1143,7 @@ $t+1$. The realization of $u_t$ is included in the information set of
$E_t$. See an explanation of Dynare++ timing on page \pageref{timing}.
\end{itemize}
The model equations are formulated in the same way as in Matlab
The model equations are formulated in the same way as in MATLAB
Dynare. The time indexes different from $t$ are put to round
parenthesis in this way: {\tt C(-1)}, {\tt C}, {\tt C(+1)}.
......@@ -1181,16 +1181,16 @@ Y-Y_SS = rho*(Y(-1)-Y_SS)+EPS;
\end{verbatim}
}
\subsection{Incompatibilities with Matlab Dynare}
\subsection{Incompatibilities with MATLAB Dynare}
This section provides a list of incompatibilities between a model file
for Dy\-na\-re++ and Matlab Dynare. These must be considered when a model
file for Matlab Dynare is being migrated to Dynare++. The list is the
for Dy\-na\-re++ and MATLAB Dynare. These must be considered when a model
file for MATLAB Dynare is being migrated to Dynare++. The list is the
following:
\begin{itemize}
\item There is no {\tt periods} keyword.
\item The parameters cannot be lagged or leaded, I think that Dynare
Matlab allows it, but the semantics is the same (parameter is a
MATLAB allows it, but the semantics is the same (parameter is a
constant).
\item There are no commands like {\tt steady}, {\tt check}, {\tt
simul}, {\tt stoch\_simul}, etc.
......@@ -1218,7 +1218,7 @@ vcov = [
There are three output files; a data file in MAT-4 format containing
the output data (\ref{matfile}), a journal text file containing an
information about the Dynare++ run (\ref{journalfile}), and a dump
file (\ref{dumpfile}). Further, Dynare++ generates two Matlab script
file (\ref{dumpfile}). Further, Dynare++ generates two MATLAB script
files, which calculate a residual and the first derivative of the
residual of the static system (\ref{output_matlab_scripts}). These are
useful when calculating the deterministic steady state outside
......@@ -1429,15 +1429,15 @@ of the planner.
The dump file serves for debugging purposes, since it contains the
mathematical problem which is being solved by dynare++.
\subsection{Matlab Scripts for Steady State Calculations}
\subsection{MATLAB Scripts for Steady State Calculations}
\label{output_matlab_scripts}
This section describes two Matlab scripts, which are useful when
This section describes two MATLAB scripts, which are useful when
calculating the deterministic steady state outside Dynare++. The
scripts are created by Dynare++ as soon as an input file is parsed,
that is before any calculations.
The first Matlab script having a name {\tt {\it modname}\_f.m} for
The first MATLAB script having a name {\tt {\it modname}\_f.m} for
given parameters values and given all endogenous variables $y$
calculates a residual of the static system. Supposing the model is in
the form of \eqref{focs}, the script calculates a vector:
......@@ -1465,14 +1465,14 @@ For example, if we want to calculate the deterministic steady state of
the {\tt kp1980.dyn} model, we need to do the following:
\begin{enumerate}
\item Run Dynare++ with {\tt kp1980.dyn}, no matter if the calculation
has not been finished, important output are the two Matlab scripts
has not been finished, important output are the two MATLAB scripts
created just in the beginning.
\item Consult file {\tt kp1980\_f.m}\ to get the ordering of parameters
and all endogenous variables.
\item Create a vector {\tt p} with the parameter values in the ordering
\item Create a vector {\tt init\_y} with the initial guess for the
Matlab solver {\tt fsolve}
\item Create a simple Matlab function called {\tt kp1980\_fsolve.m}\
MATLAB solver {\tt fsolve}
\item Create a simple MATLAB function called {\tt kp1980\_fsolve.m}\
returning the residual and Jacobian:
{\small
\begin{verbatim}
......@@ -1481,7 +1481,7 @@ function [r, J] = kp1980_fsolve(p, y)
J = kp1980_ff(p, y);
\end{verbatim}
}
\item In the Matlab prompt, run the following:
\item In the MATLAB prompt, run the following:
{\small
\begin{verbatim}
opt=optimset('Jacobian','on','Display','iter');
......@@ -1497,7 +1497,7 @@ y=fsolve(@(y) kp1980_fsolve(p,y), init_y, opt);