Richard Wittenoom and Associates Pty Ltd HARDY CROSS PIPE NETWORK ANALYSIS PROGRAM - HDX HDX is a Hardy Cross pipe network analysis program. It requires a terminal format input data file setting out details of the network, together with assumed initial flows in some or all of the pipes. HDX will perform up to 10 iterations of the Hardy Cross distribution in a single run. At the conclusion, it writes a terminal format data file which can, if desired, be used as input for a further run of HDX. In turn a further output file is produced which can again be used as input in the unlikely event that the percentage flow adjustments shown in the output file have not fallen to an acceptable level. HDX uses the standard RWA GCL (command file processor protocol) input procedures. This allows command input to be from either the terminal or a command file. The input data file is however treated as a normal data file, and is not processed as GCL input. INPUT COMMANDS -------------- These will be the same whether input from the terminal or a command file. Use of a command file allows the entire run to be controlled automatically. Available commands are: INFILE filename.ext ..specify the data file OUTFILE filename ..supply a name which will be used to create names for work and output files ITERATIONS number ..how many cycles required DEBUG number ..sets up what is to be written to a logfile (range is 1 to 5). ..program takes over ECHO ..echo commands on screen DO (or) GO ..execute the program QUIT (or) EXIT ..terminate execution HELP (or) ? .. print this message Example of command file entry where the commands are in another file: HDX @FRED (where there is a file FRED.CMD containing the commands for the run) HDX - Hardy Cross Network Analysis Program Page 2 Example of a run with all commands in a single file, showing procedure for two runs at the same session: HDX INFILE PP05WR36A.DAT OUTFILE PPFIRST ITERATIONS 10 GO ; HDX INFILE PPFIRST.OUT OUTFILE PP05WR36A ITERATIONS 10 GO INPUT FILE FORMAT ----------------- This file is a standard terminal format file. The first line MUST contain the Hazyn Williams coefficient C (normally 100 to 130). This may be followed by an optional title, which should be enclosed in double quotes. The second line makes provision for the column headings produced in an output file (becuase we wish to be able to use output files as input files for further runs). If no headings are provided it is still necessary to provide a blank line in the file (or a dummy heading of some kind, e.g. ""). file format: <"title$" (40 chars - quoted)> e.g. 0.445 "Pretty Pool Stage 1 - Water Reticulation" loop pipe oth.loop diam q l/s len 1 6 0 150 13.45 105.5 1 4 2 150 23.45 105.5 1 3 0 100 5.5 70.35 (etc) There should be NO blank lines at the bottom of the file. If theese are present, they may be read in as pipes with conflicting values. DEBUG OUTPUT ------------ Provision is made for detailed output of the internal processes by setting a debug flag. A flag of 4 or greater displays all available output. A value of 1 will display only the allocation of the flow corrections. Intermediate values provide additional data. All debug data is written to a file .LOG