Difference between revisions of "Main Page"
(→Basic HOWTO) |
(→Basic HOWTO - modified for SLURM) |
||
| Line 25: | Line 25: | ||
#!/bin/bash | #!/bin/bash | ||
#SBATCH -J helloWorld # name of job | #SBATCH -J helloWorld # name of job | ||
| − | #SBATCH -p cpu | + | #SBATCH -p cpu # name of partition or queue (default is cpu) |
#SBATCH -o helloWorld.out # name of output file for this submission script | #SBATCH -o helloWorld.out # name of output file for this submission script | ||
#SBATCH -e helloWorld.err # name of error file for this submission script | #SBATCH -e helloWorld.err # name of error file for this submission script | ||
| Line 35: | Line 35: | ||
<code>sbatch job_script.sh</code> | <code>sbatch job_script.sh</code> | ||
| − | This will enqueue our ''job'' to the default ''partition'' (or ''queue'') which is <code>cpu</code>. The scheduler decides which particular machine in the specified queue has ''resources'' needed to run the job. Typically we will see a message which tells us the ID of our job ( | + | This will enqueue our ''job'' to the default ''partition'' (or ''queue'') which is <code>cpu</code>. The scheduler decides which particular machine in the specified queue has ''resources'' needed to run the job. Typically we will see a message which tells us the ID of our job (3 in this example): |
| − | + | Submitted batch job 3 | |
| − | The | + | The options used in this example are specified inside the script using the ''#SBATCH'' directive. Any option can be specified either in the script or as a command line parameter (see ''man sbatch'' for details). |
| − | |||
| − | |||
| − | We | + | We can specify custom arguments '''before''' the name of the script: |
| − | + | sbatch --export=ARG1='firstArg',ARG2='secondArg' job_script.sh | |
| − | + | ||
| − | + | These can be accessed in the job script as <code>$ARG1</code> and <code>$ARG2</code>. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 16:49, 16 November 2022
Welcome to AIC
AIC (Artificial Intelligence Cluster) is a computational grid with sufficient computational capacity for research in the field of deep learning using both CPU and GPU. It was built on top of SGE scheduling system. MFF students of Bc. and Mgr. degrees can use it to run their experiments and learn the proper ways of grid computing in the process.
Access
AIC is dedicated to UFAL students who will get an account if requested by authorized lector.
Connecting to the Cluster.
Use SSH to connect to the cluster:
ssh LOGIN@aic.ufal.mff.cuni.cz
Basic HOWTO
Following HOWTO is meant to provide only a simplified overview of the cluster usage. It is strongly recommended to read some further documentation (CPU or GPU) before running some serious experiments. More serious experiments tend to take more resources. In order to avoid unexpected failures please make sure your quota is not exceeded.
Rule 0: NEVER RUN JOBS DIRECTLY ON aic.ufal.mff.cuni.cz HEADNODE. Use *srun* to get computational node shell!
Suppose we want to run some computations described by a script called job_script.sh:
#!/bin/bash #SBATCH -J helloWorld # name of job #SBATCH -p cpu # name of partition or queue (default is cpu) #SBATCH -o helloWorld.out # name of output file for this submission script #SBATCH -e helloWorld.err # name of error file for this submission script # run my job (some executable) sleep 5 echo "Hello I am running on cluster!"
We need to submit the job to the cluster which is done by logging on the submit host aic.ufal.mff.cuni.cz and issuing the command:
sbatch job_script.sh
This will enqueue our job to the default partition (or queue) which is cpu. The scheduler decides which particular machine in the specified queue has resources needed to run the job. Typically we will see a message which tells us the ID of our job (3 in this example):
Submitted batch job 3
The options used in this example are specified inside the script using the #SBATCH directive. Any option can be specified either in the script or as a command line parameter (see man sbatch for details).
We can specify custom arguments before the name of the script:
sbatch --export=ARG1='firstArg',ARG2='secondArg' job_script.sh
These can be accessed in the job script as $ARG1 and $ARG2.
