Found this out by noticing that a pump that had a status boundary = 0 could be turned on by Epanet, e.g.
Pump TR_PUMP_1 switched from closed to open
apparently because the element appears in a disabled control rule. If the control is completely eliminated then Epanet leaves it alone, as expected.
Bottom line is that disabling control rules is not completely "disabling" them, as currently implemented. Not sure if this is really an RTX issue or better in Epanet, but it's here since RTX is the thing that cares.
Found this out by noticing that a pump that had a status boundary = 0 could be turned on by Epanet, e.g.
apparently because the element appears in a disabled control rule. If the control is completely eliminated then Epanet leaves it alone, as expected.
Bottom line is that disabling control rules is not completely "disabling" them, as currently implemented. Not sure if this is really an RTX issue or better in Epanet, but it's here since RTX is the thing that cares.