deploy a realtime run in Jet

An example on deploying a new version of rrfs for Jet Realtime run

0. A few tips for maintaining the Jet real-time runs:

• Each time deploying a new version, the workflow will automatically set a two-month period, no need to manually set the run period. However, it is always a good idea to check the rrfs.xml file before resuming the real-time runs.
• If we need to extend the rrfs.xml run period, one can change the Y1/M1/D1/Y2/M2/D1 variables.
• If it is in Dec, one needs to change &M1;-&M2; to &M1;,&M2; in order to pass from one year to another year.

Examples:

<!ENTITY Y1 "2024">
<!ENTITY M1 "12">
<!ENTITY D1 "26">
<!ENTITY H1 "00">

<!ENTITY Y2 "2025">
<!ENTITY M2 "01">
<!ENTITY D2 "31">
<!ENTITY H2 "00">
...
<cycledef group="spin-up"> 00 03-08,15-20 * &M1;,&M2; &Y1;-&Y2; *</cycledef>

1. Clone and build

replace 2.0.1 with an appropriate version number

cd /lfs5/BMC/nrtrr/RRFS
git clone -b rrfs-mpas-jedi --recursive [email protected]:NOAA-EMC/rrfs-workflow 2.0.1
cd 2.0.1/sorc
./build.all

2. Setup the experiment and generate the rocoto XML file

crontab -e # comment out the old version of the rrfs realtime run
cd 2.0.1/workflow
cp exp/exp.jet_conus3km exp.setup 
# Modify exp.setup, set variables, such as VERSION, etc as needed.
./setup_rocoto.py
crontab -e # make sure the new version of the rrfs realtime run is active in the crontab

3. Go to the expdir to make sure everything works correctly

cd /home/role.rtrr/RRFS/2.0.1/conus3km
./run_rocoto.sh
rstat

Sometimes, manually rocoto_boot a cycle may be beneficial. For example, a new version is deployed at 03z. 03z will need lbc from 00z. So one can run the following command to reboot the lbc task at 00z so that 03z cycle can start soon.

rboot 202407190000 lbc

where rboot is a quick command provided by the qrocoto tool.
Check this instuction on how to quickly set up and use the qrocoto tool.