next up previous contents index
Next: Environment variables Up: Command line arguments Previous: Testing options   Contents   Index


Heterogeneous load file

The load file is a text file you create with your favorite text editor. It has two kinds of entries: comments and application members. Comments are lines on which the first text that appears is a pound sign (#). These are ignored by yod. The other type of entry lists a member of the parallel application and has this format:

{yod-options} {executable-path-name} {application arguments}

The only yod options accepted in a load file are -sz and -list.

Example:

yod -l 100..200 myLoadFile

The contents of myLoadFile are listed here:

#
# load file to run my computation and parallel vis server
#
-sz 2 -l 500,501 my-vis-code bufsize=2048
-sz 64 my-computational-code

In this example, the executable file my-vis-code will be loaded on nodes 500 and 501, will be passed the argument bufsize=2048, and will be ranks 0 and 1 in the parallel application. The executable file my-computational-code will be loaded on 64 free nodes found in the node number list 100 through 200. These processes will have ranks 2 through 65 in the parallel application. MPI users note that the 66 processes described will populate a single MPI_COMM_WORLD on application start up.

If a load file is provided, any size argument given on the yod command line is ignored. If there is no node list given in the load file for a member, then the node list given on the yod command line will be used. If in addition there is no node list given on the yod command line, then the requested nodes will be allocated from anywhere among the general collection of free nodes. If there is no size argument provided in the load file, but a node list is provided, it will be assumed that you want all the nodes in the node list. If there is no size argument provided in the load file and also no node list, it will be assumed that you want one node from anywhere.


next up previous contents index
Next: Environment variables Up: Command line arguments Previous: Testing options   Contents   Index
Lee Ann Fisk 2001-06-25