Laserfiche WebLink
<br />OiJD4Jl <br /> <br />(I) adding TRF's at locations other than the CCS <br />WWTF, (2) subtracting TRF's for diversion, <br />(3) repeating the computations until the assumed and <br />computed downstream TRF'S have converged (see the <br />"Changes to Program Output" section, p. 22), and <br />(4) perfonni ng the upstream calculation to determine <br />the TRF purchase quantity for any specified TRF <br />diversion (see the "Changes to Account for Diversion <br />of Transmountain Return Flows" section, p. 15-16). <br />These exceptions have been briefly explained in the <br />preceding sections of this report. In the current (1997) <br />version of the accounting program, transit-loss <br />computations are made first for the FAP TRF's, then <br />computations are made for the CCS TRF's, and lastly <br />the comparison computation is made (see the <br />"Changes to Program Output" section, p. 16). <br />The transit-loss computation steps for the FAP <br />TRF's and the CCS TRF's, which are made indepen- <br />dently for each entity, basically consist of: <br />(I) Completing the stream-segment computations <br />(fig. 4) for each stream segment, but including any <br />appropriate additional TRF sources and any TRF <br />diversions; (2) completing ,the subreach computations <br />(fig. 5) for each subreach (fig. 6, table 4) within the <br />stream segment, again inCluding any appropriate TRF <br />sources and any TRF diversions; (3) repeating each set <br />of stream-segment and subreach computations until <br />the assumed downstream TRF has converged with the <br />computed downstream TRF; (4) after convergence, <br />perfonning the upstream calculation for each specified <br />TRF diversion in each subreach to compute the TRF <br />purchase quantity required for e.ach TRF diversion; <br />and (5) updating the TRF diversion USED accounts <br />data with the computed TRF purchase quantities. <br />When the transit-loss computations are <br />completed for the FAP TRF's, the program writes the <br />resulting bank-storage and channel-storage loss and <br />gain results to the faJecov.fil file; when transit-loss <br />computations are completed for the CCS TRF's, the <br />program writes the resulting bank-storage and <br />channel-storage loss and gain results to the cSJecov.fil <br />file. Following the transit-loss computations for the <br />FAP and the CCS TRF's, the program writes (I) all the <br />updated TRF diversion USED accounts data to the <br />accl.fil file, (2) all appropriate data to the secwcd.out. <br />subrcJJ.Oul, and Ilcalc.oul files, and (3) the appropriate <br />results to the daily output file (1Iyyyymmdd) (table 5). <br />The program then (I) makes the transit-loss computa- <br />tions for the comparison calculation, (2) writes the <br />resulting bank-storage and channel-storage loss and <br /> <br />" <br /> <br />gain results to the cmpJecov.fil file, and (3) writes the <br />results for the comparison calculation to the last page <br />of the daily output file (table 5). [See the "Contents of <br />the Nexttrloss Directory" section (p. 27-29) for file <br />descriptions.l When all output has been written, the <br />program closes all the input and output files and <br />returns to the program options. <br /> <br />'{ <br />....~ <br /> <br />5' <br /> <br />MAINTENANCE OF THE TRANSIT-LOSS <br />ACCOUNTING PROGRAM <br /> <br />Maintenance of the current (1997) version of the <br />accounting program is fairly simple. Proper mainte- <br />nance of the program requires some knowledge of <br />where the program files are located and what files are <br />included in the program. In addition, some knowledge <br />is needed about the procedures used to maintain and <br />archive the current output files, where historic output <br />files are archived, and where previous versions of the <br />accounting program are arcbived. The USGS office in <br />Pueblo maintains the accounting program and the <br />associated auxiliary programs, archives the current <br />output files, creates and maintains the historic output <br />archives, and maintains the previous program <br />archi ves. <br /> <br />..,! <br /> <br />Procedures to Archive Current Output <br />Files <br /> <br />In the past, the daily output files were archived <br />manually, which consisted of moving these files from <br />the nexttrloss directory to directories for each month <br />(fig. 7). Usually, the files were not moved on any <br />regular schedule, and dozens to hundreds of files <br />would accumulate in the nexttrloss directory. <br />However, 2 or 3 months after the, end of a water year, <br />the daily output files were moved to the monthly direc- <br />tories, and the monthly directories then were archived <br />to a reel-type magnetic tape. The contents of the other <br />output files associated with the water year that just <br />ended also were archived with the monthly directories <br />containing the daily output files. <br />During preparation of this report, the manual <br />archiving procedure was partly automated. This auto- <br />mation consisted of developing a computer script <br />program that would ( I ) create the 12 monthly directo- <br />ries in the nexttrloss directory (fig. 7) at the beginning <br />of the water year (mid-October) and (2) on the 15th <br />day of each month, move the daily output files for the <br /> <br />~; <br /> <br />MAtNlCNANCE OF THE TRANSIT-LOSS ACCOUNTING PROGRAM 35 <br />