Robox, Sokar, and Metacentrum clusters

• Use shared storages (e.g., brno14-ceitec, brno12-cerit) for storing your simulation data and submitting jobs.

• With default options, qq automatically allocates storage on the compute node(s), executes your job there, and transfers the data back. qq takes care of these copying operations.

• If you want to know more about configuring the storage qq uses for your job, read this section of the manual.

• When writing scripts to be executed, you can assume that all files in the script’s parent directory will be accessible using relative paths. You can also use absolute paths to access files on shared storages. However, you cannot easily access the local storage on your desktop.

• From your Robox desktop, you can submit jobs to all Metacentrum-family clusters (see Inter-cluster job management).

• Metacentrum-family clusters are very heterogeneous — you can use pretty much any number of CPUs and GPUs you need, as long as they fit on a single node. Running multi-node jobs can be complicated, as most clusters do not have fast interconnections between individual compute nodes.

• On Metacentrum, some nodes or node groups may be slow or unstable. You can filter them out by submitting with --props ^cl_<cluster_name> to exclude a cluster, or with --props vnode=^<node_name> to exclude a specific node.

• On Robox, you should generally not submit to the desktops queue as it only contains desktops (duh). By default, qq is not installed on other people’s desktops, so your jobs will most likely crash. Instead, use the cpu or gpu queues. If you want to submit to your own desktop, you can use the desktops queue but must explicitly select your desktop (using --props vnode=YOUR_DESKTOP_NAME).

Tip

Click here for detailed external documentation of the Metacentrum family clusters.