Distribution: Why not using AixLib storage sensor outputs instead of fixed top/bottom RealOutput?

[bkadereit]

Description:
Hydraulics/Distribution contains a thermal energy storage. The model always propagates two temperatures (top and bottom) via fixed RealOutput blocks. However, when using the AixLib storage model, temperature sensors are defined at user-specified heights in a separate record.

BESMod behaviour:
Uses a RealOutput that always returns the topmost and bottommost temperatures of the storage regardless of model specifics.

AixLib storage model:
Defines temperature sensors at user-specified heights (e.g. mid-layer, inlet/outlet heights).

Possible issue:
The AixLib temperature sensor definitions are not leveraged by the control logic. This mismatch can lead to controllers reacting on different temperature values than those intended by the user.

Feature suggestion (maybe for AixLib)
In future projects, it may be beneficial to define more than two temperature sensors to optimize heat exchange and maintain stratification.

[FWuellhorst]

In the latest branch #102 which will soon become the latest main, the output connectors of the storage are used already 👍
However, I override the default record behavior in BESMod like this

Because using the height-depending sensor placement makes it harder to change the storage size during a design optimization / simulation study, as the volume affects the equation system. Those options are not final, however, so you can override them if you like.
Having all sensor values in the bus is maybe overkill, as you would not have e.g. 10 sensor values for control in reality, or? This is why I went for just two, naming them always top and bottom. But, we could also go for upp and low or something like this? If you have a use-case with more than two sensors, you could add you own control module for it 👍

[FWuellhorst]

Closed as not going to solve