Skip to content

pubsheds: Full Scenario with PRISM data #147

@rburghol

Description

@rburghol

Steps:

New All in One with met2river (see details here)

  • Edit config/control/met/met2date.con to have the correct years for grib update forcing (if any)
  • Edit config/control/met/PRISM.con to insure that dates for met2date and PRISM are overlapping.
  • Run all from met2date update thru river (for basin RU): ./srun_met2river pubsheds RU 1 0 0
  • Run just the met2date update and WDM (no land and river): ./srun_met2river pubsheds allP6 1 0 0

Do met2date

  • This is necessary to provide non-precip met inputs from legacy CBP routines
    • Note: This from 12/15/2025 when we re-generated 2022-2024 because NLDAS2 had data corrections from 2022-2025
basin=allP6
scenario=pubsheds
lsegs=`cbp get_landsegs $basin`
met_scenario=`cbp get_config $scenario land "PRECIP ATMOS DEPOSITION"`
for i in $lsegs; do
  job_name=`cbp mm_job_name met2date $i`
  sbatch  --job-name="$job_name" $NLDAS_ROOT/make_met2date $i 19840101 20250531 "2022 2023 2024 2025" landseg
done

Generate the full met wdms using a custom PRISM precip

  • Generate land wdm for all with PRISM as precip
basin=allP6
scenario=pubsheds
met_scenario=`cbp get_config $scenario land "PRECIP ATMOS DEPOSITION"`

cd /opt/model/p6/vadeq
. hspf_config
# set needed environment vars
MODEL_ROOT=/backup/meteorology/
SCRIPT_DIR=/opt/model/model_meteorology/sh
export MODEL_ROOT SCRIPT_DIR

land_segs=`cbp get_landsegs $basin`
model=hspf_cbp6

# run WDM import
for i in $land_segs; do
  job_name="${i}_wdm"
  djid=`cbp mm_job_id ${met_scenario}_${i}`
  deps=""
  if [ "$djid" != "" ]; then
     deps="--dependency=$djid"
  fi
  echo "sbatch --job-name="$job_name" $deps run_model raster_met $met_scenario $i auto wdm "
  sbatch --job-name="$job_name" $deps run_model raster_met $met_scenario $i auto wdm 
done

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions