Inflow¶
At a glance…¶
The inflow node represents an inflow to the system. This can be time-varying and therefore can represent natural inflows (e.g. from a catchment) or an inflow from another system. Inflows must be positive.
[node.my_inflow_node]
type = inflow
loc = 20, 30
inflow = data.allflows_csv.by_name.little_river_inflow
ds_1 = my_other_node
Node properties¶
| Property | Description |
|---|---|
| [node.?] (compulsory) | Start of node declaration. This says we are creating a node, and also defines the name of the node. Node naming conventions are discussed at . Example: [node.my_inflow_node] |
| type (compulsory) | The node type, which is “inflow” in this case. type = inflow |
| loc (compulsory) | The location of the node in cartesian coordinates. Example: loc = 20, 30 |
| inflow (optional) | Inflow data [ML]. Example: inflow = ata.allflows_csv.by_name.little_river_inflow |
| expected_inflow (optional) | Expected inflow for purpose of adjusting orders [ML]. Example: expected_inflow = 0.5 * this.inflow[-1,0] |
| ds_1 (optional) | Name of the downstream node. This property defines a downstream link. Inflow nodes may only have 1 downstream link. Example: ds_1 = my_other_node |
Results associated with this node¶
| Result | Description |
|---|---|
| dsflow | Downstream flow [ML] |
| usflow | Upstream flow [ML] |
| ds_1 | Downstream flow on link ds_1 [ML] |
| ds_1_order | Order on link ds_1 [ML] |
| inflow | Inflow at this node [ML]. This includes the lateral flow only, not including the component that came from any upstream nodes. |
| expected_inflow | The value of the expected_inflow expression [ML] which is used to reduce required upstream flow when adjusting for orders. |
How the node works¶
The inflow node simply adds inflows to the system as specified by the “inflow” property. The downstream flow is therefore
dsflow=usflow+inflow
References¶
None.