Changes between Version 13 and Version 14 of MTO

Timestamp:

04/05/13 11:13:37 (12 years ago)

Author:

jorisborgdorff

Comment:

--

MTO

@@ -13 +13 @@
 = Configuration files =
 
-If the MTO is not yet set up for the sites that are needed, first the configuration files have to be set and then the MTO can be executed.
+Before running MTO, its configuration files must be set to connect all clusters that will be used in a simulation.
 
 MTO's configuration is stored in two files:
@@ -47 +47 @@
 }}}
 
-For MUSCLE 2 commands, the second file is of importance: it implies that it can only use a limited port range on a given cluster, and how it should contact the MTO. To make this information available to MUSCLE 2, create the file `MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing
+The global topology file states what clusters will be connected by the MTO, and on which port the MTO will communicate with other MTO's. It should be the same for all the MTO's participating. The local configuration states how the MTO can be contacted by MUSCLE within the cluster. It also implies that MUSCLE can only use a limited port range on a given cluster. Each cluster should use a different port range. To make this information available to MUSCLE 2, create the file `MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing
 {{{
+# Make the MTO available to MUSCLE.
 export MUSCLE_MTO=private-address:5001
 export MUSCLE_PORT_MIN=5002
@@ -54 +55 @@
 }}}
 
-When MUSCLE_HOME/etc/muscle.profile is sourced, these variables are then also set.
+Whenever MUSCLE_HOME/etc/muscle.profile is sourced, these variables are set.
 = starting MTO =
  * debug mode