I built a hydraulic network with EPANET2 (GUI Software) which I now want to use with the OWA EPANET engine. I’m using the python wrapper to code the OWA EPANET. So far everything worked fine except that I get different chlorine distribution results with the OWA EPANET engine compared to the EPANET2 GUI software. Chlorine distributes much slower in the network when run with EPANET2 GUI software.
In the google drive you can find the following 4 relevant files:
- static-1h-chlorine. net the network built with the EPANET2 GUI
- static-1h-chlorine.inp the network built with the EPANET2 GUI exported as .inp
- report-static-1h-chlorine.rpt the report generated by the OWA EPANET engine
- EPANET2-static-1h-chlorine.rpt the report generated by the EPANET2 GUI software
The following code was used:
from epanet import toolkit as en
__name__ == '__main__':
# Load our static model from input file
ep = en.createproject()
# Note that the paths to the files have to be absolute paths for some reason data_root = os.getcwd() + '/data/community/' #inpname = 'static-1h-chlorine.inp' inpname = 'Net1.inp' #reportname = 'report-static-1h-chlorine.rpt' reportname = 'report-Net1.rpt' en.open(ep, data_root + inpname, data_root + reportname, data_root + 'output.out') # solve hydraulic en.solveH(ep) # solve quality en.solveQ(ep) en.resetreport(ep) en.setreport(ep, "NODES ALL") en.setreport(ep, "QUALITY PRECISION 4") en.setreport(ep, "LINKS ALL") en.setreport(ep, "STATUS NO") en.setstatusreport(ep, en.FULL_REPORT) en.setreport(ep, "SUMMARY YES") en.setreport(ep, "FLOW YES") en.report(ep) #deletes project en.deleteproject(ep)
If you compare the two reports you can see that in the EPANET2-static-1h-chlorine.rpt Chlorine reaches J-93 at 0:11 Hrs. In the report-static-1h-chlorine.rpt chlorine reaches J-93 after only 0:01:00 hrs. The time formats are copied from the .rpt files.
Did I miss configure something? Do I misunderstand the time parameters? Did something in the engine change regarding chemical distribution?