What happens when a scada driven model element status/setting conflicts with a model-based control and the control is enabled?

[jamesuber]

[samhatchett]

Congratulations on your 100'th issue. The answer is UB - this is an edge case i suppose, which should be handled somehow. Do you have a suggestion?

[jamesuber]

UB? Thinking more about it, I suppose that the answer really is - leave it to the client application to “properly” deal with. But from RTX perspective, I suppose that letting Epanet “take over” is the expected behavior. And, if that results in some weird blend of data driven and control driven - like you just changed a pipe status using a data stream at the beginning of a hydraulic time step, but Epanet changed it back using a control rule - then so be it. You get what you asked for.

On Sep 9, 2016, at 10:56 AM, Sam Hatchett notifications@github.com wrote:

Congratulations on your 100'th issue. The answer is UB - this is an edge case i suppose, which should be handled somehow. Do you have a suggestion?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #100 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ACTACXPsPn5hGldBq1XraL3Zy12CM14cks5qoXOCgaJpZM4JFXmE.