Laserfiche WebLink
<br />log file contents are listed in the sequential order of processing, whereas <br />the check file is a summary by data product. <br />b. The check file name by default is the same as the commands file name, <br />with the additional extension ".chk". <br />c. The check file will be cleared before each. run. <br />d. Data checks are specific to an output product (file). <br />e. If more than one output product is processed, the check file contains a <br />section for each product. <br />f. The format of the data check file is generally consistent for all products, <br />consisting of tables with rows of identifiers and data being checked. <br />g. Only offending data are printed to the check file. Therefore, a successful <br />run with no potential issues results in a check file with an "all OK" <br />message only. <br />h. Printing a complete summary of issues may require referencing other <br />products or raw data. In this case, the StateDMI software may need to <br />carry around additional raw data to allow the check file output to be <br />printed. This may require more memory as the program is run but should <br />not have negative impacts. <br />Data checks will be implemented for all StateMod and StateCU files created <br />by StateDMI (approximately 15 StateCU files and 15 StateMod files). <br />Features to check time series will be added to TSTooI in Task 140. Before <br />development starts, RTi will document proposed data checks and provide to <br />the State for feedback. Development will then implement the indicated data <br />checks. <br />2. Log file messages will be reviewed and the default log file will be trimmed <br />down to show only high level summary information. Given the subjectivity of <br />some of these decisions, large number of commands, and need to review a <br />large code base, the effort in Phase 4 will focus on commands that are <br />currently producing excessive output. <br />141.7 Update interface to improve usability. The StateDMI GUI provides a <br />centralized interface for a large amount of data processing. The initial GUI <br />appearance focused on listing data and commands menus for StateCU and <br />StateMod, with only one model being active at a time. Based on use in <br />production work, several enhancements have been identified and will be <br />implemented to improve usability: <br />1. In the HydroBase login dialog, add a choice to select the initial view for <br />StateDMI, either for StateCU or StateMod. This choice will be in effect until <br />changed and controls the command menus that are displayed to the user. <br />2. Add a second level of menus, allowing all products to be listed in the first <br />menu level. This organization is comparable to TSTooI. For example, in <br />TSTooI, the first menu level is "Commands...Read Time Series". Selecting <br />23 <br />