Page tree
Skip to end of metadata
Go to start of metadata

Constraints of SuperMUC-NG:

constraintMeaning
noworkJob will start, even when WORK is not available on that nodes
noscratchJob will start, even when SCRATCH is not available on that nodes 
fat*nn fat nodes will be used (useful for mixed jobs)
thin*nn thin nodes will be used (useful for mixed jobs)
Use only for special cases:
i0xIsland: Will run only on nodes of thin Island x
f0xIsland: Will run only on nodes of fat Island x
coldrun on cold islands
hotrun on hot islands (connected to adsorbtion coolers)

Examples:

Single Name: Only nodes which have the specified feature will be used. For example, "--constraint="nowork"

AND: The amersand is used for an AND operator: --constraint="nowork&noscratch"

OR: The vertical bar is used for an OR operator: --constraint="nowork|noscratch"

Matching OR: If only one of a set of possible options should be used for all allocated nodes, then use the OR operator and enclose the options within square brackets. For example: --constraint=[i03Ii04|i04] might be used to specify that all nodes must be allocated on a single island, but any of those three can be used.

Node Counts/Multiple Counts: request can specify the number of nodes needed with some feature by appending an asterisk and count after the feature name:  "--nodes=16 --constraint=[fat*4&thin*12] indicates that the job requires 4 fat and 12 thin nodes.

Parenthesis: can be used to group like node features together. For example --constraint=[i02&(noscratch|nowork)]


  • No labels