Laserfiche WebLink
<br />time series by applying a factor, for instance to represent only a portion of the ditch acreage and <br />historical diversions. <br />Objective: <br />Convert StateCUI from VB 6 to a VB.NET application, both to preserve the State's investment <br />in it as a reliable, maintainable code as well as to take advantage of the new capabilities of <br />modern programming languages. This effort is the cornerstone for the Phase 4 tasks involving <br />StateCUI, as each subsequent updates discussed below will be done after the conversion. <br />Revise the StateCU FORTRAN code to allow the code to properly handle missing daily climate <br />station data and to allow the code to read climate data into arrays, therefore allowing more <br />flexibility in the development and use of input files and to facilitate error checking within the <br />program. <br />Include the ability for users to adjust temperature and precipitation data based on the location of <br />CU structures compared to the location of the climate station where the data used in an analysis <br />was collected. <br />Revise StateCU to allow StateCU capabilities to "fill in" estimates of water supply-limited <br />consumptive use when no diversion records exist and maintain the current option to output a <br />missing data flag for supply-limited consumptive use if there are missing diversion records <br />during the calendar year. <br />Allow the user to run a daily CU analysis to estimate potential consumptive use, then sum the <br />results to monthly and use a monthly effective precipitation method to determine monthly <br />irrigation water requirement. Include the capability to run monthly supply-limited consumptive <br />use analysis within the framework of a daily CU analysis. <br />Automate the generation of new data sets from the StateCU interface using a wizard. Rather <br />than being required to start with a base dataset, allow the user to create a dataset from start to <br />finish through the GUI. As the "wizard" asks for each piece of information, the user can provide <br />data 1) directly to the GUI by copy and pasting from an Excel or text file or typing directly into <br />the GUI, 2) by specifying an existing text file name, or 3) by pulling data from HydroBase (via <br />sending a command to TSTooI or StateDMI through the GUI). <br />In support of allowing users to generate data sets from within the StateCU GUI, enhance <br />StateCUI to allow full editing of the set of StateCU input files with the capability to document <br />input file changes from within the GUI by creating and inserting comment lines into the data <br />files. <br />Program revisions will be implemented so that existing files and formats can be used (the code is <br />backward compatible). Backward compatibility will be implemented by allowing the program to <br />read both old and new formats and/or develop a process that automates the migration of old file <br />formats to new file formats. <br />Approach: <br />76.1 Convert the VB 6 StateCUI GUI to a VB.NET application. Utilize the VB 6 to VB.NET <br />tools provided by Microsoft to identify and convert code, controls, forms, and libraries in <br />StateCUI. Maintain existing StateCUI functionality and software design but utilize classes <br />Page A-9 <br />