Conditional (triggered) control

[visr]

Based on flow or concentration in one location, adjust one of the steering mechanisms.

Examples:

• Close Haringvliet to maintain flow on Nieuwe Waterweg
• Stop intake Gouda when salt concentration breaches treshold
• reduce outflow Afsluitdijk based on Lobith discharge (forecast)

or more general:

• choose a different RatingTable
• choose a different pump capacity

condition can be local or elsewhere and may, for boundary conditions, be based on a timestep in future (e.g. Lobith discharge 10 days ahead)

condition can be based on a combination of time, and multiple parameters

condition should be evaluated on discrete moments

[gijsber]

As indicated by waterboards, they typically have
(1) Vaste stuwen met klepstand die wel door het jaar heen aangepast kan worden
(2) Automatische peilgestuurde stuwen waarbij binnen het jaar het peil kan veranderen, inclusief een bereik.
(3) Automatische debietgestuurde stuwen, inclusief een bereik.

On the component side this may dealt with as follows:
(1) can probably be dealt with by a timedependent ratingTable.
(2) can probably be dealt with with our LevelControl component (if not, what does it do ?)
(3) this may need a different kind of connector (FlowControl) as I wonder whether a controlleable RatingTable (e.g. RatingTable x applied given some observation) can cope with this need.

[gijsber]

Start small and then expand:
[ ] one condition changes a parameterized dataset:

• pump flow (block function)
• FractionalFlow switch
• QH-tabel switch
  [ ] one condition + time indicator change a parameterized dataset
  [ ] two conditions change a parameterized dataset
  [ ] two conditions + time indicator change a parameterized dataset

This can then be extended to more complex situations like.
[ ] more complex conditional structures
[ ] PID controller
[ ] linear interpolation of a condition-pumpflow lookup functie voor de pumpcontroller

[gijsber]

Design decisions after discussion 11 May 2023:

• parameterized dataset should stay fixed for the next timestep
• a control-rule can only switch datasets within a node type. In other words, it can change from one Qh-table to another Qh-table, but not from a set Flow to a QH-table.
• a control rule can only affect the parameterization of one node

Recommendation:

• seperate data structure from control mechanism
• try to keep simple rules like abstraction stops at the lowest implementation level (ie in the physical layer outside the control layer)
• try to make a decision layer (on top of the physical control layer) for the prioritization of abstractions. This layer would assess what abstactions would fit the physical situation and erduce those abstractions that have lowest priority.
• it would be nice if we could offer a plugin-framework such that users can make more advanced control formulations

To decide and investigate:

• How many conditions do we allow
• how to keep the system stable

[evetion]

We're gonna implement the most simple control system. 1 obs to 1 action.

• New input type
• New network

New Issues:

• Implement callback with random state machine (boolean) #263
• Implement data structure for (boolean) control #266
• Start of control implementation #274 (Follow-up on 2, design proposal(s) for datastructures for state machine )

[evetion]

See #293 for an initial refinment after the first PoC

[evetion]

Closed by #274