compile vasp with new neb code

Vasp transition state theory tools

Moderator: moderators

Post Reply
boy7478
Posts: 6
Joined: Mon Mar 26, 2007 2:52 pm

compile vasp with new neb code

Post by boy7478 »

Hi all,
our group has compiled new Henkelman code to our vasp 4.6.26.
the result, new vasp has lower size in byte. from the original version around 20 Mbyte then it became only around 3 MByte.

is it normal?

thanks.
graeme
Site Admin
Posts: 2291
Joined: Tue Apr 26, 2005 4:25 am
Contact:

Post by graeme »

I can't imagine how this happened. We add a few modules which might slightly increase the binary size. Our binaries, built with PGI, are 8MB. The decrease in binary size is very strange.
boy7478
Posts: 6
Joined: Mon Mar 26, 2007 2:52 pm

Post by boy7478 »

PGI is parallel code in Fortran,right?
Does it mean that we have to make changes in makefile & compile of the parallel version of vasp instead of serial version?

thanks.
graeme
Site Admin
Posts: 2291
Joined: Tue Apr 26, 2005 4:25 am
Contact:

Post by graeme »

PGI (Portland Group) is just a fortran compiler. It is generally good to build both serial and parallel versions of vasp. To use the NEB, you must have the parallel version. The dimer and lanczos methods can both be run in serial or parallel.
andri
Site Admin
Posts: 117
Joined: Tue Apr 26, 2005 6:20 am

Post by andri »

Did your old executable have all the necessary libraries build statically into it? Try to run "ldd <old_executable>" and "ldd <new_executable>" and see if there is any difference.
boy7478
Posts: 6
Joined: Mon Mar 26, 2007 2:52 pm

Post by boy7478 »

refer to file that sent by thshy
Posted: Thu Oct 19, 2006 7:17 am about "A question about NEB", i saw that his vaspts file is having the same size in bytes with the one that we compile.
i've checked what andri suggested, this is the result from the new compiled vasp :
vasp:
/System/Library/Frameworks/vecLib.framework/Versions/A/vecLib (compatibility version 1.0.0, current version 182.24.0)
/opt/ibmcmp/lib/libxlf90.A.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/ibmcmp/lib/libxlomp_ser.A.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/ibmcmp/lib/libxlfmath.A.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.8)

and the old one was :
vasp:
/System/Library/Frameworks/vecLib.framework/Versions/A/vecLib (compatibility version 1.0.0, current version 152.0.0)
/opt/ibmcmp/lib/libxlf90.A.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/ibmcmp/lib/libxlomp_ser.A.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/ibmcmp/lib/libxlfmath.A.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1)

is there any problem with this message?
Post Reply