Hi All,
To preface, I'm using EPANET way, way beyond its original intended purposes (modelling Reverse Osmosis installations and other water treatment installations).
Due to the large amount of pumps and control-, check- and regular valves in such a system I often run into issues with network stability, mainly caused by dead or isolated branches, or pumps being unable to supply enough pressure during plant startup.
The instability can most often be resolved by adding a small reservoir linked to the offending node, allowing to solver to continue.
EPANET reports the node for which the network is ill-conditioned, but there is currently no way to get the node index/id, other than parsing the report file. I therefore suggest adding a EN_geterrornode method to return the node giving errors.
Apart from my rather unusual use-case I'm sure this functionality will also be of help for other people working on models using the new toolkit methods to generate and modify networks.
Hi All,
To preface, I'm using EPANET way, way beyond its original intended purposes (modelling Reverse Osmosis installations and other water treatment installations).
Due to the large amount of pumps and control-, check- and regular valves in such a system I often run into issues with network stability, mainly caused by dead or isolated branches, or pumps being unable to supply enough pressure during plant startup.
The instability can most often be resolved by adding a small reservoir linked to the offending node, allowing to solver to continue.
EPANET reports the node for which the network is ill-conditioned, but there is currently no way to get the node index/id, other than parsing the report file. I therefore suggest adding a
EN_geterrornodemethod to return the node giving errors.Apart from my rather unusual use-case I'm sure this functionality will also be of help for other people working on models using the new toolkit methods to generate and modify networks.