The fix is now in the CVS. Running test/sodium no longer produces the
evbout file.
I only made a minor modification to sander.f. The "cleanup" for the EVB
will be done at a later date, after we implement a few more functions
and then perform a full audit of EVB. If you notice anything weird in
the source or in the execution, please let me know.
Also, I was unable to compile the serial code (ifort). The error message:
....
IPO Error: unresolved : xrandom_
Referenced in ../obj/boxmove.o
Referenced in ../obj/boxstep.o
Referenced in ../obj/resstep.o
Referenced in ../obj/rottr.o
Referenced in ../obj/random.o
IPO Error: unresolved : irandom_
Referenced in ../obj/resmove.o
Referenced in ../obj/rottr.o
Referenced in ../obj/submove.o
Referenced in ../obj/parop2.o
.....
-Kim
Ross Walker wrote:
> Hi All and in particular evb people...
>
> It seems that when running amber 10 in parallel the evb_bcast and evb_alloc
> routines are always called even if we are not doing an evb run.
>
> This always results in an evbout file being produced. It seems that
> something is wrong here and that any calls to the evb routines should be
> protected in some way so that they are not called for non evb runs.
>
> Comments?
>
> All the best
> Ross
>
> /\
> \/
> |\oss Walker
>
> | HPC Consultant and Staff Scientist |
> | San Diego Supercomputer Center |
> | Tel: +1 858 822 0854 | EMail:- ross.rosswalker.co.uk |
> | http://www.rosswalker.co.uk | PGP Key available on request |
>
> Note: Electronic Mail is not secure, has no guarantee of delivery, may not
> be read every day, and should not be used for urgent or sensitive issues.
>
>
Received on Sun Oct 08 2006 - 06:07:22 PDT
