Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPANET i/o error when running EpanetSimulator in Parallel #71

Closed
tyjchen opened this issue Mar 1, 2019 · 2 comments
Closed

EPANET i/o error when running EpanetSimulator in Parallel #71

tyjchen opened this issue Mar 1, 2019 · 2 comments

Comments

@tyjchen
Copy link

tyjchen commented Mar 1, 2019

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

@tyjchen tyjchen changed the title EPANET when running EpanetSimulator in Parallel EPANET i/o error when running EpanetSimulator in Parallel Mar 1, 2019
@kaklise
Copy link
Collaborator

kaklise commented Mar 4, 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.

@tyjchen
Copy link
Author

tyjchen commented Mar 5, 2019

that seems to have solved the problem, thank you!

@kaklise kaklise closed this as completed Mar 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants