My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_08-2_HistoricalDatabaseYear1Summary
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_08-2_HistoricalDatabaseYear1Summary
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:51 AM
Creation date
6/2/2008 9:19:47 AM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.08-2 - Historical Database - Year 1 Summary
Description
The purpose of this task memorandum is to document the historical database task activities performed during Year 1.
Decision Support - Doc Type
Task Memorandum
Date
1/9/1995
DSS Category
HydroBase
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.
/
6
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
Note that it is presently planned that work done during this phase will be used to plan work tasks for the <br />Phase IIb task, Policy and Water Rights Database. <br />4.A simple scenario management database that will support the prototype modeling activities. <br />This activity was coordinated with the modeling tasks and task 1.05. The objective of this task as part of <br />the prototype was simply to make sure that the proper files were available to all users of the CRDSS, that <br />original files were not corrupted, and that it would be possible to store different model runs on the <br />system. This was accomplished using features in the UNIX file system; INFORMIX was not used. <br />5.A task memorandum describing and summarizing Task 1.08 activities and results. <br />In addition to this task memorandum, additional documentation on the database and database activities <br />have been produced. These include a revised CRDSS Database Design Document , the CRDSS Users <br />Manual, and the CRDSS Developers? Manual. <br />Work Plan <br />There are subtasks in the work plan where some summary discussion is warranted. For some subtasks <br />deliverables were produced or substantial resources were spent. <br />Subtask 1. Install and Implement the Database <br />Early in Phase IIa, the INFORMIX software was installed. There were some minor delays and problems <br />because of the necessity to synchronize the supported versions of IRIX, NFS, and INFORMIX. Later, <br />there were some other problems with disk drive failures and some incompatibilities that hampered using <br />INFORMIX with raw disk. The failed drives were replaced under the respective drive warranties, and <br />some of these drives were returned to the State. The incompatibilities were resolved by the purchase of <br />three new 2-gigabyte IBM high performance disk drives. No data were lost due to the failures because <br />the development team maintained backups of the system on magnetic tape. However some time was lost <br />to replace the failed hardware and restore the file system from the tapes. <br />Database maintenance activities were performed under this subtask for Tasks 1.07, 1.08, 1.09, and 1.10. <br />Subtask 2. Review Historical Data and Populate the Database <br />The database was populated as discussed above. Quality control checks were implemented as <br />appropriate during population of the database. After population, the data were spot checked for <br />consistency with the original source. <br />Subtask 3. Fill Data Gaps Required by the Water Rights Planning and Consumptive Use Tasks <br />Part of this subtask was to inventory the data gaps found in the historical time series records. A <br />summary of this effort can be found in Appendix A, Inventory of Data Gaps for the Time Series Data. <br />Note that this inventory was done assuming that monthly statistics would be computed for a given data <br />set. The data were searched and summarized such that any month having any number of missing days <br />counted as a missing month. <br />4 <br />A275 01.09.95 1.08-2 Greer <br />
The URL can be used to link to this page
Your browser does not support the video tag.