HPC/Applications/vasp5: Difference between revisions

From CNM Wiki
Jump to navigation Jump to search
m (Redirected page to HPC/Applications/vasp)
 
(27 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Binaries available ==
#REDIRECT [[HPC/Applications/vasp]]
The vasp5 modules as of version vasp5/5.2.12a-mkl-4 contain several binaries, determined by CPP flags in the Makefile as shown.
 
To inspect the available binaries:
ls $VASP5_HOME/bin
 
<!--
sed -n '/DMPI_BLOCK/s/.*8000//p' embody-5.2.12a-mkl-4/build.log  | uniq
-->
; vasp :
(none)
; vasp-chargehalf :
-DNGZhalf
; vasp-gamma :
-DwNGZhalf
; vasp-gamma-chargehalf :
-DwNGZhalf -DNGZhalf
; vasp-tbdyn :
-Dtbdyn
; vasp-tbdyn-chargehalf :
-DNGZhalf -Dtbdyn
; vasp-tbdyn-gamma :
-DwNGZhalf -Dtbdyn
; vasp-tbdyn-gamma-chargehalf :
-DwNGZhalf -DNGZhalf -Dtbdyn
 
== Common flags ==
-DIFC -DRPROMU_DGEMV  -DRACCMU_DGEMV -DCACHE_SIZE=16000  -DMPI -DMPI_BLOCK=8000
 
== Explanantion ==
From <code>vasp.5.2/makefile.linux_pg</code>
<pre>
#-----------------------------------------------------------------------
# possible options for CPP:
# NGXhalf            charge density  reduced in X direction
# wNGXhalf            gamma point only reduced in X direction
# avoidalloc          avoid ALLOCATE if possible
# IFC                work around some IFC bugs
# CACHE_SIZE          1000 for PII,PIII, 5000 for Athlon, 8000 P4
# RPROMU_DGEMV        use DGEMV instead of DGEMM in RPRO (usually  faster)
# RACCMU_DGEMV        use DGEMV instead of DGEMM in RACC (faster on P4)
#  **** definitely use -DRACCMU_DGEMV if you use the mkl library
#-----------------------------------------------------------------------
#-----------------------------------------------------------------------
# additional options for CPP in parallel version (see also above):
# NGZhalf              charge density  reduced in Z direction
# wNGZhalf              gamma point only reduced in Z direction
# scaLAPACK            use scaLAPACK (usually slower on 100 Mbit Net)
#-----------------------------------------------------------------------
</pre>
 
== vdW-DF functional ==
All binaries support the use of the [http://cms.mpi.univie.ac.at/vasp/vasp/vdW_DF_functional_Langreth_Lundqvist_et_al.html vdW-DF functional of Langreth and Lundqvist et al.]
 
No specific preparations are needed other than setting the INCAR flags as documented. The binaries will find the required precalculated kernel  file <code>vdw_kernel.bindat</code> by means of the environment variable <code>$VASP5_HOME</code> which is set by the module. This is a Carbon-specific extension.

Latest revision as of 15:23, June 25, 2013