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
While iterating thorugh the nodes in line156 these can be mixed types. This causes line222 to fail if the node is an int.
This is ultimately an upstream issue with ScenarioLoading but I think that SwmmNetwork needs to also enforce string types so that if any([i in node for i in self.outfall_flags]) does not fail.
The text was updated successfully, but these errors were encountered:
lucashtnguyen
pushed a commit
to lucashtnguyen/swmmnetwork
that referenced
this issue
Oct 6, 2017
I modified `scenario.py` and `swmmnetwork.py` to hopefully
closeaustinorr#4. I added a small swmm model .inp and .rpt to run all future
tests on. This test suite is not yet complete, but it is a good start.
In SwmmNetwork, node id's are allowed to be int, but id names read from the SWMM5.1 report file and/or input file should all be strings. I believe this is addressed fully by #5 and a few tweaks to how the id's are split into volume reduced flags, or treatment flags, so I'll close this. I have written a unit test that completes as I expect with int and string types in the SwmmNetwork object, and we'll also add a test for files loaded via the scenario builder objects.
While iterating thorugh the nodes in line156 these can be mixed types. This causes line222 to fail if the node is an int.
This is ultimately an upstream issue with
ScenarioLoading
but I think that SwmmNetwork needs to also enforce string types so that ifany([i in node for i in self.outfall_flags])
does not fail.The text was updated successfully, but these errors were encountered: