Current Functionality as of 12/6/2023

Bug Issues

appsettings.json is being cashed

appsettings.json in currently being cashed in memory. This causes problems when you change a setting in appsettings.json and it does not update when you run. In order to get new changes to go through you currently need to either build the solution again or clean the solution again.

MSX is throwing errors

The error Encountered EPANET Error Code 524 on EN_nextQ The 524 error is the error for illegal math ERR_ILLEGAL_MATH. The error is being called in the msxqual.c at line 626 in the transport function.

The version of EPANET is the latest release from EPA of EPANET 2.2.0 engines from OWA (https://github.com/OpenWaterAnalytics/EPANET/releases/tag/v2.2) and the EPA's updated Delphi-based Graphical User Interface. https://github.com/USEPA/EPANET2.2/tree/35040bb921791f22e7e531d8e1cd519ae217273b This is not the same as the OWA EPANET that we use. They were taken from the same source code but there have been 884 commits to the OWA version since this release EPA has also added changes so now they are not the same.

Console Core

Test Benz network EPANET GUI to run MSX In our dropbox try the old version with new dll. 32 bit.

In EPANET version 2.2 they introduced the functionally that you could make multiple Hydraulic runs using the same DLL at the same time. In order to handle this each Hydraulic run was given a pointer for the run. This was how they kept track of multiple scenarios.

MSX needs to know the pointer to get the hydraulics for the run. In order to step into the hydraulic run we had to rewind the hydraulic file to find the pointer

The quick and dirty comparison of GQC MSX and EPA MSX was done by deleting GQC MSX and replacing it with the EPA MSX. This allows us to get GIT to compar the two. One of the major differences is there is no pointer.

For a more complete level of all changes please look at the MSX changes Page. (This is not completed at this time.)