Changes between Version 12 and Version 13 of QCG-AdvancedClient

Timestamp:

11/18/12 21:11:48 (12 years ago)

Author:

mmamonski

Comment:

--

QCG-AdvancedClient

@@ -42 +42 @@
 }
 }}}
-You can set there two environment variables interpreted by the MUSCLE framework:
-   * MUSCLE_CLASSPATH
-   * MUSCLE_LIBPATH
-to set Java classpath and the path of dynamically loadable libraries. Thanks to this mechanism you can use single abstract CxA that do not contain any site-specific paths. Also you can load the module in the interactive QCG job:
+You can set there two environment variables interpreted by the MUSCLE framework, namely: `MUSCLE_CLASSPATH` and `MUSCLE_LIBPATH`
+which set the Java classpath and the path of dynamically loadable libraries respectively. Thanks to this mechanism you can use single abstract CxA that do not consist of any site-specific paths. Also you can load the module in the interactive QCG job, e.g:
 {{{
 bash-4.1$ module load Fusion/Turbulence
@@ -129 +127 @@
 }}}
  * In the above example we:
-   * run the simulation on the two clusters using advance reservations created  automatically by the QCG-Broker (in the co-allocation process) on two clusters: inula and zeus (`<candidateHosts>`
-   * we requested 30 minutes of maximum job walltime (`<executionDuration>`)
-   * we added 
+   * run the simulation on the two clusters using advance reservations created  automatically by the QCG-Broker (in the co-allocation process) on two clusters: inula and zeus (`<candidateHosts>`),
+   * we requested 30 minutes of maximum job walltime (`<executionDuration>`),
+   * we specify the kernels to be run in the `processesId` attribute of the `<processes>` element (multiple kernels must be separated with a colon ":"),
+   * we specify the number of processes to be allocated