Laserfiche WebLink
Subtask 5. Update the low-level DMI routines needed by the cucropco, cuclimat, cucommon, and <br />cunonet DMI utilities as needed for the Year 2 efforts, and help the consumptive use developers <br />implement standard DMI features in existing programs. <br />Low-level DMI routines have been updated throughout Year 2 to support the consumptive use modeling <br />effort. <br />Subtask 6. Document all DMI utilities and library routines. <br />DMI utilities are documented in the CRDSS Users? Manual and are available in hard-copy and on-line <br />forms. The DMI library is documented in the CRDSS Developers? Manual and is available in hard copy <br />and on-line forms. <br />Subtask 7. Develop a GUI for the StateMod program to control the execution of the model and <br />view/edit the model input/output files documented in the StateMod Users? Manual. <br />StateMod <br />The graphical user interface (GUI) has been implemented and contains extensive functionality <br />for reading, displaying, editing, and writing StateMod files, as well as being able to run the model. The <br />program is documented in the CRDSS Users? Manual. This application represents a significant amount <br />of effort. <br />Additional functionalities or modifications to the original scope are: <br />? <br />Graph templates have been implementing to help the user quickly produce graphical output. <br />Graphical output can be created as line or bar graphs. Different scenarios can be graphed on <br />the same graph. <br />? <br />The status message bar can be set to display additional debug and warning messages and <br />output is written to a log file. Coordination with State representatives resulted in a StateMod <br />update to flush its output buffer and exit with appropriate stop codes to allow the GUI to <br />detect problems. <br />? <br />All files are read into memory. Time series that are read into memory could potentially <br />cause performance problems and, at a minimum, require additional memory. However, the <br />option of reading the time series only when displayed or graphed could also result in <br />performance problems (slow execution). One approach to not reading time series into <br />memory is to run the StateMod model in report mode to generate an ASCII time series file <br />when necessary. This will eliminate the need for the GUI to read through the time series <br />files. Note that if a time series file is to be written, then the entire time series file will have <br />to be read in order to be written. It is recommended that this issue be studied further when <br />the interface is ported to the PC. <br />? <br />In addition to implementing spreadsheets for viewing data, advanced search features have <br />been implemented to allow the user to type in part of an identifier or description to find <br />stations, structures, and water rights. <br />3 <br />a320/taskmems/ 2-06-01.doc 01/03/97 <br />