My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC03595
CWCB
>
Water Supply Protection
>
Backfile
>
16000-16999
>
WSPC03595
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 11:35:38 AM
Creation date
10/9/2006 4:03:26 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Basin-Colorado River Computer Models-Colorado River Decision Support System
State
CO
Basin
Colorado Mainstem
Water Division
5
Date
9/30/1994
Author
Hydrosphere
Title
Hydrosphere Gunnison Model-Data Dictionary-Operations Code Overview-Model Solution Procedure and Sequence of Calls to Specific Procedures Flowcharts-Model Input Files-Gunnison Specific Computer Codes
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
35
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
<br />-> ' <br /> <br />....~ <br />1.11l1r3' 3 <br /> <br />Operatiuns Code Overview <br /> <br />ReportLoopConvergence [LOOPCONV.MOD] <br /> <br />This procedure was described above. It is used tu determine if an iteration loop needs to <br />be solved again or not. In this position is used to determine if the outer (return tlow) loop <br />needs to be iterated or not. <br /> <br />DoFinalSolutionStep [SOLUTION .MOD] <br /> <br />A tinal solution step may be required for either of two reasons. First, if there is a <br />Compact requirement for additional water from the Gunnison Basin, that requirement is met in <br />this version of the Planning Model by a special release from Blue Mesa Reservoir. Second, it <br />may be that either the inner or the outer iteration loop terminated (because the change was <br />within tolerance or because the iteration limit had been reached) after a moditication had been <br />made to the immediate return tlows or to operational releases. In this case the network would <br />be in an inconsistent state, where highs had been reduced helow the value currently stored in <br />the tlow parameter. If the network is in such an inconsistent state when the outer loop is <br />exited, the variable NeedToDistributeFlows in DoCram will cause a tlnal solution step to be <br />called. <br /> <br />DistributeReturnFlows [RTFLOW.MOD] <br /> <br />This is a CRAM library procedure to calculate and process return tlows which do not <br />return in the current model month. <br /> <br />DoEvapAccounting [ACCOUNTG .MOD] <br /> <br />This procedure does the necessary accounting of evaporation for Taylor Park and <br />Ridgway reservoirs. The evapuratiun accounting process differs signiticantly for the two <br />reservoirs. Taylor Park is relatively simple. because all water in the reservoir is divided into <br />three proprietary accounts. and the total physical evaporation from the reservoir can be <br />allocated directly among tbe three accounts in proportion to their end-of-month contents. <br />Ridgway is more complex because the proportionate allocation of total physical ~vaporation <br />extends to only four of the six accounts in the reservoir. These upper four accounts divide the <br />total physical evaporation in proportion to their respective contents, until they all are empty. <br />Thereafter, the Minimum Pool is charged for 100% of the evaporation until it is empty, and <br />then the Dead Storage Pool is charged for. 100% of evaporation. <br /> <br />CalcPower [POWER.MOD] <br /> <br />This is a CRAM library function to calculate the power generated by power plants <br />simulated in a network model. <br /> <br />OutputData [OUTPUT. MOD] <br /> <br />The is a CRAM lihrary function to write the results of the current month's simulation to <br />an output tile. <br /> <br />10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.