A serial job uses one CPU core. To run a serial job in the batch system you should not<\/strong> specify a partition or a queue<\/em> (which you may have done on other systems).<\/p>\n We now recommend loading modulefiles within your jobscript so that you have a full record of how the job was run and it also minimises the potential for conflict between different pieces of software and libraries. See the example jobscript below for how to do this. <\/p>\n You should run jobs from within your scratch<\/em> area:<\/p>\n An example single core job script:<\/p>\n To submit the job to the batch system:<\/p>\n Where jobscript<\/em> is replaced with the name of your submission script.<\/p>\n The above serial job can also be achieved all on the command-line on the login node (a quick way of running a serial job in batch). Note that you will need to load any modulefiles before<\/em> submitting the job. The batch system takes a copy of any settings made by the modulefile so that they are visible<\/em> to the job when it eventually runs. You could logout of the CSF before the job runs and it will still have a copy of the modulefile settings allowing the job to run correctly. <\/p>\n where Serial jobs can run on Intel Cascade Lake<\/em> compute-nodes. The type of Intel hardware used (amount of memory available to the job, CPU architecture, runtime) can be controlled with extra jobscript flags as shown below. But in general you don’t need to specify any of these flags in your jobscript unless you know your job needs more memory or a specific type of CPU for example.<\/p>\ncd ~\/scratch\/my_code\/run01 # for example<\/pre>\n
\r\n#!\/bin\/bash --login\r\n#SBATCH -n 1 # (or --ntasks=1) Use just 1 core\r\n\r\n# OPTIONAL LINE: the default partition is serial\r\n#SBATCH -p serial # (or --partition=serial)\r\n\r\n# The default output file will be named slurm-JOBID<\/em>.out\r\n# To use SGE-style file names, use the following\r\n# #SBATCH -o %x.o%j # %x is job name (default name is the jobscript filename)\r\n# #SBATCH -e %x.e%j # If no -e flag used, everything goes in the -o file\r\n\r\n# Load any required modulefiles\r\nmodule load someapp\/1.2.3<\/em>\r\n\r\n# Now the commands to be run by the job\r\ntheapp.exe\r\n<\/pre>\n
\r\nsbatch jobscript<\/em>\r\n<\/pre>\n
Command-line one-liner…<\/h3>\n
\r\nmodule load someapp\/1.2.3<\/em>\r\nsbatch -J jobname<\/em> --wrap=\"theapp.exe optional-args<\/em>\"\r\n #\r\n # Optional. If not given the job will be named 'wrap' in the squeue listing.\r\n<\/pre>\n
optional-args<\/em><\/code> are any command line flags that you want to pass to the theapp.exe<\/code> program (or your own program). The --wrap=\"...\"<\/code> wraps your commands up as though they were in a jobscript.<\/p>\nSerial Hardware<\/h2>\n