Laserfiche WebLink
~ ~ <br />2. The well stations file (*.wes) is being split into multiple files containing well <br />station parametric information, efficiencies, delay and depletion table <br />assignments. <br />3. The reservoir stations file (*.res) file is being split into multiple files <br />containing reservoir station parametric information, accounts, climate station <br />assignment, area/content/seepage, and delay table information. <br />The following StateDMI enhancements are necessary to support these changes: <br />1. Data management in the main program will be updated to include the separate <br />data products. <br />2. New low-level code will be written to read/write the separate files. <br />3. New command menus and associated commands will be added reflecting the. <br />new data products and associated files. Although some code can be reused <br />(e.g., reading efficiencies from the StateCU list file), new code will need to be <br />written for commands that are specific to the new data products (e.g., editing <br />efficiencies will need to edit only the efficiencies, not the station). <br />4. Backward compatibility will be maintained by retaining existing commands. <br />However, it is likely that implementation of a "Version" parameter may need <br />to occur to support writing old files, with the default being the current file <br />format. <br />5. To eliminate iteration on the capacity value (which is constrained to time <br />series), either a new data value will be added to HydroBase (e.g., maximum <br />historical CF5) or a separate StateMod file will be implemented for capacity. <br />The former will require HydroBase and stored procedure changes and the <br />latter will require StateMod model changes. <br />141.6 Improve error handling. StateDMI as initially implemented printed significant <br />feedback to the log file. However, based on user feedback, the log file is difficult <br />to use when evaluating StateDMI messages to determine whether a run was <br />successful. In Phase 3, several enhancements were made to address this situation, <br />with mixed success. Ultimately, it was decided that a check file should be <br />implemented to provide a summary of potential issues with output products. This <br />approach was successfully applied to well stations and rights. Therefore, the <br />following enhancements will occur to extend the approach to other output <br />products: <br />1. Add check file output for all output products (StateMod and StateCU output <br />files). The initial implementation of the check file was made in Phase 3 for <br />well stations and rights using the following guidelines, and will be <br />implemented on a wider scale in Phase 4: <br />a. For typical users, the check file should be the primary file that is reviewed <br />after commands are run to determine whether data processing was <br />successful, based on a review of the output products. The log file will <br />continue to be used for technical information and for troubleshooting. The <br />22 <br />