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
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:
Allow the user to specify the temporary, report, and .bin file names.
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.
The text was updated successfully, but these errors were encountered:
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.
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:
Happy to discuss this issue and work together on a solution.
The text was updated successfully, but these errors were encountered: