Adding a new model to real-time surface (METAR) verification (jet)

If adding new region(s), complete steps marked with New Region. Otherwise, those steps may be ignored.

• db - New Region: Update reg set in madis3.metars with new region name

• db - New Region: Update madis3/regions_per_model (seems this doesn’t need to happen for all models??)

  • New Region: Add new models with associated regions

  • New Region: Add region to any models that will be compared against

• db - New Region: Create new partials sums tables for region (where being added to existing models) in surface_sums2

• jet: update /misc/whome/role.amb-verif/ruc_madis_surface/surface_driver_q1.pl

  • add elsif clause with new model(s) & associated regions & fcst_lens

  • New Region: Add new region to other models as needed

• jet: update /misc/whome/role.amb-verif/ruc_madis_surface/get_iso_file3.pl

  • Add elsif clause for new model(s) ($data_source) with dir ($anal_dir) convention

  • Add elsif clause for new model(s) ($data_source) with filename ($base_file) convention

• jet: add crontab entry (can copy similar), like:

  20 0-9,11-23 * * * $HOME/sb.sh $HOME/ruc_madis_surface/surface_driver_q1.pl [model] -12 0 METAR  > /dev/null

• Run and check that tables created in db (madis3, surface_sums2)

• model-verif-prod or hera or jet Update MATS metadata:

  • run /home/amb-verif/mats_metadata/update_metadata_surface.py [model1],[model2],...,[modeln]

• (model-verif-prod) add cron jobs for updating table partitions, like:

  07 7 * * 0 $HOME/utilities/update_week_partition.pl [model]qp 30  > /dev/null
  07 7 * * 0 $HOME/utilities/update_week_partition.pl [model]qp1f 30  > /dev/null