...
Before the SCM can be run, it is necessary to
...
- obtain and extract the SCM test-case package.
- load the SCM environment variables by source the
oifs-config.edit_me.sh
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 user's HOME directory, and that the wget utility is available for convenient download:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd $HOME
wget https://sites.ecmwf.int/openifs/openifs-data/scm/48r1/scm_openifs_48r1.1.tar.gz
tar -xvzf scm_openifs_48r1.tar.gz |
- obtain and extract the SCM test-case package
...
Load SCM environment variables
...
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
| Code Block | ||||
|---|---|---|---|---|
| ||||
#---Single-column model environment variables
#---Test case list, which can contain DYCOMS, BOMEX AND TWPICE
export SCM_CASE_LIST="BOMEX TWPICE"
#---SCM experiment name, please set to anything that is relevant
#---to your test
export SCM_EXPT_NAME="ref-oifs-scm-dp"
#---Path to the executable for the SCM. This is the
#---default path for the exe, produced by openifs-test.sh.
#---DP means double precision. To run single precision change
#---DP to SP
export SCM_EXEC="${OIFS_HOME}/build/bin/MASTER_scm.DP"
#---Default assumed paths, only change if you know what you are doing
export SCM_TEST="${OIFS_HOME}/scripts/scm"
export SCM_RUNDIR="${OIFS_EXPT}/scm_openifs/48r1/scm-projects/ref48r1"
export SCM_PROJDIR="${OIFS_EXPT}/scm_openifs/48r1/scm-projects"
export SCM_VERSIONDIR="${OIFS_EXPT}/scm_openifs/48r1" |
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, and that wget utility is available for convenient download:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd $OIFS_EXPT
wget https://sites.ecmwf.int/openifs/openifs-data/scm/48r1/scm_openifs_48r1.1.tar.gz
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 |