Laserfiche WebLink
s • <br />and other VB.NET object oriented language features where feasible. Perform extensive <br />testing to assure no functionality was lost during the conversion. <br />76.2 Revise the StateCU FORTRAN code to allow the code to handle missing daily climate <br />station data. The code will be revised so daily climate station data (minimum temperature, <br />maximum temperature, precipitation, wind speed, vapor pressure, and solar radiation) is <br />read into climate station arrays. If any of the daily climate data required for an analysis is <br />missing, then CU will not be calculated, and a missing flag will result. Climate station <br />arrays will be used to allow more flexibility in the development and use of input files and <br />to facilitate error checking within the program. <br />76.3 Add geographic elevation (orographic) climate data adjustment capability to StateCU and <br />StateCUI. An input variable will be added to the structure file (*.str) to allow the <br />adjustment of temperature and precipitation data for each structure or climate station <br />analyzed for CU analyses using the monthly original and modified Blaney-Griddle <br />methods. <br />76.4 Update StateCU to allow StateCU capabilities to "fill in" estimates of water supply-limited <br />consumptive use when no diversion records exist. Add a control variable to the control file <br />(*.ccu) that allows the user to choose to either 1) output a missing data flag for supply- <br />limited consumptive use if there are missing diversion records during the year, or 2) <br />estimate monthly supply-limited consumptive use by structure based on average monthly <br />CU shortages within the same Water District. <br />76.5 Revise StateCU to sum daily potential consumptive use results to total monthly potential <br />consumptive use, sum daily precipitation data to total monthly precipitation, and use a <br />monthly effective precipitation method to determine monthly irrigation water requirement. <br />The effective precipitation method flag in the control file (*.ccu) will be enabled in a daily <br />analysis for both daily and monthly methods. Allow monthly supply-limited consumptive <br />use analysis to be run in conjunction with a daily CU analysis if the user provides monthly <br />diversion records. The flag to control the level of CU analysis in the control file will be <br />enabled to allow daily analysis to perform asupply-limited "water budget" analysis. <br />76.6 Design and develop a wizard to automate the generating of StateCU scenarios and <br />associated input file sets directly from within StateCUI. Design and develop an interface <br />to this methodology within StateCUI using VB.NET GUI capabilities. Create generic <br />TSTooI and StateDMI command files that will read output from the StateCUI wizard to <br />create StateCU input files. Add input screen wizard that directs the user to answer <br />questions related to the type of analysis, the CU method, climate stations to use in the <br />analysis, crop types/coefficients/elevation or oeographic adjustments, acreage, analysis <br />period, etc. Work with other CDSS contractors to design and develop new features as <br />necessary, for instance simpler command line operations for StateDMI. Enhance StateCUI <br />to read the new data set and alert the user to missing data that should be entered through <br />the GUI (see 76.7 below). <br />76.7 Expand StateCUI file editing capability. Utilize the forms, controls and features in <br />VB.NET to expand the StateCUI editing capability to all StateCU input file data. Enhance <br />current data-checking functions in both the StateCU GUI and StateCU FORTRAN <br />programs to support input file editing. <br />76.8 Update the StateCU documentation to reflect the new features and operation of the <br />VB.NET version of StateCUI as well as all other Phase 4 upgrades to StateCU and <br />StateCUI. Compile the FORTRAN code using the latest version of the Lahey compiler. <br />Page A-10 <br />