Dear developers,
I came across a potential issue (not quite the status of a bug) in the NEB routines (v2.04b). Specifically, the default setting appears to set the climbing image on -- line 560 in neb.f sets lclimb=.TRUE. before reading the INCAR. This is somewhat inconsistent with the online ...
Search found 4 matches
- Tue Jul 31, 2012 3:36 pm
- Forum: VTSTTools
- Topic: Possible problem with default NEB settings
- Replies: 1
- Views: 30477
- Sun Dec 17, 2006 5:44 pm
- Forum: VTSTTools
- Topic: NEB crash on IBM
- Replies: 10
- Views: 102918
I checked the bands and planewaves and you suggested and therein lies my problem. If I repeat my run by copying the *same* POSCAR file to directories 00, 01 and 02 and run the NEB, things work like a normal VASP run. My problem was that that the structure in 01 was intermediate between 00 and 02 ...
- Sun Dec 17, 2006 4:36 pm
- Forum: VTSTTools
- Topic: NEB crash on IBM
- Replies: 10
- Views: 102918
- Fri Dec 15, 2006 5:41 pm
- Forum: VTSTTools
- Topic: NEB crash on IBM
- Replies: 10
- Views: 102918
NEB crash on IBM
Dear all,
I compiled VASP with the VTST code on an IBM P6x and I seem to be running into problems. Brief description of what I did first:
- When compiling, I had to add the dstev.f to VASP's lapack_double.f file---I was subsequently able to link the Lapack library directly to avoid this hack ...
I compiled VASP with the VTST code on an IBM P6x and I seem to be running into problems. Brief description of what I did first:
- When compiling, I had to add the dstev.f to VASP's lapack_double.f file---I was subsequently able to link the Lapack library directly to avoid this hack ...