14.09.2014 Views

CASINO manual - Theory of Condensed Matter

CASINO manual - Theory of Condensed Matter

CASINO manual - Theory of Condensed Matter

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

for a single job in an ensemble <strong>of</strong> multiple jobs (e.g.<br />

certain Blue-Gene Qs cannot run jobs <strong>of</strong> less than 128<br />

nodes because <strong>of</strong> the hardware).<br />

TIME_FORMAT S (TYPE=cluster only) a string determining how the<br />

&WALLTIME& variable is to be constructed when specifying<br />

the requested job time in the submission script. In<br />

this variable, D, H, M, and S are evaluated to days,<br />

hours, minutes and seconds, respectively; if the letters<br />

are repeated, the respective number is padded with<br />

zeroes on the left to fill the number <strong>of</strong> digits given by<br />

the number <strong>of</strong> repetitions. E.g., for a <strong>CASINO</strong>-formatted<br />

walltime <strong>of</strong> 5h43m31s,<br />

H:MM:SS<br />

would make &WALLTIME& expand to "5:43:31", while<br />

DD:HH:M:SSSS<br />

would make &WALLTIME& expand to "00:05:43:0031", and<br />

MMMM minutes SS seconds<br />

would make &WALLTIME& expand to "0343 minutes 31<br />

seconds".<br />

MIN_WALLTIME S (TYPE=cluster only) minimum/maximum wall time that can<br />

MAX_WALLTIME be requested, in <strong>CASINO</strong> format. E.g.,<br />

1d4h51m<br />

WALLTIME_CODES S (TYPE=cluster only) blank-separated list <strong>of</strong> associations<br />

between strings and associated wall times in <strong>CASINO</strong><br />

format. The strings will be used as the &WALLTIME&<br />

variable on machines which force discrete job times and<br />

uses custom codes to identify them. E.g.,<br />

u=24h t=12h s=6h<br />

ALLOWED_WALLTIME S (TYPE=cluster only) blank-separated list <strong>of</strong> wall times<br />

that can be requested on a machine which forces discrete<br />

job times. One need not supply this if WALLTIME_CODES<br />

is specified. If both are, the intersection <strong>of</strong> both<br />

lists will take effect. If MAX_*TIME is specified,<br />

both the limits and the discrete list constrain the<br />

available runlengths.<br />

MIN_CORETIME S (TYPE=cluster only) minimum/maximum sum <strong>of</strong> time on all<br />

MAX_CORETIME requested cores, in <strong>CASINO</strong> format. If both MIN_WALLTIME<br />

and MIN_CORETIME, or MAX_WALLTIME and MAX_CORETIME, are<br />

specified, the most restrictive value takes effect. This<br />

is particularly useful if there is an accounting credit<br />

system in place on the machine, so one can provide a<br />

*MAX_CORETIME tag which returns the time remaining in<br />

the user’s account.<br />

MAX_NJOBS<br />

RELPATHNAMES<br />

SCRIPTCSH<br />

S (TYPE=cluster only) On some machines there is a maximum<br />

number <strong>of</strong> jobs that may be flagged by a single runqmc<br />

command (e.g. on Titan only 100 aprun processes are<br />

permitted per job submission script). The maximum may<br />

be specified using this tag, so that runqmc can complain<br />

about this problem.<br />

S (TYPE=cluster only) If set to ’yes’, this flags the<br />

existence <strong>of</strong> a machine with completely different<br />

filesystems on the login nodes and the compute nodes<br />

(and which therefore requires ’staging’ <strong>of</strong> the <strong>CASINO</strong><br />

input and output files). This necessitates the use <strong>of</strong><br />

relative pathnames rather than absolute pathnames and<br />

a more elaborate clean-up procedure.<br />

S (TYPE=cluster only) This should be set to ’yes’ on<br />

extremely unusual machines which insist that batch<br />

225

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!