My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SPDSS_WatRightScope4_20060712
CWCB
>
Decision Support Systems
>
DayForward
>
SPDSS_WatRightScope4_20060712
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/26/2011 8:30:16 AM
Creation date
7/17/2008 10:43:57 AM
Metadata
Fields
Template:
Decision Support Systems
Title
SPDSS Phase 4 - Relational System Integration and Water Rights Administration Component
Description
The Scope of Work for the Relational System Integration and Water Rights Administration components of the South Platte Decision Support System; Phase 4.
Decision Support - Doc Type
Scope of Work
Date
7/12/2006
DSS Category
Surface Water
DSS
South Platte
Basin
South Platte
Contract/PO #
C153966
Bill Number
SB01-157, HB02-1152, SB03-110, HB04-1221, SB05-084, HB06-1313, SB07-122
Prepared By
CWCB
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
31
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
r ~ <br />HydroBase changes. Once the formal tests are established, they can help ensure a <br />working system and can help new developers better evaluate impacts of their <br />work. <br />140.5 Add features to support HydroBase database queries from the StateCU GUI. <br />TSTooI will be enhanced to support queries from the StateCU GUI (see also the <br />StateDMI Task 141 discussion), as follows. Performance issues will be evaluated <br />in the StateDMI task. <br />1. The readHydroBase () command will be updated to allow reading of <br />monthly and daily (as available in HydroBase) precipitation, temperature, <br />wind, and evaporation time series, allowing Where criteria to be specified for <br />division and district. Also add a parameter to indicate that time series data <br />values should NOT be read, resulting only in header information being read. <br />This command was previously implemented to support structure time series <br />queries, including diversion records. <br />2. Add a new writeTimeSeriesToList () command (or similar), which <br />will write the time series header information to a delimited list file. Output <br />will include the station identifier, data type, period of record, etc. This output <br />will be read by the StateCU GUI to provide users with lists of time series. <br />140.6 Ensemble data processing for StateMod modeling. TSTooI will be updated to <br />process data to allow StateMod to be run in ensemble fashion, where multiple <br />runs are made with a variety of inputs determined by shifting input time series <br />into new combinations. The following activities will occur: <br />1. Participate in conference calls and help document the approach for ensemble <br />modeling, in particular to support the Aspinall EIS effort. <br />2. Add a new TSTooI command (or modify an existing command) to read a <br />delimited file containing lists of years to indicate the sequence of years for <br />processed time series, and then resequence the years. Parameters will be <br />implemented to handle leap year processing, to facilitate exchange of data <br />with RiverWare. The command will be designed to allow additional <br />enhancements in the future (e.g., to allow sequences of years/months to be <br />specified, with or without a spatial designation). The command will be tested <br />with daily and monthly streamflow time series. <br />3. Test running StateMod from TSTooI using the runProgram () command, a <br />batch file, or other approach, in order to automate running StateMod many <br />times with the various inputs. The enhancement described above will be <br />applied to StateMod monthly and daily data for as many sequences are <br />defined. Each run will be saved in a separate folder, to allow inspection of <br />input and results. A sample commands file will be provided to the State and <br />may need refinement for production use. <br />4. An example commands file will be created to extract input and results from <br />each simulation at a single point, resulting in an ensemble of time series traces <br />(one ensemble for input streamflow, one for simulated streamflow). Each <br />trace will be identified with a scenario and/or sequence number, features that <br />15 <br />
The URL can be used to link to this page
Your browser does not support the video tag.