Lew Rossman

This issue has been addressed by PR #702 and can be closed.

Mitch Heineman sent me an input file that had an orphan conduit with junctions at both ends with no inflow and initial depths of 5 and 4.99 ft, respectively. Below...

Looks like a fractal drawing :astonished: .

I believe this issue has been addressed in release 5.2.0. From the epaswmm5_updates.txt file: _6 . Support for relative path names for files appearing in an input file has been...

For some unknown reason the Modified Horton bug fix in PR #56 never actually got added to release 5.1.015 and all subsequent releases. The attached zip file contains the updates...

@lbutler I still think we should design the 2.x versions so the "official" EPA-EPANET GUI can still work with them (minus the new features). Changing the "Emitter Backflow" keyword to...

PR #788 has changed the "EMITTER BACKFLOW" option keyword to "BACKFLOW ALLOWED" to resolve the issue raised here. @lbutler you should probably update your OWA GUI code accordingly.

How about `EMITTER_BACKFLOW`? I tested it with the current 2.2 GUI and it simply ignores it - no error message and no confusing it with `EMITTER EXPONENT`.

I'm staying with `BACKFLOW ALLOWED`. I just merged its PR into `dev`.

Sharing my 2 cents: 1. I think the two new functions are worth adding. 2. The existing `EN_getnodevalue `and `EN_getlinkvalue `functions should not be modified to return all values based...