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

EPyT crashes when the same .inp is opened by another process #54

Open
andreArtelt opened this issue Jun 12, 2024 · 3 comments
Open

EPyT crashes when the same .inp is opened by another process #54

andreArtelt opened this issue Jun 12, 2024 · 3 comments

Comments

@andreArtelt
Copy link

Currently, EPyT (and EPANET) crashes when the same .inp is opened by another process -- e.g. this could happen when simulating scenarios in parallel.

I think the crash comes from the fact that the .bin, temporary, and report file names are derived from the .inp file in a deterministic manner -- i.e. the same .inp file always leads to the same temporary, report, and .bin file names.

I see two potential solutions:

  1. Allow the user to specify the temporary, report, and .bin file names.
  2. Add a random component (e.g. random number) to the file names such that those are never the same.

Happy to discuss this issue and work together on a solution.

@andreArtelt
Copy link
Author

But how/when do I call it? First, I would have to create a new instance by calling epanet -- this will create these temporary files automatically.
Also, does a similar function exist for .msx files? loadMSXFile does not allow me to change the naming of the temporary files.

@andreArtelt
Copy link
Author

What is the status of this issue?
For me, this is kind of an urgent issue because it also hinders the training of RL agents in parallel.

Let me know if I can help resolve this issue.

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