分类: LINUX
2009-02-21 14:24:08
Few things were noticed after a successful compilation.
Serial version problems:"Question: I am running VASP on a SGI Origin, and the simple benchmark (benchmark.tar.gz) fails with lib-4201 :
UNRECOVERABLE library error READ operation tried to read past the end-of-record.
Encountered during a direct access unformatted READ from unit 21
Fortran unit 21 is connected to a direct unformatted unblocked file:
"TMPCAR" IOT Trap
Abort (core dumped)
Answer: VASP extrapolates the wave functions between molecular dynamics time steps. To store the wave functions of the previous time
steps either a temporary scratch file (TMPCAR) is used (IWAVPR=1-9) or large work arrays are allocated (IWAVPR=11-19).
On the SGI, the version that uses a temporary scratch file does not compile correctly, and hence the user has to set IWAVPR to 10."
When running the Hg benchmark (bench.Hg.tar.gz), the OUTCAR file has numerous lines saying:
"WARNING in EDDRMM: call to ZHEGV failed, returncode = 6 3 9"
Solution:
This issue is addressed in the VASP support forum ()
Short summary is given here. Possible reasons (this may, once again, be connected to failures calling LAPACK routines):
1) The diagonalization algorithm is not stable for your system
-> Change ALGO = Normal or ALGO = Fast in your INCAR file
2) Your geometry is not reasonable. Maybe your initial structure or the algorithm handling ion relaxation is giving a bad structure
-> Switch to a different ion relaxation scheme (IBRION line in your INCAR)
-> Reduce the step size of the first step by reducing the POTIM value in your INCAR
3) Problem with your LAPACK installation
-> Use the LAPACK routines that came with the VASP library tar-file (vasp.4.lib)
4) If the error does not go away even if you already did the thing described in part 1 (ALGO change), then there may be a problem with LAPACK.
-> Disable the calls to ZHEGV subroutine. This can be done by commenting the line
# define USE_ZHEEVX
in subroutines davidson.F, subrot.F and wavpre_noio.F.
-> Recompile VASP after you changed the subroutines
NOTE TO SELF:
These issues have much in common with the problems usually described with Silicon Graphics computers. How curious...
Jukka-Pekka Jalkanen