Skip to content

Hspf_cbp_rundata

Jump to bottom
rburghol edited this page Feb 11, 2022 · 8 revisions

Model Configuration Files

  • Create Control files - these are the master list of files for model input

    • River - config/control/river/[scenario].con
    • Land - config/control/land/[scenario].con
    • Note: a -.con file contains a number of references to config file name paths and may mix and match “parameter sets” (paramset), for example, the p532sova scenario uses the p532cal files for hydrologic and water quality parameters, but uses it’s own files for land cover and land use area

  • Create Directories for runtime data

    • Land: run/standard/make_land_directories.csh
    • River: run/standard/make_river_directories.csh

  • Runtime Segment Lists: these are for running the model, once created they are available for all scenarios

    • River - config/seglists/[segment group name].riv
    • Land - config/seglists/[segment group name].land

  • Hydrology files

    • One file per Scenario, HSPF PWATER Module and land use:
      • General: input/param/[luname]/[paramset]/[hspf-module].csv
      • Ex: input/param/pas/p532cal/PWATER.csv
    • Pervious Landuses Modules/Files used:
      • ATEMP.csv PWATER.csv MSTLAY.csv PQUAL1.csv PQUAL2.csv PQUAL3.csv PQUAL4.csv PQUAL5.csv PWTGAS.csv PQUAL6.csv SEDMNT.csv PSTEMP.csv SNOW.csv
    • Impervious Landuse Modules/Files used:
      • ATEMP.csv IQUAL1.csv IQUAL2.csv IQUAL3.csv IQUAL4.csv IQUAL5.csv IQUAL6.csv IWATER.csv IWTGAS.csv SNOW.csv SOLIDS.csv
    • Notes:
      • Southern Rivers seem to have been carried forward into this version of the model for basic PWATER (not so for cover, see below)
      • What else might be missing? Use “fgrep 51167” (Russell County) in param directories and if it shows up then southern rivers are there. If not, generate base from Bedford (or some other).

land control files

  • Example: config/control/land/p532sova_2021.con
  • Climate Files
    • ./input/scenario/climate/met/[met scenario name]/met_B42027.wdm
    • ./input/scenario/climate/met/fjs8405xyz/met_B42027.wdm
    • Set this in the control files for land and river. i.e.:
METEOROLOGY
fjs8405xyz
END METEOROLOGY
  • All blocks in .con file
    • CROP COVER
    • DETS
    • TOTAL FERTILIZER
    • MANURE
    • LEGUME
    • TOTAL UPTAKE
    • MONTHLY FRACTION UPTAKE
    • PRECIP ATMOS DEPOSITION
    • METEOROLOGY
    • PARAMETERS
    • IOVARS
    • GEOMETRY
    • PER MODULES(PQUAL)
    • PER MODULES (AGCHEM)
    • PER MODULES (NITR)
    • CALIBSCEN
  • Atmospheric Depositions Files
    • some are created with met scripts
    • /opt/model/p53/p532c-sova/input/scenario/climate/prad/f611nsA902/prad_A42099.wdm
PRECIP ATMOS DEPOSITION
f611nsA902
END PRECIP ATMOS DEPOSITION

river control files

  • Example: config/control/land/p532sova_2021.con

  • Sections:

    • LAND SCENARIO - this tells us were the runoff comes from, so, theoretically, run_river could use a different land scenario?
      • LAND SCENARIO
      • LU <-file--->***
      • all p532sova_2021
      • END LAND SCENARIO

  • Land Use Areas:

    • In river simulation (land use is all simulated as 1.0 acres in land simulation)
    • Config file in config/control/river tells which file names to look for, in block “LAND USE”
      • Ex (current VA+southern rivers model): config/control/river/p53sova.con & config/control/river/p532cal_062211.con
      • 1985CALIBN040611 === file named “land_use_1985CALIBN040611.csv”
    • Land Use CSV located in “input/scenario/river/land_use/landuse_[timeperiod-paramset]”
      • Keyed by “Land Segment, River Segment” Identifier
      • CSV riverseg,landseg,lu1,lu2,lu3,...
      • Ex:
        Riverseg,landseg,for,hvf,hwm,nhi,lwm,nlo,hom, ...
        JU2_7140_7330,A51005,38637.5,390.28,28.32,0,85.055,0,29.37 ...
      • Ex (current VA+southern rivers model): input/scenario/river/land_use/land_use_p53cal_1985.csv
      • Ex (Phase 5.3.2 p53cal data set):
        input/scenario/river/land_use/land_use_1985CALIBN040611.csv

  • Land hydrology factors

    • Keyed by scenario (ex: p532cal)
    • Parameter group named “PWAT” in hspf
      • All PWAT params in a single CSV per land use: input/param/alf/p532cal/PWATER.csv
      • PWAT groups (tables):
        • PWAT-PARM1 - flags to enable blocks
        • PWAT-PARM2 - infiltration and surface parameters
        • PWAT-PARM3 - ET and losses to deep aquifers
        • PWAT-PARM4 - interflow, surface storage and interception
        • MON-INTERCEP - interception by surface vegetation/canopy
        • MON-UZSN - monthly upper zone storage
        • MON-LZETPARM - monthly varying lower zone et coefficients
        • PWAT-STATE1 - initial state variables
        • MON-MANNING - monthly varying roughness coefficients
Clone this wiki locally