-
Notifications
You must be signed in to change notification settings - Fork 97
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
Sharrow debug in simulate.py not working #874
Labels
Bug
Something isn't working/bug f
Comments
Update: I ran the small ABM3 test example with sharrow on, the model got stuck (no crash, no response, no termination) in the same location. I believe this is why our GitHub Actions test has been failing with error code 143: https://github.com/ActivitySim/activitysim/actions/runs/9209634995/job/25335037344 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This came up when I ran ABM3 100% sample with sharrow set to
test
. See issue ActivitySim/sandag-abm3-example#18. I found a work around to debug but it would be better if we can fix sharrow...In sharrow
test
mode, when the utility returned by sharrow does not match the non-sharrow utility, sharrow attempts to retrieve data and print outpossible problematic expressions
to help debugging. See code here:activitysim/activitysim/core/simulate.py
Lines 800 to 809 in 29d12bc
However, currently the run will get stuck (no crash no response) in line 807
_sh_flow_load = sh_flow.load(sh_tree)
. Not sure if this is broken due to some recent changes.Also, for many example models, the sharrow
test
mode has only been run with small samples, and issues like this seem to get discovered especially when we run large samples (100% HH). This means when agencies adopt sharrow, we should probably recommend runningtest
mode with a large (enough) sample.To Reproduce
Steps to reproduce the behavior:
test
and run ABM3.Expected behavior
It would be nice to have line 807 working and return the problematic expressions.
The text was updated successfully, but these errors were encountered: