Do Chemistry

Most steps follow the same instructions as regular rrfs-workflow with some steps have some special options or configurations.

1. Build

which git-lfs 2>/dev/null ||  module load git-lfs
GIT_LFS_SKIP_SMUDGE=1 git clone -b rrfs-mpas-jedi --recursive https://github.com/NOAA-EMC/rrfs-workflow
cd rrfs-workflow/sorc
./build.all chem noda

NOTE: If doing chemistry data assimilation, one needs to build as ./build.all chem

2. Setup and run experiments:

Example:

cd workflow
cp exp/exp.conus12km exp.conus12km
vi exp.conus12km # set DO_CHEMISTRY=true; modify EXP_NAME, OPSROOT, RETRO_PERIOD and others as needed.
vi config_resources/config.chemistry # double check chemistry related variables are set correctly
./setup_rocotpy.py exp.conus12km

NOTE:

1. DO_IODA,DO_JEDI,DO_CYC are true by default in exp files, but overrode to false in config_resources/config.chemistry. If doing chemistry DA, one needs to change them back to true in config.chemistry.
2. If one wants to modify CYC_INTERVAL, CYCLEDEF_IC_STEP_HRS, LBC_CYCS, COLDSTART_CYCS, FCST_LEN_HRS_CYCLES, LBC_LENGTH, they should be modified in config_resources/config.chemistry. This strategy is to ensure we have a working chemistry workflow out-of-the-box with minimum changes.

The other steps are the same as running regular RRFS experiments documented here

3. Under the hood

3.1 The RAVE_dummy file

When RAVE emission file is not available, rrfs-workflow will use a RAVE_dummy file from ${COMINrrfs}/RAVE_dummy.nc; if the dummy file is not available, the workflow will stop with an error.

One can link an existing one from other staged area or create a new one using the utility workflow/ush/chem_create_rave_dummy.sh
Usually, each different mesh has a corresponding RAVE_dummy file and it may be found at ${CHME_INPUT}/emissions/RAVE/processed/RAVE.dummy.${MESH_NAME}.nc.

3.2