Model works in EPANET but not so well in WaterGEMS

Hello Linda, 

While looking at sample models from EPANET I saw that for simple controls on tank in EPANET it is denoted as NODE 1 e.g. not TANK 1. So I replaced tank word with node in EPANET and then exported the file as .NET and then imported in WaterGEMS then controls are imported correctly. 

After computing the model there are user notifications like junctions are disconnected as tanks become full.

In WaterGEMS whenever tank becomes empty or full the a built-in altitude valve will close the adjacent pipe., making the network disconnected.

So you see those user notifications about junctions being disconnected and tanks becoming full. You would need to revise your controls so as tanks not become completely empty or completely full. Please see below technote for reference on this.

What happens when a tank becomes empty or full? (altitude valve)

Hello Linda, 

While looking at sample models from EPANET I saw that for simple controls on tank in EPANET it is denoted as NODE 1 e.g. not TANK 1. So I replaced tank word with node in EPANET and then exported the file as .NET and then imported in WaterGEMS then controls are imported correctly. 

After computing the model there are user notifications like junctions are disconnected as tanks become full.

In WaterGEMS whenever tank becomes empty or full the a built-in altitude valve will close the adjacent pipe., making the network disconnected.

So you see those user notifications about junctions being disconnected and tanks becoming full. You would need to revise your controls so as tanks not become completely empty or completely full. Please see below technote for reference on this.

What happens when a tank becomes empty or full? (altitude valve)

Hi Sushma

I am working on this model again and I am trying to rationalize the process flow here. the tanks have been defined in EPANET and the model runs successfully as supposed to, as there are TANKS. When these are changed to NODE you are only referring to the name only or the entire element type as that would make the model incorrect as that would mean there would be no tanks.

Should this change be in the model or the control file or both.

I am not that well versed on EPANET so this is also a discovery on my part.

When I replace the word 'TANK' with NODE the model runs successfully in EPANET but once exported as .inp and imported into WaterGEMS when run a new set of errors come up:

-1    "(N/A)"    "Action"    "9501"    ""    (N/A)    "Unknown status value in control action (12.140). Value assumed as SETTING."    EPANET import
-1    "(N/A)"    "Action"    "9504"    ""    (N/A)    "Unknown status value in control action (9.10). Value assumed as SETTING."    EPANET import
-1    "(N/A)"    "Action"    "9507"    ""    (N/A)    "Unknown status value in control action (12.6). Value assumed as SETTING."    EPANET import
-1    "(N/A)"    "Action"    "9510"    ""    (N/A)    "Unknown status value in control action (6.7). Value assumed as SETTING."    EPANET import
-1    "(N/A)"    "Action"    "9513"    ""    (N/A)    "Unknown status value in control action (13.55). Value assumed as SETTING."    EPANET import

........

I've tried to search what these refer to but I can't find anything.

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?

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