You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/usage.qmd
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -321,7 +321,9 @@ There are currently 4 possible link types:
321
321
The LevelDemand and FlowDemand nodes use control links to indicate which nodes it will assign demands to.
322
322
3. "listen": The listen links define which nodes are listened to by control nodes.
323
323
They point from the listened node to the control node.
324
-
The control node tables define listening behavior (`listen_node_id`, variable, weight, look-ahead), and the Python API automatically adds missing `listen` links when writing a model.
324
+
The control node tables define listening behavior (`listen_node_id`, variable, weight, look-ahead).
325
+
Listen links are **automatically created** when a control link is added via `model.link.add`: the Python API reads the `listen_node_id` columns from the control node's tables and adds any missing listen links immediately.
326
+
If you want custom geometries, listen links can also be added manually with `model.link.add`, where `from_node` is a listenable node (e.g. a Basin) and `to_node` is a control node (e.g. DiscreteControl or PidControl). The link type is automatically inferred as `"listen"` from the node types.
325
327
4. "observation": Observation links point from an Observation node to the node being observed. These links are not used in the simulation core, but allow attaching time series data for reference, validation, or visualization.
0 commit comments