compute:tobegin
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| compute:tobegin [2024/08/16 11:12] – created bjorns | compute:tobegin [2024/12/02 09:55] (current) – bjorns | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | An How-To example for beginners. | + | ===== An How-To example for beginners. |
| - | Connect to the cluster with you user and pass | + | Connect to the cluster with you user and pass.\\ |
| - | To utilize the power of the cluster you to add you code (project files) onto your home directory, then run it. | + | To utilize the power of the cluster you to add you code (project files) onto your home directory, then run it.\\ |
| - | If you examine you home directory (use the command " | + | If you examine you home directory (use the command " |
| - | In you working (home) directory create your project files for computing. | + | \\ |
| - | After your coding file's are ready you need you test the code try them and resolve any issue, bugs(debug) | + | In you working (home) directory create your project files for computing. |
| - | When ready send your job(project) to cluster, using sbatch command | + | After your coding file's are ready you need you test the code try them and resolve any issue, bugs(debug)\\ |
| + | When ready send your job(project) to cluster, using **sbatch** command.\\ | ||
| The cluster uses Slurm as a scheduler and workload manager. | The cluster uses Slurm as a scheduler and workload manager. | ||
| To submit your you need to create a file(batch file for Slurm), an example filed is already in your home directory called " | To submit your you need to create a file(batch file for Slurm), an example filed is already in your home directory called " | ||
| - | But user can also create their own batch file for Slurm, but the content of it must follow slurms ruleset to work and it must be executable. | + | But user can also create their own batch file for Slurm, but the content of it must follow slurms ruleset to work and it must be executable.\\ |
| - | Assuming your python file is called | + | \\ |
| - | This is the content of myJob.sh. | + | Assuming your python file is called |
| - | When ready user submit | + | This is the content of myJob.sh\\ |
| - | This should be the result user gets | + | ''# |
| - | For user to see the status of his job issue the command squeue. | + | #SBATCH < |
| + | #SBATCH %%--%%job-name=MyJob\\ | ||
| + | #SBATCH %%--%%gpus-per-node=1\\ | ||
| + | #SBATCH %%--%%mem-per-cpu=2G\\ | ||
| + | #SBATCH < | ||
| + | python3 runSomeCode.py\\ | ||
| + | '' | ||
| + | To submit | ||
| + | This should be the result user gets\\ | ||
| + | For user to see the status of his job issue the command squeue.\\ | ||
| + | \\ | ||
| + | \\ | ||
| + | Beware if coping (uploading) files from Windows to the cluster, you might encounter issues because of different handling of character encoding (Linux/ | ||
| + | [[compute: | ||
| - | |||
| - | Beware if coping (uploading) files from Windows to the cluster, you might encounter issues because of different handling of character encoding (Linux/ | ||
compute/tobegin.1723806744.txt.gz · Last modified: (external edit)
