WSP12125 - Laserfiche WebLink

Home Browse Search

(J J ;\4 ..; 0 '. user for the dirch numbers for which the diversion data are to be changed, (3) queries the user to input each new diversion quantity, and (4) repeats the display of the diversion data for error checking and additional changes. If the response is no, the program proceeds to the input of the TRF diversion discharge data. The data input steps for each of the three TRF diversion categories (FAP TRF diversions, CCS TRF diversions that are exchanged, and CCS TRF diver- sions that are not exchanged) are identical. For each category, the program first queries the user if there are any TRF diversions for that particular category. If the response is yes, the program repeats the previous display of the NSF diversion table, but lists data for the appropriate TRF diversions from the last computa- tion date. Changes to the TRF diversions are made in the same way as changes were made for the NSF diversions; when all the diversion data for a TRF cate- gory are correct, the program proceeds 10 the next category. If the response to the "any TRF diversions?" query is no, for any TRF category, the program defines that TRF diversion at each ditch as zero and proceeds to the next TRF diversion category. For each TRF diversion in each TRF diversion category, the accounting program makes three intemal checks on the data. The first check is that the account balance for a ditch must be greater than zero before a TRF diversion can be specified. The account balance is computed by the program as the difference between the PURCHSD and the USED account values (table 5); the program also converts the balance to cubic feet per second. If the account balance is less than or equal to zero, the program only allows a TRF diversion of zero for that ditch. The second check is that the TRF diversion specified for a ditch may not be larger than the TRF account balance for that ditch. If the TRF diversion is larger than the account balance. the program defines the TRF diversion as zero, but the user can specify another TRF diversion quantity that is less than or equal to the account balance for that ditch. The third check is that the sum of all TRF diver- sions in each TRF diversion category may not exceed the TRF release quantities that are input. For this check, however, the TRF release quantity is assumed to be 20 percent less than the actual release quantity. This assumption is used because the computed purchase quantity for each TRF diversion' (see the "Changes to Account for Diversion of Transmountain Return Flows" section, p. 15-16) usually is larger than the specified diversion. Without this assumption, spec- ': ~: ,.' ifying a total TRF diversion quantity (for each TRF diversion category) that is equal to the TRF release quantity specified on input would be possible; in this case, because of (I) transit loss as the TRF moves downstream and (2) the TRF diversions, the TRF could be less than or equal 10 zero in the transit-loss computations. If the FAP TRF or the CCS TRF quan- tity is less than or equal to zero at any node in the computations, the program prints an error message, SlOps all computations. and returns to the program options. Use of the 20-percent reduction assumption decreases the likelihood of a program SlOp because the total of the specified TRF diversions always is less than the TRF release quantities specified on input. In the third check just described, the accounting program defines the following TRF release quantities for each TRF diversion category: (I) For the FAP TRF diversions, the TRF release quantity is equal to the FAP release quantity at the CCS WWTF plus the FAP release quantities at the Security. Widefield, and Foun- tain WWTF's, when release data becomes available for these three WWTF's (see the "Return-Flow Discharge Data" section, p. 33); (2) for the CCS TRF diversions that are exchanged, the TRF release quan- tity is equal to the CCS TRF release quantity at the CCS WWTF plus the Fort Carson TRF; and (3) for the CCS TRF diversions that are not exchanged. the TRF release quantity is equal to the CCS TRF release-quan- tity sum computed in item 2, minus the sum of the CCS TRF diversions (in item 2) that are exchanged. When input of all NSF and TRF diversion discharge data is completed, the accounting program sums the NSF and TRF diversions in each category by stream segment and by subreach for use in the stream- segment and subreach computations (figs. 4 and 5). After summing the diversion discharge data, the program writes all of the newly input TRF and native return-flow discharge data, gaging-station discharge data, and NSF and TRF diversion discharge data to the divers.fit file, and then proceeds to the transit-loss computations. Transit-Loss Computations Following the 1994-95 program changes, transit-loss computations were made by the accounting program for two TRF entities-the FAP and the CCS TRF's. The computations made for each TRF entity are identical to the computations in the original accounting program (figs. 4 and 5), except for 34 Descriptions 01 the Program Changes (1989-97) and a User Manual tor 8 Transit-Loss Accounting Program Apptted to Fountain Creek Between Cotoredo Springs and the Arksne.. Rtver, Cotoredo