Laserfiche WebLink
CRDSS <br />TASK MEMORANDUM 2.06-1 <br />Input/Output Database <br />Input/Output Database Year 2 Efforts <br />1.0 ISSUE <br />This task memorandum describes the input/output database efforts for Year 2 of CRDSS. <br />2.0 DISCUSSION/ANALYSIS <br />This task was named in Year 1, but the Year 2 activities cannot be fully considered input/output <br />activities. The primary focus of this task was to implement a graphical user interface (GUI) for the <br />StateMod program and update supporting data management interface (DMI) programs to support <br />StateMod modeling. <br />The Year 2 effort was broken into several subtasks which are summarized below. <br />Subtask 1. Develop an overall design for the methodology used to access scenario handling. <br />During scoping, the State management team recommended a simple scenario management structure in <br />which data sets are stored in directories. Scenario management then becomes a matter of tracking and <br />manipulating directories. <br />RTi implemented a scenario manager that can be called from different applications (and is called from <br />the StateMod GUI and the consumptive use interface). The scenario manager is documented in the <br />CRDSS Users? Manual and consists of a simple interface that allows a user to perform the following <br />actions on scenario directories: copy to any other directory, duplicate on same directory level, create a <br />child directory, and delete. Basic information about scenarios are stored in a scenario file (the file name <br />is scenario ) in the data set directory. This file is important because it tells the scenario manager which <br />files to copy and can consequently be used to limit scenario files to input and control files (not huge <br />output files, which, if copied, could fill up the system and impede performance). <br />The scenario manager as implemented enforces basic scenario standards and allows for a README file <br />to be stored with data sets. It is the responsibility of modelers to update the README file. Approved <br />data directories for each application exist and are similarly named (e.g., /crdss/statemod/data/coloup ). <br />Subtask 2. Design and implement an improved DMI utility program or equivalent. <br />demandts <br />demandts <br />The DMI utility has been implemented and contains functionality to process historical <br />diversions, irrigation demand time series, and crop information. The utility is documented in the CRDSS <br />Users? Manual. It was agreed with State representatives that this utility need not process CRSS time <br />tapedit <br />series directly. Instead, the program has been updated with the assistance of the State to output <br />tstool <br />StateMod format time series. These time series can then be read by and can be manipulated as <br />desired. <br />demandts <br />Additional functionalities not specifically addressed in the scope, but of interest are: <br />1 <br />a320/taskmems/ 2-06-01.doc 01/03/97 <br />