Laserfiche WebLink
<br /> <br />multiple files). Basic features, once implemented, could be extended in future <br />enhancements, as needed. <br />140.3 Improve error handling. The TSTooI software is by design very generic. <br />Consequently, error handling occurs at various levels but may not always provide <br />users with feedback that is ideal for troubleshooting, and enhancements are <br />required. Similar StateDMI enhancements are discussed in Task 141. However, <br />whereas StateDMI has specific data products that allow for specific data checks <br />(e.g., well stations and rights), TSTooI output is more general and software cannot <br />as easily perform appropriate checks in all cases (in particular because in TSTooI <br />intermediate time series are often not written to final output and should probably <br />not be included in checks). Preventing errors in TS'I'ool often involves preventing <br />user input errors. The following TSTooI enhancements will be implemented to <br />address usability issues with error handling, focusing on features most often used <br />in StateMod modeling: <br />1. A general checkTimeSeries () command will be implemented, allowing <br />users to check for data problems at the end of the run. Optional parameters <br />will be provided to specify the time series to check, verify that a time series is <br />created for a list of location identifiers (specified as a delimited list file), <br />check for missing data, and check for all zero data. Results will be printed to <br />auser-specified check file, which can be overwritten or appended. This <br />command will therefore provide similar check capabilities as in StateDMI, <br />while relying on users to help define check criteria (whereas in StateDMI <br />default checks specific to each data type can are implemented). The purpose <br />of the check file is therefore to help the user get an indication of whether the <br />results are "ok" or have potential issues. <br />2. A list of output files created during the session will be added to the bottom of <br />the main TSTooI window, similar to StateDMI. This will allow users to <br />quickly review output and will allow the optional check file to be listed. <br />3. Log file messages will be reviewed and the current log file messages will be <br />trimmed down to show only high-level summary information. Given the <br />subjectivity of some of these decisions, large number of commands, and need <br />to review a large code base, the effort in Phase 4 will focus on common <br />commands used and errors encountered in CDSS modeling, including reading <br />HydroBase and StateMod files, and fill commands. This will allow users to <br />more effectively use the log file during troubleshooting. <br />4. The readStateMod () command, which is used to read all monthly or <br />daily time series from a StateMod time series file, will be enhanced so that <br />editing subsequent commands will show the list of time series from previous <br />readStateMod () commands. Currently, only time series identified by <br />TSID strings, and left-hand side of TS Alias =commands, are listed in <br />time series choices for subsequent commands. Only the header of the <br />StateMod file will initially be read to get the list of time series, with the data <br />being read when the commands are run. This capability will involve changing <br />some of the main program design but when complete will provide a roadmap <br />13 <br />