Laserfiche WebLink
<br />001984 <br /> <br />Slot <br /> <br />A slot is simply a named location within any object that holds data. A slot <br />may be configured as a single value, a table or a time series. <br /> <br />Link <br /> <br />A link enables slots within objects to be tied together. For example a Reach <br />object will have an inflow and outflow slot (among others). The outflow slot <br />of an upstream Reach is linked to the inflow slot of a downstream reach. <br /> <br />Preprocessors <br /> <br />A computer program ("PreProcessor") was developed that calculated depletion requests and diversion <br />requests by RiverWare depletion objects or nodes. A RiverWare depletion node consists of any <br />combination of exports, irrigation diversions, and non-irrigation diversions at a given point in the <br />watershed. All depletion categories were mapped to specific RiverWare nodes using a database <br />system discussed in the following paragraphs. The database. node mapping and pre-processor system <br />result in computed depletions equivalent to those used in the natural flow analysis. <br /> <br />It should be noted that a primary purpose of the pre-processor was to compute depletion request and <br />diversion request by non-irrigation water users. These data only exits as depletions by HUC <br />(Colorado) or unit (New Mexico). A HUC is a hydrologic unit code established by the USGS. A <br />unit is a subunit of a HUC established for computation of depletions from a geographic area. Since <br />this depletion data is tabulated based on geographical area instead of water user, a tool was need to <br />proportion the water use data to individual RiverWare nodes. The pre-processor proportions the <br />HUC and unit data to appropriate RiverWare nodes. RiverWare nodes may include single water <br />users or aggregates of many water users. <br /> <br />Originally, the pre-preprocessor computed irrigation depletion and diversion requests. Later versions <br />of RiverWare computed these requests internally. However, the pre-processor was needed to <br />accumulate acres and compute weighted evapotranspiration rates. Further details of the Preprocessor <br />may be found in Chapter 4 of this document. <br /> <br />Post-processing <br /> <br />The SJRIP Hydrology Model currently runs on a monthly time step with flows in ac-ftImonth or the <br />monthly equivalent cfs as output. In order to assess the effect of the various flow conditions on <br />fisheries habitat, daily flows are necessary at the key habitat locations. These flows are typically <br />evaluated at the Four Comers gage. The Model output is disaggregated from monthly flows into <br />daily flows in a combination of BASIC programs and Excel spreadsheets. Within the spreadsheets a <br />daily volume balance is completed for the mainstem of the San Juan between Navajo Reservoir and <br />Bluff. To insure that the daily volume balance is correct, the daily flows are summed back to <br />monthly flows and compared against the model monthly flows at the San Juan gage locations. <br />Further details of Post-Processing may be found in Chapter 7. <br /> <br />DRAFT - SJRIP Hydrology Model Documentation <br />June 18, 1999 <br /> <br />45 <br />