Laserfiche WebLink
<br />Network Data <br /> <br />,I :,1,' <br />Stations. : ~l I~ ,. <br />~. .. .' \ '-I.~j <br /> <br />4 Network Data <br />4.1 Stations <br />4.1.1 Station Identification. (10): Required. This must be an integer with at most 6 <br /> <br />digits. <br /> <br />4.1.2 Station name: 4O-character maximum. This is not used by the program, but it <br />appears on the reports. <br /> <br />4.1.3 Downstream station: The station identification of the downstream station: This <br />is a unique field for each station, since there can be only one downstream station for each given <br />station (although any number of stations may have the same downstream station). Leave this field <br />blank for a basin exit (no more stations); there may be any number of basin exits in the system. This <br />is the mechanism HYDROSS uses to organize the network. <br /> <br />4.1.4 Other loss table: Optional. This is the 'miscellaneous' means of forcing water <br />into or out of the network. The 'other loss' table gives monthly values of flow leaving the system <br />(negative values are an 'other gain'). <br /> <br />4.1.5 Local flow table: Optional. HYDROSS normally computes the station gain by <br />subtracting the flow at this station from the total flow at all stations immediately upstream from this <br />station; a local flow table overrides this and uses the table value for the station gain. <br /> <br />4.1.6 Reach efficiency table: Optional. If the reach immediate! y below the station <br />can be accurately represented as a canal, then the reach efficiency table functions like a canal <br />efficiency table for diversions: the table value is the percentage of the flow in the reach which <br />actually reaches the downstream station. <br /> <br />4.1.7 % reach loss to return flow: Optional, pennitted only if there is a reach <br />efficiency table given for the station. This gives the percentage of the reach loss which will <br />eventually return to the system (see section B.5.2 [page 43]). Reach losses must be delayed and may <br />not return to the system in the month they were lost. <br /> <br />4.1.8 Channel caoacitv table: Optional. Channel capacity represents the flow at <br />which the river goes into flood, and flows in excess of this value will cause flood damage. <br />HYDROSS will not voluntarily release water which will cause flooding. Normally this would be a <br />constant value, but there are cases (such as the dual operation of the Jamestown and Pipestem <br />reservoirs at Jamestown, ND) where the channel capacity is redefined depending on the severity of <br />flood conditions. This table gives you the option of redefining channel capacity during the 1 % (or <br />less) of the months when you might want to. <br /> <br />4.1.9 Diversion caoacity: Optional. If it is desirable to constrain the total of all <br />diversions at a station, either because they leave the stream through a common canal or because they <br />leave a reservoir through a common pump, then this is a means of providing a constraint. The <br />diversions will be satisfied in priority order up to the constraint; then no more water will be diverted. <br /> <br />4.1.10 Pumoinl! schedule table: Optional. This provides a further constraint on the <br />total diversion at a station. In a case where total diversion is blocked by ice for part of a month, this <br />table provides a means of telIing HYDROSS just what the diversion limit really is for the month. <br />This worb in tandem with the diversion capacity constraint above: the smaller number governs. <br /> <br />March 25, 1991 <br /> <br />HYDROSS 4.1 <br /> <br />Page 23 <br />