MPH4: Distributed Multi-Component Environment


Each executable resides on a set of SMP nodes. Components within an executable may overlap on different nodes or processors. Instances within an executable may not overlap on different nodes or processors.

MPH4 contains the following functionality:

component name registration
resource allocation
multi-component single executable, multi-component multi-executable, multi-instance multi executable, etc.
inter-component communication
inquiry on the multi-component environment
standard in/out redirect

The major addition over MPH3 is the multi-instance executable for ensemble simulation.

More explanation and source code as a tar file here (please see copyright info here) or access the individual files as follows:

MPH4 User's Manual (in html, in pdf)
mph.F: MPH_module
Makefile: shared makefile.

test1:
1 executable: Ocean - Atmosphere - Coupler (3 components).
test2:
3 executables: Coupler (1 component); Ice - Land (2 components); Ocean - Atmosphere (2 components).
test3:
2 executables: Coupler; Ice - Land (2 components).
join communicator for Ice and Coupler.
send/recv messages between components.
redirect output.
test4:
1 executable: 3 instances of POP.
test5:
1 executable: 3 instances of POP.
Input arguments passed from command line.
test6:
4 executables: Coupler; 3 instances of POP; Ice - Land; POP_control.
join communicator for Ice and Coupler.
Input arguments passed from command line.
send/recv messages between components.
redirect output.

For more information, please go to web page:
http://www.nersc.gov/research/SCG/acpi/MPH
 

Last modified June 5, 2003.

Back to NERSC ACPI Homepage