Thanks! I have been able to get this to run... I was running out of memory apparently. All I have done for now is to use the brute force approach and quadruple the number of processors; I need to run more tests to check exact memory utilization. Incidentally, I can recommend two things when compiling: 1) If using lanczos.f, some compilers might require the '-qextname=flush' tag 2) If only VASP's lapack_double.f and ESSL are being used on an IBM (see e.g. makefile.sp2) , dstev.f (Lapack routine for eigenvalues) will have to be included, although I prefer linking the lapack library directly if available on the machine.
I observe something interesting thus far: when I do a normal VASP run with 8 processors (12gb limit) things work fine. However, when I run only 1 image (IMAGES = 1, ICHAIN = 0, SPRING = -5, LCLIMB = .TRUE.)
with 8 processors (12gb limit again), the code crashes when planning the FFT with insufficient memory. So why does the latter, consume much more memory than the former? Naively, I would expect that both procedures are running only one structure, possibly with some additional information being stored in the NEB case.