Workflow: `om` model -- model run metrics, and OM functions (need to separate the log file retrieval from the analysis in the old OM functions)

[rburghol]

Tasks

• run_shaketree.php caller (set RUN_METHOD = shake_tree)
• run_model (set RUN_METHOD = run_model) run_model caller #120
• replace shaketree with slurm + run_model
  • Use .out file date for cache time check -- see raster workflow alt for example
  • How to insure that sub-watersheds are run inside parent?
    • Inititial workflow should grab the custom1/custom2 and skip if segment is type cova_subshed, since it will be run by the parent in either shaketree or regular run mode.4
  • Can use existing segments lists in cbp tree?
  • is it ok to call the run on a contained subshed, which returns rapidly anyhow without running? Or better yet, load the cache property in the run work step
• om -> usgs module for area-weighted gages  #128
• Create land module
  • use scripts/om/clone_runoff_data #113 to clone from model baseline scenario if out of date or FORCE_RO_UPDATE=1
• Create facility module, with copy from template, and steps for each in the VWP model setup workflow

Workflow Modules and Steps

• river
  • run:
    • 01_run_shaketree: until we have a slurm implementation, we can use this.
      • config/control/[scenario].con -> RUN_METHOD = shake_tree
    • 01_run_model: this is the future (and the past). See run_model caller #120
      • config/control/[scenario].con -> RUN_METHOD = run_model
  • analysis: model run metrics, and OM functions (need to separate the log file retrieval from the analysis in the old OM functions)
    • Use: /opt/model/meta_model/run_model om [scenarioid] [riverseg] auto [module] [submodule] [step]
    • Ex: /opt/model/meta_model/run_model om 11 PL2_4970_5250 auto river analyze 05
    • 01_summarize_children
    • 02_summarize_river
    • 03_summarize_cached_children
    • 05_water_availability https://github.com/HARPgroup/meta_model/blob/main/models/om/river/analyze/05_water_availability
• land
  • prep
    • 01_copy_baseline - optional
    • 02_run_runoff
      • get runoff container by riverseg/custom2, and send to run_model with cache checking
      • does the run_model.php check cache and return?
• usgs
• facility
  • prep
    • 01_create_model - optional
    • 02_local_impoundment
    • 03_parent_impoundment
    • 04_ps_advanced
    • 05_impoundment_control
• manage
  • migrate migrate data from dh to om by model elementid
    • Use: run_model om 401 351476 auto manage migrate
    • 01_dh_to_om - runs the migration script (TBD spit this into an 01_export_dh_json and 02_json_to_om)

Examples

Banister River SOVA

• sudo -u www-data run_model om 17 OD3_8520_8621 auto river run 01_run_shaketree
• sudo -u www-data run_model om 17 TU0_0000_0000 auto river run 01_run_shaketree