My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SPDSS_Task62_Review IDSCU
CWCB
>
Decision Support Systems
>
DayForward
>
SPDSS_Task62_Review IDSCU
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/17/2013 9:36:03 AM
Creation date
5/27/2008 11:29:08 AM
Metadata
Fields
Template:
Decision Support Systems
Title
SPDSS Task 62 - Review IDSCU (formerly SPMAP)
Description
This memorandum provides a review of the IDSCU documentation and functionality.
Decision Support - Doc Type
Task Memorandum
Date
3/9/2005
DSS Category
Consumptive Use
DSS
South Platte
Basin
South Platte
Contract/PO #
C153954
Grant Type
Non-Reimbursable
Bill Number
SB01-157, HB02-1152, SB03-110, HB04-1221, SB05-084, HB06-1313, SB07-122
Prepared By
Leonard Rice Engineering
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
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
- Weather data can be added directly from HydroBase, NCWCD, or CoAgMet and <br />edited by the user on the screen. This feature makes it easy to update an existing <br />file with new climate data. For CDSS, climate station data must be extended <br />using TSTooI. However, using TSTooI, missing data can also be filled whereas <br />IDSCU does not offer any filling methods. <br />- Diversion data can be added directly from HydroBase and edited by the user on <br />the screen. Diversions can be selected based on the "Source" and "Use" codes <br />contained in HydroBase. The GUI interprets the use codes for the user (i.e. <br />Source = 2 represents reservoir storage). For CDSS, diversion data must be <br />created using TSTooI. It is recommended that TSTooI continue to be used to <br />develop diversions under CDSS as it improves the potential for gaining a clear <br />understanding of the diversion coding and associated data. <br />Multiple ET methods can be run at the same time (e.g. Blaney-Griddle and ASCE <br />Standardized Penman) for the same modeling area (location). The results from two <br />different ET methods can be directly compared on a yearly, monthly, or annual basis. <br />Note that a similar feature will be added to StateCU under the SPDSS Phase 3 <br />StateCU Enhancements with the simplified report generator (see Recommendations <br />below). <br />A comprehensive water budget report generator allows the user to select components <br />of the results and allows the user to view these results in several different formats <br />(e.g. daily/monthly/annually and on a unit basis or for the acreage specified in the <br />input file). Note that a similar feature will be added to StateCU under the SPDSS <br />Phase 3 StateCU Enhancements with the simplified report generator (see <br />Recommendations below). <br />Any data displayed in a grid format can be copied to or from Excel or another file <br />type. Note that a similar feature will be added to StateCU under the SPDSS Phase 3 <br />StateCU Enhancements (see Recommendations below). <br />The following features of IDSCU were found to be less useful than with StateCU (summarized <br />in Table 1 below): <br />• As with StateCU, IDSCU requires a scenario to start with a template or dataset. <br />There are several templates provided with the program, however it is unclear what <br />these templates are based on. For example, as with StateCU, only the crop types <br />defined by the crop coefficient and crop characteristic files associated with the <br />template are available for a model run. Some of the templates included with IDSCU <br />include crop types that are not included in the other templates. <br />• Some of the settings are not well documented, such as the use of the "ET <br />Adjustment" and "Altitude Adjustment" to the Blaney-Griddle coefficients. <br />• The GUI screens generally have a lot of information and settings on each screen, <br />making them more confusing than if data were organized by more specific data types. <br />• Some features that do not apply to most analyses have been added to the GUI for <br />specific users and are not well documented in the Help manual (e.g. Sprinkler Spray <br />Loss). <br />• All of the input and output data cannot be viewed graphically through the GUI. <br />• The user must toggle between the input and output screens to view data. This can <br />become cumbersome when checking model results. <br />Task 62.doc 2 of 4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.