Actions

Difference between revisions of "Specifying the cluster on which to run"

From ALICE Documentation

 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==Specifying the cluster on which to run==
 
==Specifying the cluster on which to run==
 
To use other clusters, you can swap the cluster module. This is a special module that change what modules are available for you, and what cluster your jobs will be queued in. By default you are working on victini. To switch to, e.g., skitty you need to redefine the environment so you get access to all modules installed on the skitty cluster, and to be able to submit jobs to the skitty scheduler so your jobs will start on skitty instead of the default victini cluster.  
 
To use other clusters, you can swap the cluster module. This is a special module that change what modules are available for you, and what cluster your jobs will be queued in. By default you are working on victini. To switch to, e.g., skitty you need to redefine the environment so you get access to all modules installed on the skitty cluster, and to be able to submit jobs to the skitty scheduler so your jobs will start on skitty instead of the default victini cluster.  
   $ module swap cluster/skitty
+
   $ module swap cluster/alice
  
Note: the skitty modules may not work directly on the login nodes, because the login nodes do not have the same architecture as the skitty cluster, they have the same architecture as the victini cluster however, so this is why by default software works on the login nodes. See section 8.9 for why this is and how to fix this.  
+
Note: the skitty modules may not work directly on the login nodes, because the login nodes do not have the same architecture as the skitty cluster, they have the same architecture as the victini cluster however, so this is why by default software works on the login nodes. See  
To list the available cluster modules, you can use the module avail cluster/ command:
+
 
 +
[[Running software that is incompatible with host]]  for why this is and how to fix this.  
 +
 
 +
To list the available cluster modules, you can use the module avail cluster/ command:
 
   $ module avail cluster/  
 
   $ module avail cluster/  
 
   -----------------------------------------------------------------------------------
 
   -----------------------------------------------------------------------------------
     /etc/modulefiles/vsc
+
     /etc/modulefiles/alice
 
   -----------------------------------------------------------------------------------
 
   -----------------------------------------------------------------------------------
 
   cluster/golett (S) cluster/phanpy (S) cluster/skitty (S) cluster/swalot  
 
   cluster/golett (S) cluster/phanpy (S) cluster/skitty (S) cluster/swalot  
Line 14: Line 17:
 
   S: Module is Sticky, requires --force to unload or purge  
 
   S: Module is Sticky, requires --force to unload or purge  
 
   L: Module is loaded
 
   L: Module is loaded
   If you need software that is not listed, request it via https://www.ugent.be/hpc/en/ support/software-installation-request
+
   If you need software that is not listed, request it helpdesk@alice.leidenuniv.nl
 
As indicated in the output above, each cluster module is a so-called sticky module, i.e., it will not be unloaded when module purge (see [[Purging all modules]]) is used.  
 
As indicated in the output above, each cluster module is a so-called sticky module, i.e., it will not be unloaded when module purge (see [[Purging all modules]]) is used.  
 +
 
The output of the various commands interacting with jobs (qsub, stat, ...) all depend on which cluster module is loaded.
 
The output of the various commands interacting with jobs (qsub, stat, ...) all depend on which cluster module is loaded.

Latest revision as of 11:20, 7 May 2020

Specifying the cluster on which to run

To use other clusters, you can swap the cluster module. This is a special module that change what modules are available for you, and what cluster your jobs will be queued in. By default you are working on victini. To switch to, e.g., skitty you need to redefine the environment so you get access to all modules installed on the skitty cluster, and to be able to submit jobs to the skitty scheduler so your jobs will start on skitty instead of the default victini cluster.

 $ module swap cluster/alice

Note: the skitty modules may not work directly on the login nodes, because the login nodes do not have the same architecture as the skitty cluster, they have the same architecture as the victini cluster however, so this is why by default software works on the login nodes. See

Running software that is incompatible with host for why this is and how to fix this.

To list the available cluster modules, you can use the module avail cluster/ command:

 $ module avail cluster/ 
 -----------------------------------------------------------------------------------
   /etc/modulefiles/alice 
 -----------------------------------------------------------------------------------
 cluster/golett (S) cluster/phanpy (S) cluster/skitty (S) cluster/swalot 
    (S) cluster/victini (S,L)
 Where: 
  S: Module is Sticky, requires --force to unload or purge 
  L: Module is loaded
 If you need software that is not listed, request it helpdesk@alice.leidenuniv.nl

As indicated in the output above, each cluster module is a so-called sticky module, i.e., it will not be unloaded when module purge (see Purging all modules) is used.

The output of the various commands interacting with jobs (qsub, stat, ...) all depend on which cluster module is loaded.