Laserfiche WebLink
<br />" , <br />001 O'~g, " <br /> <br />CRDSS Progress Report (Continued) <br />Year 2 <br /> <br />Progress for Task No.: 2.06 Month: May 1995 Preparer: Steve MaIers <br />Input/OutDut Database (continued) <br />Subtask <br />No. Progress Concerns <br />I The requirements of DMI development and the need to address data flow coordination between tasks <br /> has delayed implementation of a scenario selector, However, work to date has not precluded such <br /> imolementation. and preliminarY rmidelines seem to be falling into place well. <br />7 I. Model updates requested by the WRP group have affected the progress of generating data sets for <br /> basins, delaying full testing of the GU! (see Task 2,10 for file subtasks and concerns, if any). <br /> 2, The State indicated that a fully functional test data set (with all files) is used for testing <br /> ST A TEMOD, RTi requests a copy of this data set; however, the data set must be kept current with <br /> the model in order to be of full use, (This need will go away when data sets for the Yampa and <br /> Gunnison are available for testing.) <br /> 3, It is important that the documentation for the model be kept up to date with the current version of <br /> the code and that data files and execution commands are well documented because the on-line <br /> documentation is the primary source of information for many developers. <br /> 4, A concern exists that the GU! will be depended upon to do too many file manipulation tasks, RTi <br /> would like to discuss how "import" and "merge" features are to be implemented for STATEMOD <br /> and the GUr. <br />7,5 Implementing a status bar for the ST A TEMOD GU! is turning out to be somewhat challenging. The <br /> issue is that the I/O buffering causes abrupt updates in the status rather than consistent updates, It <br /> may be necessarY to imolement a status file in the STATEMOD orogram that can be read bv the GUr. <br /> <br />Authorized <br />Bud et <br />$118,154 <br /> <br />Task Bud et Status (Based on Invoice) <br />Previously Current Month <br />Invoiced Invoice Amount <br /> <br />$22,568 <br /> <br />$11,324 <br /> <br />Total Cost to Date <br />$33,892 <br /> <br />Cost! Authorization <br />29% <br /> <br />.4.3200j.95 <br />