Something went wrong on our end
-
J.W. Smith authored
This might be useful if ever rerunning a full day of results following Met Office results. It has the basic dependencies that exist between EWS components. It's rudimentary, but beats manually waiting and watching for jobs to finish before starting the next component. A much better tool would be a workflow manager with some sort of 'backfill' or 'rerun' option...
J.W. Smith authoredThis might be useful if ever rerunning a full day of results following Met Office results. It has the basic dependencies that exist between EWS components. It's rudimentary, but beats manually waiting and watching for jobs to finish before starting the next component. A much better tool would be a workflow manager with some sort of 'backfill' or 'rerun' option...
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
catchup_day.sh 902 B
#/bin/bash
# A script that runs all of a day's wheat rust forecasts in order
# 1: depo
# 2: env
# 3: epi
# 4: advisory
echo "starting catchup"
config=$1 # /storage/app/EWS_prod/regions/EastAfrica/resources/coordinator/configs/config_EastAfrica_fc_live.json
date=$2 # 20221009
# depo
/storage/app/EWS_prod/code/coordinator/run_Processor.sh -p Deposition -c $config -s $date &
# Wait at least a minute so that logfile timestamps do not clash
sleep 70
# env
/storage/app/EWS_prod/code/coordinator/run_Processor.sh -p Environment -c $config -s $date &
# wait for depo and env to finish
wait
# epi
/storage/app/EWS_prod/code/coordinator/run_Processor.sh -p Epidemiology -c $config -s $date &
# Wait at least a minute so that logfile timestamps do not clash
sleep 70
# advisory
/storage/app/EWS_prod/code/coordinator/run_Processor.sh -p Advisory -c $config -s $date &
wait
echo "finished catchup"