From ad84d63cd1ae0b4e27da8943ce81fafee532a32f Mon Sep 17 00:00:00 2001 From: Houtan Bastani Date: Wed, 3 Nov 2010 15:47:28 +0100 Subject: [PATCH] Dynare parallel: manual entry --- doc/manual.xml | 221 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 221 insertions(+) diff --git a/doc/manual.xml b/doc/manual.xml index d54672f9e..f20f3eec8 100644 --- a/doc/manual.xml +++ b/doc/manual.xml @@ -283,6 +283,10 @@ mark_as_command dynare + =CLUSTER_NAME + =FILENAME + + @@ -360,6 +364,22 @@ mark_as_command dynare Tells Dynare that your MATLAB is configured for compiling MEX files with Microsoft Visual C++ (see ). This option is only available under Windows, and is used in conjunction with . + + [=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 for more information about the configuration file. + + + + Specifies the location of the configuration file if it differs from the default. See for more information about the configuration file and its default location. + + + + Instructs Dynare to leave the connection to the slave node open after computation is complete, closing this connection only when Dynare finishes processing. + + + + Tests the parallel setup specified in the configuration file without executing the .mod file. See for more information about the configuration file. + @@ -4405,6 +4425,207 @@ plot_conditional_forecast(periods = 10) e u; +The Configuration File + The configuration file is used to provide Dynare with information not related to the model (and hence not placed in the model file). At the moment, it is only used when using Dynare to run parallel computations. + + On Linux and Mac OS X, the default location of the configuration file is $HOME/.dynare, while on Windows it is %APPDATA%/dynare.ini. + + The parsing of the configuration file is case-sensitive and it should take the following form, with each option/choice pair placed on a newline: + + + +[command0] +option0 = choice0 +option1 = choice1 + +[command1] +option0 = choice0 +option1 = choice1 + + + +The configuration file follows a few conventions (self-explanatory conventions such as USER_NAME have been excluded for concision): + + COMPUTER_NAME indicates the valid name of a server (e.g. localhost, cepremap.org) or an IP address. + DRIVE_NAME indicates a valid drive name in Windows (e.g. C). + PATH indicates a valid path in the underlying operating system (e.g. /home/user/dynare/matlab/). + PATH_AND_FILE indicates a valid path to a file in the underlying operating system (e.g. /usr/local/MATLAB/R2010b/bin/matlab). + BOOLEAN true or false. + + + +Parallel Configuration + + + + [cluster] + + + + [cluster] + spceficies a computing cluster + + + + + [cluster] + = CLUSTER_NAME + = NODE_NAME + NODE_NAME + + + + Description + When working in parallel, [cluster] is required to specify the group of computers that will be used. It is required even if you are only invoking multiple processes on one computer. + + + Options + + + = CLUSTER_NAME + The reference name of this cluster. + + + = NODE_NAME NODE_NAME ... + A list of nodes that comprise the cluster. Each node is separated by at least one space.At the current time, all nodes specified by must run the same type of operating system (i.e. all Windows or all Linux/Mac OS X). The platform versions don't matter (i.e. you can mix Windows XP and 7). + + + + + Example + + +[cluster] +Name = c1 +Members = n1 n2 n3 + + + + + + + + [node] + + + + [node] + spceficies a computing node + + + + + [node] + = NODE_NAME + + = + + INTEGER + [INTEGER:INTEGER] + + + + = COMPUTER_NAME + + = USER_NAME + + = PASSWORD + + = DRIVE_NAME + + = PATH + + = PATH + + = PATH_AND_FILE + + = BOOLEAN + + + + + Description + When working in parallel, [node] is required for every computer that will be used. The options that are required differ, depending on the underlying operating system and whether you are working locally or remotely. + + + Options + + + = NODE_NAME + The reference name of this node. + + + = INTEGER | [INTEGER:INTEGER] + If just one integer is passed, the number of processors to use. If a range of integers is passed, the specific processors to use (processor counting is defined to begin at one as opposed to zero). Note that using specific processors is only possible under Windows; under Linux and Mac OS X, if a range is passed the same number of processors will be used but the range will be adjusted to begin at one. + + + = COMPUTER_NAME + The name or IP address of the node. If you want to run locally, use localhost (case-sensitive). + + + = USER_NAME + The username used to log into a remote system. Required for remote runs on all platforms. + + + = PASSWORD + The password used to log into the remote system. Required for remote runs originating from Windows. + + + = DRIVE_NAME + The drive to be used for remote computation. Required for remote runs originating from Windows. + + + = PATH + The directory to be used for remote computation. Required for remote runs on all platforms. + + + = PATH + The path to the matlab subdirectory within the Dynare installation directory. The default is the empty string. + + + = PATH_AND_FILE + The path to the Matlab or Octave executable. The default value is matlab. + + + = BOOLEAN + Whether or not to disable Matlab's native multithreading. The default value is true. + + + + +Example + + +[node] +Name = n1 +ComputerName = localhost +CPUnbr = 1 + +[node] +Name = n2 +ComputerName = dynserv.cepremap.org +CPUnbr = 5 +UserName = usern +RemoteDirectory = /home/usern/Remote +DynarePath = /home/usern/dynare/matlab +MatlabOctavePath = matlab + +[node] +Name = n3 +ComputerName = dynserv.dynare.org +CPUnbr = [2:4] +UserName = usern +RemoteDirectory = /home/usern/Remote +DynarePath = /home/usern/dynare/matlab +MatlabOctavePath = matlab + + + + + + + + Examples Dynare comes with a database of example .mod files, which are designed to show a broad range of Dynare features, and are taken from academic papers for most of them. You should have these files in the examples subdirectory of your distribution.