Difference between revisions of "CFX/Batch"

From ScientificComputing
Jump to: navigation, search
(Submitting jobs from the GUI)
Line 31: Line 31:
  
 
===Submitting jobs from the GUI===
 
===Submitting jobs from the GUI===
It is possible to directly submit CFX jobs out of the GUI to the batch system. When you would like to use this option, then you first need to login with X11 forwarding enabled, in order to start the CFX GUI.
+
It is possible to directly submit CFX jobs out of the GUI to the batch system. When you would like to use this option, then you first need to login with [[Accessing_the_clusters#X11|X11 forwarding]] enabled, in order to start the CFX GUI.
  
 
  ssh -Y username@''hostname''
 
  ssh -Y username@''hostname''

Revision as of 12:42, 10 January 2017

You can either submit your CFX job from the command line, using the cfx_submit_job script, or you can directly submit your jobs to the batch system from the CFX graphical user interface (GUI).

Submitting jobs from the command line

CFX jobs can be submitted from the command line, using the script cfx_submit_job.

[leonhard@euler01 ~]$ ./cfx_submit_job

USAGE: cfx_submit_job [-h|--help] [-n NCPUS] [-W HH:MM] [-M MBytes] [-J job_name] ...

   -h | --help : show usage information and exit
   -n NCPUS    : number of processors for the job (default 1, maximum 96)
   -W HH:MM    : job run-time limit in hours and minutes (default 1 hour)
   -M MBytes   : memory required per processor (default 2 GB)
   -J job_name : name of the job (jobs with the same name will be chained)
   -ptile N    : use N processors per node
   -wrap X     : wrap up at given time point or percent (X = HH:MM or %)
   -lsf "opts" : pass additional bsub options to the batch system (LSF)
   ...         : all subsequent arguments are passed varbatim to cfx5solve

The number of processors (NCPUS) and run-time limit (HH:MM) are optional. The default values are 1 processor for one hour. The options -h or --help can also be used to print a brief description of the command's arguments. All other arguments are passed verbatim to cfx5solve. You can get a complete list of all supported options using the command

cfx5solve -h

The most important options are

-def {definition or results file}

-ini {initial values file}

Most other cfx5solve options — especially those relative to partitioning, parallel execution, hosts, etc. — should be avoided due to potential conflicts with the batch system on our clusters.

Submitting jobs from the GUI

It is possible to directly submit CFX jobs out of the GUI to the batch system. When you would like to use this option, then you first need to login with X11 forwarding enabled, in order to start the CFX GUI.

ssh -Y username@hostname

where username is your NETHZ username and hostname is the hostname of the cluster you would like to use. Afterwards, you need to load the CFX module. This will set your PATH, MANPATH and other variables needed by CFX. At this point, you can start either CFX Launcher or CFX Solver using respectively

cfx5          ← start CFX Launcher, then select CFX Solver in the Tool menu
cfx5solve     ← start CFX Solver directly

When submitting job through the CFX GUI by choosing file->define run in the solver manager, one has the possibility to choose a run mode from a drop-down menu, that will define the resource requirements as the job length and the memory. For the job length, there are three options.

  • 4 hours
  • 24 hours
  • 120 hours

For the memory, you can choose among three options

  • M = 1999 MB/core
  • L = 3999 MB/core
  • XL = 6999 MB/core

For many jobs, M or L should be sufficient. Please only choose the XL option, when you are running a large simulation that requires a large amount of memory per core.