-
Notifications
You must be signed in to change notification settings - Fork 41
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
Loading outfalls crashes depending on order #187
Comments
@MortenGrum thank you for identifying this issue with so much detail! I'm going to investigate this over the next day or two. Hopefully we can leverage your unit test to fix this. |
Hey @aerispaha, this is the same issue I mentioned to you some time ago. Are you planning on merging this fix? Thank you @BuczynskiRafal. This addresses a bunch of issues that happens when data blocks have rows with more elements that the first row. |
Hi @lmontest! I would like to merge this fix. I'm having trouble constructing the PR though. This commit on @BuczynskiRafal 's fork seems to be in a unusual state, with GitHub showing this warning: Warning This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. @BuczynskiRafal can you advise? If you can create a PR with these changes, I'll review it asap. |
I think this warning came up because I closed PR. I closed PR because @aerispaha wrote that he was already working on a more general solution to this issue. |
Loading outfalls seems to crash depending on the order of the free and timeseries staged outfalls. Perhaps a bug?
Loading these outfalls works fine:`
but these outfalls raise an IndexError:
The error is:
This unittest fails for the inp file where the free outlet is first:
The two inp file both run in SWMM5.1 (.txt needs to be removed):
outfalls_issue.inp.txt
outfalls_issue_free_first.inp.txt
I am on Windows 11, python 3.9.7, pandas 1.5.1 and using swmmio version 0.6.2.
The text was updated successfully, but these errors were encountered: