Skip to content

End to End Run

Jump to bottom
Manabendra Saharia edited this page Jun 1, 2018 · 45 revisions

source activate ff for flood frequency conda environment

Prepare FUSE

  • Compile SCE: ifort -O2 -c -fixed sce_16plus.f
  • mkdir bin
  • make

Forcing generation

  • Create a mapping file
    • Go to /d3/msaharia/ffreq/forcinggeneration in Hydro-c1 server
    • python2.7 poly2poly/poly2poly.py /d3/msaharia/ffreq/forcinggeneration/pilot_basin_data/IslandPark_WatershedDelineation.gpkg Id PNW/PNW_elev_0625_poly2.gpkg id GRID map.nc
  • Create a time series file using this mapping file
    • Go to /d3/msaharia/ffreq/forcinggeneration
    • python2.7 poly2poly.map_timeseries.py ../islandpark.nc /d3/hydrofcst/overtheloop/data/forcing/retro/forc_nc/PNW/ens_forc.PNW.0625.1980-1989.051.nc ../testme.nc
  • Create time series polygon files for all 100 ensembles: /d3/msaharia/ffreq/aasi/hydrometEnsGen.py

Forcing manipulation

  • Move time series data created above to Cheyenne: scp -r /d3/msaharia/ffreq/forcinggeneration/islandpark/* manab@cheyenne.ucar.edu:/glade/p/work/manab/ff/islandpark/rawinput/
  • Concatenates by time for each ensemble, inserts PET in each ensemble, and writes out final input files: /d3/msaharia/ffreq/aasi/convert4fuse.ipynb

Elevation bands

  • Temporarily use this: https://github.com/msaharia/aasi/blob/master/temporaryCopyElevBanFile.py
  • Use real elevation bands provided by USBR here: /glade/p/work/manab/ff/islandpark/ip_elev_bands_usbr.nc

Running FUSE

  • ./bin/fuse.exe /glade/p/work/manab/ff/islandpark/fm_902_us.txt islandpark 123 run_def
    • 2nd CLI arg: dom_id. This dictates which input_info file it looks for inside /settings/. For example, this will look for islandpark_input_info.txt
    • 3rd CLI arg: FMODEL_ID. This dictates what decision file FUSE looks for. i.e. /glade/p/work/manab/ff/islandpark/settings/fuse_zDecisions_123.txt
  • Things I will need templates for automated runs:
    • Main config file with TIME insertions
    • Creating x_input_info.txt in settings file with forcing file name insertion and filename change
  • Works: ./bin/fuse.exe /glade/p/work/manab/ff/islandpark/fm_template.txt islandpark 001 run_def
  • Run 100 ensembles using: and then https://github.com/msaharia/aasi/blob/master/cheyenneJobs.ipynb
  • ./submitalljobs.sh (for now)

Calibration

  • Moved namelists to setup
  • Change /glade/p/work/manab/ff/islandpark/settings/namelist.fuse_calib_control. Replace by KGE, NSE, RMSE
  • /glade/p/work/manab/ff/newfuse/fuse/bin/fuse.exe /glade/p/work/manab/ff/islandpark/fm_prms.txt 001 xyx calib_sce (For 1 ensemble)
  • Here xyx = 111(prms), 222(hechms), 333(vic), 444(sacsma). Different decision files have been created.
  • /glade/p/work/manab/ff/islandpark/pbscalib.sh - Calibrates for 1 ensemble for 3 metrics - KGE, RMSE

Notes

  • Convoluted mess
  • Here, 123 dictates what decision file FUSE looks for. i.e. /glade/p/work/manab/ff/islandpark/settings/fuse_zDecisions_003.txt. I think it just ignores the 'fuse_zDecisions_902.txt' ! M_DECISIONS = definition of model decisions in the main config file
  • The new setup from Andy Newman is kept in fusenew

Milestones

  • 100 flow ensembles (1970-2016) ready with all necessary concatenation and files
  • Baseline uncalibrated and calibrated model output completed for 1 ensemble

To-do

  • Automated Elevation data insertion.
  • Automated script for creating and submitting FUSE Cheyenne jobs
  • Double check all units
  • Put all negative PET to zero in the input preparation script
Clone this wiki locally