Laserfiche WebLink
HYDROSS V3.0 <br />Introduction <br />1.3 Files <br />The HYDROSS procedure files on the Cyber use the following standard <br />symbolic names for data files. Substitution of actual names takes <br />place when the procedure is invoked. <br />FLOS Flow source file. <br />FLOB Flow 'binary' file. This is actually an ASCII file, but should <br />be treated as a binary look but don't touch. If you have to <br />make any edit changes, make them to the source file and re-run <br />module H320. <br />TBLS Table source file. <br />TBLB Table binary file. As with FLOB this is actually an ASCII file <br />which should be treated as a binary for safety reasons. If you <br />have to make any edit changes, make them to the source file and <br />re-run module H310. <br />NETS Network source file. <br />NETB Network binary file. This is a true binary file. Module H330 <br />pre-processes NETS into NETS with the help of TBLB; NETB is then <br />a checked-out network file for input to the compute module H300. <br />NETB is a temporary file, destroyed at the end of the compute <br />phase. <br />INPC Input file for-the compute module H300. Contains title, years <br />of study, and initial reservoir contents. <br />INPR Input file for report module H350. Contains years of reports <br />-and list of desired reports. <br />ODS Output file from compute module H300, input to report module <br />H350. An ASCII file of 150-character records. <br />UFIL Optional input to module H350, controls the units and <br />precision of the output reports. , <br />KEPT Output from report module H350, to be routed to the printer. <br />RFIL Output from report module H350, stored as a file, presumably <br />for later processing by another program. H350 will produce only <br />one RFIL per execution. If you need several different reports <br />of this type, you will have to invoke H350 once for each <br />report. <br />~~...~ <br />