Using the queue system on skd-cyclone - Revision history

Csp001 at 10:56, 22 May 2017

2017-05-22T10:56:56Z

← Older revision		Revision as of 10:56, 22 May 2017
Line 44:		Line 44:
	#SBATCH --output=results.%j.txt		#SBATCH --output=results.%j.txt
	#SBATCH --error=errors.%j.out		#SBATCH --error=errors.%j.out
	#SBATCH --mail-type=~~ALL~~		#SBATCH --mail-type=END
			#SBATCH --mail-type=FAIL
	#SBATCH --ntasks=1		#SBATCH --ntasks=1
	#SBATCH --cpus-per-task=4		#SBATCH --cpus-per-task=4
Line 113:		Line 114:
	*'''error''': error messages will be written to this file. %j is a placeholder for the jobid		*'''error''': error messages will be written to this file. %j is a placeholder for the jobid
	Example: <code>--error=errors.%j.out</code>		Example: <code>--error=errors.%j.out</code>
	*'''mail-type''': an email will be send on normal completion (parameter END) or error (parameter FAIL) or ~~both~~ (parameter ALL)		*'''mail-type''': an email will be send on normal completion (parameter END) or error (parameter FAIL) or for all occations (parameter ALL). For a combination of parameters (e.g. END and FAIL) the line must be included several times.
	Example: <code>--mail-type=ALL</code>		Example: <code>--mail-type=ALL</code>
	*'''time''': maximum requested computation time (12h in the example below)		*'''time''': maximum requested computation time (12h in the example below)

Csp001 at 06:34, 22 May 2017

2017-05-22T06:34:56Z

← Older revision		Revision as of 06:34, 22 May 2017
Line 44:		Line 44:
	#SBATCH --output=results.%j.txt		#SBATCH --output=results.%j.txt
	#SBATCH --error=errors.%j.out		#SBATCH --error=errors.%j.out
	#SBATCH --mail-type=~~ERR,END~~		#SBATCH --mail-type=ALL
	#SBATCH --ntasks=1		#SBATCH --ntasks=1
	#SBATCH --cpus-per-task=4		#SBATCH --cpus-per-task=4
Line 113:		Line 113:
	*'''error''': error messages will be written to this file. %j is a placeholder for the jobid		*'''error''': error messages will be written to this file. %j is a placeholder for the jobid
	Example: <code>--error=errors.%j.out</code>		Example: <code>--error=errors.%j.out</code>
	*'''mail-type''': an email will be send on normal completion (parameter END) or error (parameter ~~ERR~~)		*'''mail-type''': an email will be send on normal completion (parameter END) or error (parameter FAIL) or both (parameter ALL)
	Example: <code>--mail-type=~~ERR,END~~</code>		Example: <code>--mail-type=ALL</code>
	*'''time''': maximum requested computation time (12h in the example below)		*'''time''': maximum requested computation time (12h in the example below)
	Example: <code>--time=12:00:00</code>		Example: <code>--time=12:00:00</code>

Csp001: /* Description of each element */ Make clear END is only for normal completion, do ERR,END by default.

2017-05-22T06:26:48Z

Description of each element: Make clear END is only for normal completion, do ERR,END by default.

← Older revision		Revision as of 06:26, 22 May 2017
Line 113:		Line 113:
	*'''error''': error messages will be written to this file. %j is a placeholder for the jobid		*'''error''': error messages will be written to this file. %j is a placeholder for the jobid
	Example: <code>--error=errors.%j.out</code>		Example: <code>--error=errors.%j.out</code>
	*'''mail-type''': an email will be send on completion (parameter END) or error (parameter ERR)		*'''mail-type''': an email will be send on normal completion (parameter END) or error (parameter ERR)
	Example: <code>--mail-type=END</code>		Example: <code>--mail-type=ERR,END</code>
	*'''time''': maximum requested computation time (12h in the example below)		*'''time''': maximum requested computation time (12h in the example below)
	Example: <code>--time=12:00:00</code>		Example: <code>--time=12:00:00</code>

Csp001: /* Short tutorial */ Write mail on error by default

2017-05-22T06:25:31Z

Short tutorial: Write mail on error by default

← Older revision		Revision as of 06:25, 22 May 2017
Line 44:		Line 44:
	#SBATCH --output=results.%j.txt		#SBATCH --output=results.%j.txt
	#SBATCH --error=errors.%j.out		#SBATCH --error=errors.%j.out
	#SBATCH --mail-type=END		#SBATCH --mail-type=ERR,END
	#SBATCH --ntasks=1		#SBATCH --ntasks=1
	#SBATCH --cpus-per-task=4		#SBATCH --cpus-per-task=4

Hso039: /* Description of each element */

2017-04-06T07:25:13Z

Description of each element

← Older revision		Revision as of 07:25, 6 April 2017
Line 96:		Line 96:
	These parameters control for example the output directory, emails, resource allocation and emailing.		These parameters control for example the output directory, emails, resource allocation and emailing.

	The most important aspect is to determine the memory demands of your job. This is described here:		'''The most important aspect is to determine the memory demands of your job.''' This is nicely described here:
	[https://rc.fas.harvard.edu/resources/documentation/slurm-memory/ Finding out which memory limits to use]		[https://rc.fas.harvard.edu/resources/documentation/slurm-memory/ Finding out which memory limits to use]

	The most common script parameters are explained here in short:		The most common script parameters are explained here in short:

	*''mem''': how much memory your job will use at most (in MB).		*'''mem''': how much memory your job will use at most (in MB).
	Example: <code> --mem 1000</code>		Example: <code> --mem 1000</code>
	*'''workdir''': output files will be created in this directory.		*'''workdir''': output files will be created in this directory.

Hso039: /* Description of each element */

2017-04-06T07:24:22Z

Description of each element

← Older revision		Revision as of 07:24, 6 April 2017
Line 95:		Line 95:
	#SBATCH --<parameter>=<argument>		#SBATCH --<parameter>=<argument>
	These parameters control for example the output directory, emails, resource allocation and emailing.		These parameters control for example the output directory, emails, resource allocation and emailing.

			The most important aspect is to determine the memory demands of your job. This is described here:
			[https://rc.fas.harvard.edu/resources/documentation/slurm-memory/ Finding out which memory limits to use]

	The most common script parameters are explained here in short:		The most common script parameters are explained here in short:

			*''mem''': how much memory your job will use at most (in MB).
			Example: <code> --mem 1000</code>
	*'''workdir''': output files will be created in this directory.		*'''workdir''': output files will be created in this directory.
	Example: <code> --workdir=/scratch/$USER</code>		Example: <code> --workdir=/scratch/$USER</code>

Hso039: /* Short tutorial */

2016-12-27T13:17:05Z

Short tutorial

← Older revision		Revision as of 13:17, 27 December 2016
Line 41:		Line 41:
	#SBATCH --job-name=my_slurm_job		#SBATCH --job-name=my_slurm_job
	#SBATCH --workdir=/scratch/$USER		#SBATCH --workdir=/scratch/$USER
	#SBATCH --partition=~~default~~		#SBATCH --partition=normal
	#SBATCH --output=results.%j.txt		#SBATCH --output=results.%j.txt
	#SBATCH --error=errors.%j.out		#SBATCH --error=errors.%j.out

Hso039: /* Short tutorial */

2016-12-27T12:57:59Z

Short tutorial

← Older revision		Revision as of 12:57, 27 December 2016
Line 45:		Line 45:
	#SBATCH --error=errors.%j.out		#SBATCH --error=errors.%j.out
	#SBATCH --mail-type=END		#SBATCH --mail-type=END
	#SBATCH --~~time~~=~~12:00:00~~		#SBATCH --ntasks=1
			#SBATCH --cpus-per-task=4

	#apply any required path settings		#apply any required path settings

Hso039: /* Description of each element */

2016-12-27T12:57:21Z

Description of each element

← Older revision		Revision as of 12:57, 27 December 2016
Line 112:		Line 112:
	Example: <code>--time=12:00:00</code>		Example: <code>--time=12:00:00</code>
	*'''ntasks''': number of cores requested, for example for a MPI parallelisation		*'''ntasks''': number of cores requested, for example for a MPI parallelisation
	Example:<code>ntasks=1</code>		Example:<code>--ntasks=1</code>
	*'''cpus-per-task''': number of parallel threads to be run, for example for OpenMP parallelisation		*'''cpus-per-task''': number of parallel threads to be run, for example for OpenMP parallelisation
	Example: <code>--cpus-per-task=4</code>		Example: <code>--cpus-per-task=4</code>

Hso039: /* Description of each element */

2016-11-02T14:39:04Z

Description of each element

← Older revision		Revision as of 14:39, 2 November 2016
Line 112:		Line 112:
	Example: <code>--time=12:00:00</code>		Example: <code>--time=12:00:00</code>
	*'''ntasks''': number of cores requested, for example for a MPI parallelisation		*'''ntasks''': number of cores requested, for example for a MPI parallelisation
	Example:<code<ntasks=1</code>		Example:<code>ntasks=1</code>
	*'''cpus-per-task''': number of parallel threads to be run, for example for OpenMP parallelisation		*'''cpus-per-task''': number of parallel threads to be run, for example for OpenMP parallelisation
	Example: <code>--cpus-per-task=4</code>		Example: <code>--cpus-per-task=4</code>