...
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd $OIFS_HOME $OIFS_TEST/openifs-test.sh -cbt |
where
...
$OIFS_TEST is defined in the platform configuration file (oifs-config.edit_me.sh) as $OIFS_HOME/scripts/build_test
and the command line options are
...
-c creates source directory in $OIFS_HOME, which is used to bring all the sources, e.g. ifs-source, ifs-test and any packages in the bundle (ecbuild, eccodes etc.), together in preparation for the build
-b builds the source. This step creates the directory build in $OIFS_HOME, which is used to build and store
- the OpenIFS double and single precision master executables (ifsMASTER.DP and ifsMASTER.SP, respectively) , which are used to run 3-D OpenIFS. The executables are located in
$OIFS_HOME/build/bin.- The location and name of the executable for OpenIFS is defined in the platform configuration file (oifs-config.edit_me.sh) as
$OIFS_EXEC.
- The location and name of the executable for OpenIFS is defined in the platform configuration file (oifs-config.edit_me.sh) as
- the double and single precision Single Column Model (SCM) executables (MASTER_scm.DP and MASTER_scm.SP, respectively), which are used to run the SCM derived from OpenIFS. The executables are located in
$OIFS_HOME/build/bin.- The location and name of the executable for the SCM is defined in the platform configuration file (oifs-config.edit_me.sh) as
$SCM_EXEC.
- The location and name of the executable for the SCM is defined in the platform configuration file (oifs-config.edit_me.sh) as
-t will run the ifs-test t21 tests, which comprise of
- 21 3-D OpenIFS forecast-only tests with and without chemistry
- 1 SCM test (based on TWP-ICE)
In addition to the command line options defined above (-cbt) , openifs-test.sh allows a user to add ecbuild options from command line using the -- notation, e.g.,
$OIFS_TEST/openifs-test.sh -cbt --without-single-precision.
The main available options are--arch=<add path of arch file>
- Allows a user to over-ride $OIFS_ARCH loaded while sourcing oifs-config.edit_me.s
h
--without-single-precision or --without-double-precision
- By default both single and double precision executables are built. These options pertmit the exclusion of double or single precision, which speeds up the build
--build-type=DEBUG
- Builds the executable in debug mode with bounds checking, some trapping and no compiler optimisation
If everything has worked correctly then all tests should have passed and the script returns the following
...