First time here? Check out the Help page!
1 | initial version |
I saw the issue on GitHub and have taken a quick look at it. I'll also post an answer there as well. The Input-Output Reference does address this issue. Here is the section of text that addresses the flow rate:
1.14.14.1.13 Field: Pool Water Maximum Flow Rate This input is the maximum water volumetric flow rate in m3/s going between the pool and the water heating equipment. This along with the pool setpoint temperature and the heating plant equipment outlet temperature will establish the maximum heat addition to the pool. This flow rate to the pool will be varied in an attempt to reach the desired pool water setpoint temperature (see Setpoint Temperature Schedule below).
The code backs this up. Basically, if the input fluid temperature is fixed as is the case here, there's only one way to adjust the heat addition--vary the flow rate. Without doing that, you won't hit the setpoint and will overshoot. The question is: if you don't vary the flow rate, what is the strategy? Do you use an intermittent strategy? Or just let it overheat and then compensate with less heat addition the next time step? That would more or less simply be an on-off strategy. Either way, it seems like this would require an additional input and new code (basically a small new feature). I'm not sure there is time for this given that the IO Freeze is in less than one week. If this can get resolved quickly, I might be able to get it into the code for the 23.2 release, but no guarantees at this point.