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

Improvement: change undefined object error in [REPORT] section to a warning #171

Open
MdoubleDash opened this issue Apr 17, 2024 · 1 comment · May be fixed by #194
Open

Improvement: change undefined object error in [REPORT] section to a warning #171

MdoubleDash opened this issue Apr 17, 2024 · 1 comment · May be fixed by #194
Assignees
Milestone

Comments

@MdoubleDash
Copy link

In the event that an entity (subcatchment, node, or link) within the reporting section cannot be located within the model, SWMM promptly issues an error message:

ERROR 209: undefined object Test_Element_01 at line 5577 of [REPORT] section:
  SUBCATCHMENTS object Test_Element_01

Dealing with this can be a real pain, especially when you're juggling multiple scenarios. So, instead of freaking out with an error, it would be way cooler if SWMM just gave a heads-up:

WARNING 13: undefined object for reporting Test_Element_01
@cbuahin
Copy link
Collaborator

cbuahin commented Apr 23, 2024

It will be nice to make the model output a self contained unit that is independent from an input file, but your suggestion is a good intermediate step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment