You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm trying to run simulations using the wntr.EpanetSimulator() function in parallel and i keep getting back epanet errors "EPANET Error 200" or "EPANET Error 224". the error implies i do not have a supply nodes but I explicitly call wntr.add_reservoir()/wntr.add_tank() beforehand, it's unclear to me why this is happening.
i also assert that the network is completely connected (using the wntr.to_undirected() function), and that there is at least one supply node (length of wntr.reservoir_name_list + wntr.tank_name_list).
the os im using is linux (ubuntu), any pointers as why this is happening? my hunch is the parallelization of writing and running multiple files at once
The text was updated successfully, but these errors were encountered:
tyjchen
changed the title
EPANET when running EpanetSimulator in Parallel
EPANET i/o error when running EpanetSimulator in Parallel
Mar 1, 2019
It's possible that each process is pointing to the same INP file. The EpanetSimulator writes an INP file called 'temp.inp' by default. You can set a unique name for that file using file_prefix when you call run_sim.
i'm trying to run simulations using the wntr.EpanetSimulator() function in parallel and i keep getting back epanet errors "EPANET Error 200" or "EPANET Error 224". the error implies i do not have a supply nodes but I explicitly call wntr.add_reservoir()/wntr.add_tank() beforehand, it's unclear to me why this is happening.
i also assert that the network is completely connected (using the wntr.to_undirected() function), and that there is at least one supply node (length of wntr.reservoir_name_list + wntr.tank_name_list).
the os im using is linux (ubuntu), any pointers as why this is happening? my hunch is the parallelization of writing and running multiple files at once
The text was updated successfully, but these errors were encountered: