This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Model works in EPANET but not so well in WaterGEMS

Hi Guys

Please assist, a user has sent me this for help and I am in transit and unable to assist for the next few hours.

WA corrected controls.ctl  Western Aqueduct_As-Built Current Demands_Rev 5.1.zip

He has a model which he has saved from EPANET (.inp) and imported into WaterGEMS but id does not work as well in WaterGEMS (errors).

Please see the attached (model, control file and screen grabs) and advise further.

Thank you.

  • Hello Linda, 

    I meant to change names in only in controls and not in actual model of EPANET as that would change whole hydraulics. 

    I tested the results between two models in one model controls were defined with word TANK and in other controls in EPANET were defined with word NODE, and results in EPANET were same for tanks results. 

    About below user notifications of "unknown status value in control action ", you may ignore it as controls are successfully imported which can be confirmed in the controls window by comparing that with EPANET controls. There is always a difference in the way you define controls in EPANET and WaterGEMS, its just about that. 

    What are the limitations of importing/exporting EPANET files?

    Regards,

    Sushma Choure

    Bentley Technical Suppport

    Answer Verified By: Linda Maseko 

  • Hi Sushma

    Apart from the warnings about the tank emptying/filling up is the a way to clean up and remove all the other warnings which come up after importing.

    Regards

    Linda

  • Hello Linda,

    There isn't an automated way of doing that. It may be possible fix many issues (depending on what they are) with features like global edits, updates using ModelBuilder, control sets, etc. What are the messages that you need cleaned up?

    Keep in mind that some warning or informational messages may have little or no impact on the actual hydraulic calculation.

    Regards,

    Scott