CRDSS_Task1_05-9_UtilityStructureAndScenarioHandling

• Title: CRDSS Task 1.05-9 - Study of System Integration Issues DMI - Utility Structure and Scenario Handling
• Description: This memorandum describes the structure of DMI utility programs and presents preliminary ideas on scenario management ‎(which is a Year 2 task)‎.
• Decision Support - Doc Type: Task Memorandum
• Date: 5/10/1994
• DSS Category: DMI Utilities
• 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.

without storing the scenario as such in a scenario database. This preliminary Year 1 product will
require that the user manually change the baseline values each time the DMI is run.
The flag that will indicate whether a display is to contain an editable half will be implemented
simply as a single integer, such as 1=FORM_EDITABLE or 0=FORM_NOT_EDITABLE.
Additionally, based on specific applications, it may be desirable to have an array of edit flags
indicating which specific components of a display are editable. This would allow fields to be turned
on for editing as development of the CRDSS database and the scenario database proceeds. This
would also allow the flexibility of turning off scenario options in certain situations. For example, if
it is possible to edit the capacity of reservoirs, but, for some reason, it is known that the user should
not do so, then the edit flag could be set so that parameter is not editable. The display form could
indicate non-editable parameters in a grayed font, or simply by not displaying the field.
3.0 CONCLUSIONS AND RECOMMENDATIONS
Each DMI utility will use display components developed as described in Task Memoranda 1.05-15,
1.05-16, 1.05-17, and 1.05-18, and will contain model-specific code for translating CRDSS database
information into model-specific flat files. This will involve:
(1)Calling low-level DMI routines to retrieve data from the CRDSS database;
(2)Displaying the data in a form that contains a parallel display for editing scenario data; and
(3)Writing the data in model format to flat files using a model-specific library of output
routines.
Forms for displaying data will be developed in conjunction with modelers, but they will be reusable
so that different programs can use the same display forms.
Specific details of DMI forms will be developed based on the demands of models, and specifications
will evolve throughout Phase II. DMI utilities will in general be model-specific. Their ability to be
shared between models will depend on the differences between models.
5
A275 05.10.94 1.05-9 Malers