...

#---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"
export SCM_LOGFILE="${SCM_RUNDIR}/scm_run_log.txt"

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.

...

Once the above has been completed, it is necessary to select which test-case you are ready to run . There is a choice of the following 3 testcasesthe SCM. The scm_openifs  contains 3 testcases, each representative of different cloudy regimes

• DYCOMS - marine stratocumulus case
• BOMEX - trade-wind cumulus case 
• TWPICE - A multi-day deep convective case

The case can be SCM is run using the callscm script, which is a wrapper for the main run.scm. Both scripts can found in $SCM_TEST , which is set in the oifs-config.edit_me.sh, using SCM_CASE_LIST  file to ${OIFS_HOME}/scripts/scm . 

callscm  includes default settings, which are the all cases, with a 450 s timestep and an experiment name of ref-oifs-scm . To run with these settings, enter the following

SCM_CASE_LIST="BOMEX TWPICE DYCOMS"

The above will run all the cases. If making this change in oifs-config.edit_me.sh, remember to source the file once the change has been made.

cd $OIFS_HOME
$SCM_TEST/callscm

This will run the DYCOMS case with the SCM and create an output directory in $SCM_RUNDIR/scmout_DYCOMS_ref-oifs-scm_450s , which contains the diagnostic output from the SCM. In addition, the file scm_run_log.txt will be created in $SCM_RUNDIR . This file contains the print output from the SCM, which is useful for checking all the sources and paths for a simulation. 

A user can change the defaults by using the available command-line optionsOnce the cases are set, then do the following to run the SCM

cd $OIFS_HOME
$SCM_TEST/callscm

The callscm  script is a wrapper for the main run.scm. Both scripts can found in $SCM_TEST , which is set in the oifs-config.edit_me.sh file to ${OIFS_HOME}/scripts/scm . At present, callscm  needs the following  

...

callscm -h -c <case_name or list of case_names> -t <timestep or list of timesteps>
        -x <expt_name>
where :
-h is help which returns basic usage options and exits
-c case_name or list of case_names (space delimited) of the case study
   used for namelist and output directory. Default list is
   "DYCOMS BOMEX TWPICE" 
-t timestep or list of timesteps in seconds. The default is 450s. An
   example of a list is "1800 900 300" 
-x expt_name shortname to identify experiment. Default is ref-oifs-scm

 For example, if a user wanted to run the BOMEX case with timesteps of 1800 s and 900 s and an experiment name of "bomex_test", they would enter the following

$SCM_TEST/callscm -c BOMEX -t "1800 900" -x "bomex_test"

This command results in the following output directories 

scmout_BOMEX_bomex_test_900s
scmout_BOMEX_bomex_test_1800s

Example plotting script

Once the SCM has successfully, it will produce output in $SCM_RUNDIR