A time-series demand model allows you to extract water directly from a storage and identify the amount of water required to satisfy a demand at each time-step. The model doesn’t have to be directly downstream of the storage, the supply point will order water from the storage to meet demands.
If a confluence is between the storage and water user demand, the flow pathway link in the confluence must be set to regulated for the storage to order water to satisfy the demand downstream. If it is left unregulated, water will not be ordered from the storage and the supply point will pull water from the river at the point in the network that it sits to meet the demand. if the demand is higher than the volume in the reach, then the supply point will extract everything.
If there is no storage in the network above the supply point and water user node, then the volume is extracted from the river at the point where the supply point sits in the network.
Time-series demands can be defined using either a time-series data file (Table 25 shows the format of a file), an expression, or by linking to the output of another scenario in the same project.
Refer to Return flows for details on configuring this parameter.
Table 25. Water User node (Time Series Demand, data file format)
Row | Column (comma-separated) | |
|---|---|---|
1 | 2 | |
1 | date | value |
Where: date is the date of observation in dd/mm/yyyy format (eg 31-12-2000)
value is the observed value (eg 2600).