My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_15-4_EvaluationOfUSBRModelHYDROSS
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_15-4_EvaluationOfUSBRModelHYDROSS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/26/2011 8:32:33 AM
Creation date
7/11/2008 9:51:46 AM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.15-4 - Water Rights Planning Model - Evaluation of U.S. Bureau or Reclamation Model HYDROSS
Description
The purpose of this memorandum is to generally describe the computer model HYDROSS and to address its suitability for incorporation into the CRDSS.
Decision Support - Doc Type
Task Memorandum
Date
5/10/1994
DSS Category
Surface Water
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
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
stream flow data, adjusted for historic diversions, return flows, and storage. The USBR has <br />developed a virgin flow database which apparently is based on estimates of irrigated acreage and <br />evapotranspiration (ET). The ET varies by month and year to simulate a time series history. <br />Although the model involves a somewhat broad-scale analysis, it may be of use in the development <br />of the CRDSS. It would however require additional effort by the CRDSS Project Team to review <br />this existing virgin flow data set and make the modifications that may be necessary for the CRDSS <br />applications. <br />Once the pristine natural flow data are determined, HYDROSS begins the process of allocating water <br />to the water rights in a strict sequential order of priority. The operations also proceed in a strict time <br />sequence (the results from one month depend on the state of the river system at the end of the <br />preceding month) and are cognizant of the spatial relationships in the system network (the results at <br />one node are dependent upon what is occurring at other upstream and downstream nodes). <br />HYDROSS attempts to meet demands for water for: (a) instream flow requirements; (b) power <br />requirements; (c) diversions; and (d) storage. <br />HYDROSS recognizes a difference between "natural flow" (that which would occur absent any man- <br />related activity) and "project flow" (water that has been stored or otherwise appropriated as project <br />water). The distinction is made between natural and project flows because originally the model was <br />developed to assess water resources implications related to federal projects. Water rights decreed to <br />divert natural flow are allowed to divert water subject to a number of constraints and limitations <br />including consumptive demand, headgate capacity, etc. Diversions are also limited to the <br />availability of supply after senior water rights in the network are satisfied. Project water rights <br />generally operate by priority among themselves and typically do not divert natural flows until all <br />natural water rights are satisfied. Project water cannot be withdrawn under a natural water right. In <br />the CRDSS applications, most of the water rights would be considered as natural water rights, <br />including those rights owned by the federal government (e.g., the Aspinall Unit water rights) since <br />they do carry their own decreed priorities. <br />HYDROSS does not specifically allow the assignment of a priority date to a reservoir for storage. <br />Storage is apparently automatically assigned the lowest priority available, which in effect will allow <br />storage of all remaining water not used in the basin. However, reservoirs with decreed priority dates <br />can be modeled by using a diversion to deliver the water to the reservoir (the model treats a decreed <br />reservoir as off stream and supplied via a feeder ditch). <br />In the operation of HYDROSS, there are three basic components of operation to consider at each <br />node. <br />Inflow . This consists of: (a) the available flow from upstream nodes; (b) return flows from <br />upstream diversions that are occurring within the current month (including lagged returns from prior <br />months); (c) the incremental pristine gain (loss) to the river between nodes; and (d) a category for <br />"other gains" which is a means for forcing water into the network, if desirable. <br />Station Action . This represents the actions at a node (station) once the inflow is determined. These <br />actions include: (a) diversions, taking into account the demands of more senior priorities at <br />downstream nodes; (b) evaporation (if there is a reservoir at the node); (c) change in storage content <br />(if there is a reservoir); (d) a component for "other losses," a specialized form of diversion; (e) an <br />allowance for an in-stream flow bypass, if applicable; and (f) an inflow-outflow calculation to <br />determine the "available flow" remaining after all other demands at the node are satisfied. <br />2 <br />A275 05.10.94 1.15-4 Fosha, Hyre <br />
The URL can be used to link to this page
Your browser does not support the video tag.