> (1) it is probably not very practical to run tests using queuing
> systems
> anyway
Except that on a LOT of systems these days this is the only way to run the
test cases since interactive parallel jobs are not allowed or are limited to
a short amount of time that is not sufficient to get the tests completed. On
some, but not all, systems one can request an interactive job through the
queuing system and conceivably run the tests this way but of course the same
issues surround what the 'mpirun' command looks like.
> (3) I am basically suggested a possibility to put a "tag" (named
> in some unique way; for example AMBER_NTHREADS) everywhere it
> is needed in the DO_PARALLEL
> command, and then replace it with the desired number;
> i.e., instead of export DO_PARALLEL='mpirun -np 4' user would do
> export DO_PARALLEL='mpirun -np AMBER_NTHREADS'; I don't know
> whether
> it is worth the effort, probably not since this is just slightly
> less typing over (2), which is much less intrusive
This is the bit I do not think will work and I do not think can be made
anywhere near general enough. Note a number of systems, for example CRAY,
specify both the size of the job (in cores) and the number of cores per node
to use. Would it not make more sense to have several parallel test targets.
E.g. (better names are probably possible)
test.parallel
Tests that can run on any number of cpus.
test.2cpu
Tests that only run on 2 cpus.
test.4cpu
Tests that only run on 4 cpus.
etc. Of course this doesn't deal with the fact that a lot of the test cases
will run on up to 4 cpus say and that is all but happily run on 1,2,3 or 4
cpus. The current approach that some test cases have, which is to skip the
test if the number of cpus is not compatible is a bad idea I think since
this just results in these test cases never being run.
All the best
Ross
/\
\/
|\oss Walker
| Assistant Research Professor |
| San Diego Supercomputer Center |
| Tel: +1 858 822 0854 | EMail:- ross.rosswalker.co.uk |
|
http://www.rosswalker.co.uk |
http://www.wmd-lab.org/ |
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.
> > However, if I'm understanding numprocs.awk correctly (I don't know
> awk
> > that well, but I'm familiar with some C-type syntax, and it looks
> like
> > a very simple script), it will grab the number of processors from the
> > argument following -np or -n (perhaps -c should be tossed in there as
> > well), so wouldn't this, also, be useless in the situations described
> > above?
>
> Yes. tests/ncsu/common.sh additionally checks environment variable
> MPICH_NP (the way I am using to start mpi jobs locally).
>
> Best,
>
> Volodymyr
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Feb 18 2010 - 20:00:04 PST
