VASP: Difference between revisions

Jump to navigation Jump to search
130 bytes added ,  7 years ago
Line 55: Line 55:
== Example of a VASP job script ==
== Example of a VASP job script ==


The following is a job script to run VASP as parallel using slurm job scheduler:
The following is a job script to run VASP in parallel using the Slurm job scheduler:


{{File
{{File
Line 62: Line 62:
   |contents=
   |contents=
#!/bin/bash
#!/bin/bash
#SBATCH --account=def-<SOMEUSER>
#SBATCH --account=<ACCOUNT>
#SBATCH --ntasks=4               # number of MPI processes
#SBATCH --ntasks=4             # number of MPI processes
#SBATCH --mem-per-cpu=1024M     # memory; default unit is megabytes
#SBATCH --mem-per-cpu=1024M   # memory
#SBATCH --time=0-00:05           # time (DD-HH:MM)
#SBATCH --time=0-00:05         # time (DD-HH:MM)
module load vasp/<VERSION>
module load vasp/<VERSION>
srun <VASP>
srun <VASP>
}}
}}


The above job script uses 4 cpu's and 1024MB memory per cpu (in this case the total memory is 4x1024MB). <SOMEUSER> in above example is your PI's username, <VERSION> is the vasp version that you would like to run. It can be 4.6 or 5.4.1. <VASP> is the name of the executable. The above section "Executable" shows the various executables that you can choose for each vasp version.  
The above job script requests four CPU cores and 4096MB memory (4x1024MB). <ACCOUNT> is a Slurm account name; see [[Running_jobs#Accounts_and_projects|Accounts and projects]] if you don't know what to put there. <VERSION> is the VASP version that you would like to run, 4.6 or 5.4.1. <VASP> is the name of the executable. The above section "Executable" shows the various executables that you can choose for each version.  


submit the job from the input file directory
VASP uses four named input files: INCAR, KPOINTS, POSCAR, POTCAR. It is best to prepare VASP input files in a separate directory for each job. The submit the job from that directory with
  sbatch vasp_job.sh
  sbatch vasp_job.sh


Please note that:
If you do not know how much memory you need for your job, prepare all your input files and then run <code>makeparam</code> in an interactive job submission. Then use the result as required memory for the next run. For more information about interactive jobs see [[Running jobs#Interactive_jobs|Interactive jobs]].


VASP uses 4 named input files: INCAR, KPOINTS, POSCAR, POTCAR. You can prepare VASP input files in a sub-directory per job.
If you want to use 32 or more cores, please read about [[Job_scheduling_policies#Whole_nodes_versus_cores|whole-node scheduling]].
 
If you do not have any idea about how much memory you need for your job you can run "makeparam" first after you prepared all your input files and in an interactive job submission. Then use the result as required memory for the next run. For more information about interactive jobs please take a look at [[Running jobs]]


<!--T:14-->
<!--T:14-->
[[Category:Software]]
[[Category:Software]]
</translate>
</translate>
Bureaucrats, cc_docs_admin, cc_staff
2,918

edits

Navigation menu