Commit a7b0e3dc authored by Radim Vavřík's avatar Radim Vavřík
Browse files

Changed README extension.

parent 49b0b324
Uncertainty modelling for BOSP
This software provides uncertainty modelling of rainfall-runoff model Math1D
adapted for execution as a managed application under the BOSP.
- Properly installed and configured BOSP framework
1) Place root folder of the application (MpiUncertainty) to the user
contribution folder of the BOSP installation
(e.g. /home/%user%/BOSP/contrib/user).
2) Start a BOSP shell by sourcing the environment configuration script
$ . ~/BOSP/out/etc/bbque/bosp_init.env
3) Move to the BOSP working directory and install the newly added application:
$ cd path/to/BOSP
$ make bootstrap
4) Start a BOSP configuration menu:
$ make menuconfig
5) In the menuconfig, enable the newly added application (e.g. MpiUncertainty):
Applications -> [*] MpiUncertainty (NEW)
6) Edit AWMs resources requirements in recipes located under the application
recipes folder (e.g. /home/%user%/BOSP/contrib/user/MpiUncertainty/recipes)
to fit the hardware platform possibilities. For more details about recipes see
7) Recompile BOSP including all enabled applications:
$ make
or compile only newly added application (e.g. MpiUncertainty):
$ make mpiuncertainty
Running application
1) Start a BOSP shell by sourcing the environment configuration script
$ . ~/BOSP/out/etc/bbque/bosp_init.env
2) Move to the BOSP working directory:
$ cd path/to/BOSP
3) Start a BBQUE deamon (requires root privileges):
$ bbque-startd
4) Run the application:
Usage: mpiuncertainty [options]
MpiUncertainty Configuration Options:
-h [ --help ] print help message
-v [ --version ] print program version
-C [ --conf ] arg (=/home/%user%/BOSP/out/etc/bbque/MpiUncertainty.conf)
MpiUncertainty BBQUE configuration file
-u [ --unconf ] arg (=/home/%user%/BOSP/contrib/user/MpiUncertainty/data/config.xml)
Uncertainty configuration file
-r [ --recipe ] arg (=MpiUncertainty) recipe name (for all EXCs)
Enabling additional BBQUE recipes
By default, usage of two independent recipes is supported. To enable additional
recipes follow the steps below:
1) Create a new receipe (XML file with filename terminated by .recipe extension)
under the application recipes folder
(e.g. /home/%user%/BOSP/contrib/user/MpiUncertainty/recipes). If any parameters
and/or system metrics are used, continue with following steps.
2) Add the opList genertion target to the CMakeLists.txt file located
in the application src folder
(e.g. /home/%user%/BOSP/contrib/user/MpiUncertainty/src):
DEPENDS ${PROJECT_SOURCE_DIR}/recipes/MpiUncertainty3.recipe
COMMAND bbque-oplb -v -v BBQUE_RTLIB_OPLIST=opList3 ${PROJECT_SOURCE_DIR}/recipes/MpiUncertainty3.recipe
COMMENT "Generating OPList3..."
Where is any unique filename of the generated source file,
opList3 is an appropriate variable name and MpiUncertainty3.recipe is filename
of the newly created recipe.
3) Add the filename (without the .cc extension) of the generated oplist
source file from the previous step to the sources list in the same
CMakeLists.txt file located in the application src folder
(e.g. /home/%user%/BOSP/contrib/user/MpiUncertainty/src).
4) Declare the oplist variable (e.g. opList3) at the beginning
of the source file:
extern ba::OperatingPointsList opList3;
5) Use the oplist variable in the MpiUncertainty::onConfigure method, e.g.:
if(rpc_name == "MpiUncertainty3")
m_threadsNumber = opList3[awm_id].parameters["threads"];
Where MpiUncertainty3 is the filename of the newly created receipe,
m_threadsNumber is the member variable, opList3 is a vector of AWM parameters
(e.g. threads) and system metrics, and awm_id is the ID of the current AWM. For
more details about advanced receipe creation see
6) Build the application:
$ make mpiuncertainty
7) Run the application with the -r flag, e.g.:
$ mpiuncertainty -r MpiUncertainty3
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment