...
The SCM source code is extracted and installed alongside OpenIFS. Thus, if not done already, to install the SCM please follow the instructions detailed in Getting started to install OpenIFS.
In short the , once the source code is extracted and installed from from https://sites.ecmwf.int/openifs/openifs-data/src/48r1/openifs-48r1.tar.gz, then the code can be built using the following:
| Code Block | ||||
|---|---|---|---|---|
| ||||
# load the OpenIFS and SCM environment variables
source /path/to/file/location/oifs-config.edit_me.sh
# using our installation example:
# source $HOME/openifs-48r1.1/oifs-config.edit_me.sh
# change to the home directory for OpenIFS and SCM
cd $OIFS_HOME
# Use the openifs-test.sh script to build and automatically test OpenIFS and the SCM
$OIFS_TEST/openifs-test.sh -cbt |
...
- The location and name of the executable for the SCM is are defined in the platform configuration file (oifs-config.edit_me.sh) as
$SCM_EXEC
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
source /path/to/file/location/oifs-config.edit_me.sh
# using our installation example:
# source $HOME/openifs-48r1.1/oifs-config.edit_me.sh |
This will load all the OpenIFS and SCM environment variables. The OpenIFS variables are described in Getting started, so here we focus on the SCM variables, which are defined in oifs-config.edit_me.sh, with comments, as shown below
...
It is worth noting that the SCM environment variables depend on the OIFS_HOME and OIFS_EXPT, which are also defined by sourcing oifs-config.edit_me.sh. In the above there is the assumption that the SCM executable exists in ${OIFS_HOME}/build/bin and that the SCM test case package exists in $OIFS_EXPT.
Extract SCM test-case package
In a similar fashion to the OpenIFS package and the experiment data, the SCM test-case package can be download from https://sites.ecmwf.int/openifs/openifs-data/scm/48r1/scm_openifs_48r1.1.tar.gz. Please note that access to this web site is restricted to registered OpenIFS users, i.e. your personal ECMWF account must have been added to the OpenIFS user policy.
In the example below we assume that the SCM package shall be installed in the $OIFS_EXPT directory, where the $OIFS_EXPT is the OpenIFS experiment directory, which is defined oifs-config.edit_me.sh, and that wget utility is available for convenient download:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd $OIFS_EXPT wget# download the scm_openifs_48r1.tar.gz from https://sites.ecmwf.int/openifs/openifs-data/scm/48r1/scm_openifs_48r1.1tar.gz model and copy the tarball to your $OIFS_EXPT directory: cp scm_openifs_48r1.tar.gz $OIFS_EXPT tar -xvzf scm_openifs_-48r1.tar.gz |
| Note |
|---|
The untarred SCM package is small, ~45 Mb and data produced by a standard individual SCM simulation is also low. However, if I user is planning to perform many simulations and store the data, which is often the case, the disk space usage can become large. If this is the plan, then a user may need to consider installing the SCM test-case package on a larger disk area than $ |
Once installed it is important to ensure that the $OIFS_EXPT is set to the directory that scm_openifs has been installed in. For example, in the template oifs-config.edit_me.sh, $OIFS_EXPT=${HOME}/openifs-expt . In this scenario, the directory scm_openifs needs to be in $OIFS_EXPT or `${HOME}/openifs-expt/.
...
Once the SCM has successfully, it will produce output in $SCM_RUNDIR/scmout_<casename>_<expt_name>_<timestep>, which contains some netcdf files.
As part of the scm_openifs download package we provide a python script $SCM_RUNDIR/plotscm.py , which can be used to plot some profiles at a certain time, 2-d time height plots and some scalar timeseries. This script will work without any changes for the DYCOMS case and the default settings of callscm by type the following
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd $SCM_RUNDIR
python3 plotscm.py |
For the defaults, the above will produce plot_DYCOMS directory, which contains png plots
| Note | |||||||
|---|---|---|---|---|---|---|---|
On ECMWF ATOS, it is necessary to load python3 before attempting to run plotscm.py, i.e.,
|
To plot the other cases or experiments with different names and/or timesteps to the defaults, at present, the user will need to edit plotscm.py appropriately.