My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task11-7_VerifyDiversionEstimates
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task11-7_VerifyDiversionEstimates
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/26/2011 8:31:55 AM
Creation date
7/10/2008 3:23:16 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 11.7 - Verify Diversion Estimates
Description
This memo describes the results of Subtask 11.7, Verify Diversion Estimates.
Decision Support - Doc Type
Task Memorandum
Date
11/1/1999
DSS Category
Surface Water
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153728
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Boyle
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
In the first step, actual data for explicit structures are pulled from Hydrobase and are written <br />to a temporary file (demandts.ddh), along with individual replacement time series for some <br />structures. To accomplish this step for this subtask, Boyle created a commands file based on <br />the Phase IIIa commands file for this step, ph2_ddh_commands, with two modifications: 1) <br />the final Phase IIIa structure (*.dds) file (rather than the preliminary structure file <br />demandts.dds created by watright) was input to demandts, and 2) the -fillmonave <br />instruction to fill missing data was removed. <br />In the second step, diversions for aggregated irrigation structures are estimated based on <br />crop water requirements and basin-wide efficiencies. To accomplish this step for this <br />subtask, Boyle created a commands file based on the Phase IIIa commands file for this step, <br />ddh_commands, except that 1) the Phase IIIa structure file was input, as in the previous step, <br />and 2) the data filling algorithm was then invoked to estimate ALL historical diversions for <br />explicit and aggregate structures based on actual data and local wetness conditions. <br />Specifically: <br />^ the demandts top-level command fillpattern(WDID, Gage ID) was used to assign <br />diversion structures to an indicator gage as described above. The wild card character in <br />the WDID field allows entire water districts to be assigned the same fill pattern (i.e. <br />fillpattern(29*,9342500)). <br />^ the --filldata filename command was added to pass the hydrologic characterization file to <br />demandts. <br />^ the --fillall command directs demandts to estimate all of the diversion data based on <br />wetness conditions. The wet, dry, and average year monthly averages calculated by <br />demandts are used to populate the final historical diversions (*.ddh) file. <br />^ the -rights option directs demandts to constrain the calculated average by the <br />structure's cumulative decreed amount, based on the decrees listed in the Phase IIIa <br />diversion rights file (*.ddr). <br />^ the fwadminnum 0.0 command directs demandts to treat any free water rights as if <br />their administration number was 0.0. This effectively removes the -rights constraint on <br />structures that have free water rights in the model, allowing them to divert more than <br />their water right if records indicate that was historical practice. <br />^ the -fillmonave directs demandts to use the average historical diversion, based on all <br />diversion values available for that month, if the sample size of historical diversions for a <br />given hydrologic condition is zero. <br />Execute Statemod <br />The San Juan and Yampa models were executed in baseflow generation mode using historical <br />diversions file containing estimated rather than recorded data. The Phase IIIa input files and <br />commands files for the San Juan model were used for this task. The "Task Order 1" commands <br />files and input files were used for the Yampa model. <br />The following should be noted regarding the San Juan model in Subtask 11.7: <br />Appendix E E_82 <br />
The URL can be used to link to this page
Your browser does not support the video tag.