This is fixed. [bsallen@knl04 ~]$ cat $COBALT_NODEFILE knl04 knl08 [bsallen@knl04 ~]$ cat $COBALT_NODEFILE | wc -l 2
On Aug 11, 2016, at 1:03 PM, Allen, Benjamin S. <[email protected]> wrote:
It's because wc -l counts newlines, and the node file is missing the trailing newline. I'll fix this this afternoon.
Ben
From: "Steven C. Pieper" <[email protected]> Sent: Aug 11, 2016 12:49 PM To: [email protected] Subject: Re: [JLSE-Intel-NDA] the mystery of COBALT_JOBSIZE
The second possibility doesn't work for some reason I don't understand. I had observed that cat does not list two lines for a 2-node node file:
[knl02 ~] echo $COBALT_NODEFILE /var/tmp/cobalt.327 [knl02 ~] cat /var/tmp/cobalt.327 knl07 knl02[knl02 ~] NODECOUNT=$(cat $COBALT_NODEFILE | wc -l) [knl02 ~] echo $NODECOUNT 1
however vi does show the two lines:
knl07 knl02 ~
Seems very strange.
Steve Steven C. Pieper, Senior Physicist Emeritus: [email protected]
Argonne National Laboratory, Physics Division, Bldg. 203, Argonne, IL 60439 Phone: 630-252-4232 Fax -6008 Secretary, Debra Beres, -4100
http://www.phy.anl.gov/theory/staff/scp.html On 08/11/16 11:43, Allen, Benjamin S. wrote:
Couple ways to deal with this:
mpirun -f $COBALT_NODEFILE -ppn 64
or
NODECOUNT=$(cat $COBALT_NODEFILE | wc -l)
COBALT_NODEFILE and COBALT_JOBID are the only two environmental variables passed from Cobalt, similar to Cooley.
Ben
On Aug 10, 2016, at 6:08 PM, Alvaro <[email protected]> wrote:
hi.
I am not getting any value for COBALT_JOBSIZE.
So I cannot do
proc=64
mpirun -n $((COBALT_JOBSIZE*proc))
How I can get the number of nodes in cobalt?
-- -Alvaro http://web.alcf.anl.gov/~vama/
_______________________________________________ Intel-nda mailing list
[email protected] https://lists.jlse.anl.gov/mailman/listinfo/intel-nda
Intel-nda mailing list
[email protected] https://lists.jlse.anl.gov/mailman/listinfo/intel-nda