File ReadMe_smallBonny_CO_CREP_model_backup.txt Jun 30, 2016 spp

Model runs: case names (suffixes for files, e.g. [case].nam) and descriptions. Additional details are in the pseudo-batch file named
run_cocrep_2000-2015_model_backup.txt.

Baseline:
For compliance accounting, groundwater CBCU for CO and KS were the values posted on the RRCA website for years 2000-2011,
but were given for the Small Bonny, historical pumping case that follows for years 2012-2015.

Small Bonny, historical pumping scenario:
2000-2015_sb				Base run – small Bonny with historical pumping for all years 2000-2015
2000-2015a_sb				No CO pumping and no MOUND imports for the above case [impacts: 2000-2015a_sb.htm]
2000-2015b_sb				No KS pumping and no MOUND imports for the above case [impacts: 2000-2015b_sb.htm]

Small Bonny, existing CREP scenario
2000-2015_sb_cocrep			Base run – Small Bonny all years; KS and NE historical pumping; CO pumping given by CO existing CREP files (in CO backup folder no)
2000-2015a_sb_cocrep		No CO pumping and no MOUND imports for the above case [impacts: 2000-2015a_sb_cocrep.htm]
2000-2015b_sb_cocrep		No KS pumping and no MOUND imports for the above case [impacts: 2000-2015b_sb_cocrep.htm]

Small Bonny, enhanced CREP scenario:
2000-2015_sb_sfcrep			Base run – Small Bonny all years; KS and NE historical pumping; CO pumping given by CO enhanced CREP files (in CO backup folder sf)
2000-2015a_sb_sfcrep		No CO pumping and no MOUND imports for the above case [impacts: 2000-2015a_sb_sfcrep.htm]
2000-2015b_sb_sfcrep		No KS pumping and no MOUND imports for the above case [impacts: 2000-2015b_sb_sfcrep.htm]

Summary of input data for model runs

Pumping and recharge files for all model runs were generated by rrppv8, a modified version of rrpp. Input parameter files reference historical
pumping and recharge files as posted by RRCA in ..\data folders co, ks and ne. For CREP cases, input parameter files reference Colorado pumping
and recharge files in Colorado CREP model backup (existing CREP: no; enhanced CREP: sf). The CO CREP backup files, for years 2016-2031, were
renamed to corresponding years 2000-2015 (using commands in rename_co_files.txt), and are in folders cocrep and sf.

Stream: file 2000-2015_sb.str, used in all model runs, was generated by mkstr2_smallBonny.pl, a modified version of RRCA perl script mkstr2.
The script mkstr2_smallBonny.pl sets conductance for Bonny (segment 150) equal to 8.873 ft^2/s in one reach, based on an assumed forebay
elevation of 3640 ft and lake surface area of 176 acres. The conductance is set in file data0\12s3_sb.str, a modified version of stream skeleton
file 12s3.str; lake elevations were read from data\sb\reservoir.dbf. 2 cfs seepage below Bonny (segment 176) was read from data/flow.dbf.
CCP augmentation flows (segment 122) were inadvertently left out when 2000-2015_sb.str was built, but this doesn't affect South Fork impacts. 
# STR:     perl bin/mkstr2_smallBonny.pl 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 > 2000-2015_sb.str

Evapotranspiration: File ref.evt, from the CO backup files for CREP scenarios, was used for the base and CO impact cases for all three scenarios.
File 2000-2015.evt, generated by mket.pl (modified to run on Windows), was used for the KS impact case for all three scenarios:
# EVT:     perl bin/mket.pl 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 > 2000-2015.evt

Initial heads for year 2000 were specified by computed heads at the end of 1999. Computed heads were read by Program readheads from output files
for 1918-2000 simulations for the base case 12p and for Colorado and Kansas impact cases 12p14 and 12p2, and written to files
2000.shead (all stresses ON), 2000ad.shead (CO pumping and MOUND OFF) and 2000b.shead (KS pumping OFF);
file 2000ad.shead was then renamed as 2000a.shead.

Pumping impacts were calculated using the multiyear version of the acct program, acctyrs, which was provided by Willem.
Mound imports are included for the base case and the Kansas impact case, but not for the Colorado impact case. This inconsistency
does not affect South Fork impacts, but should be resolved for evaluating impacts in all subbasins according to the 5-run convention.