-
Notifications
You must be signed in to change notification settings - Fork 2
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
Uncertain why ModelRunner's sequencer chokes halfway through scenario #20
Comments
Still getting the same issue but isolated it down to a smaller region. Suspect it stems from a (single?) value in the metrics-local.csv file but there are no obvious inconsistencies in the inputs. http://23.253.225.19:8888/worker_data/60bb5fd9-fedf-440b-a524-980b9c6d10ec/job_log.txt |
@Naigege, Per Natali's insight, the problem seems to stem from how Sequencer deals with sub-graphs of the http://23.253.225.19:8888/worker_data/65db50c1-39ce-4e33-894a-a1e8dabd082a/job_log.txt
|
Tested the same scenario with Set network =100 on network planner, model runner sequenced it successfully. So our deduction is right on fake nodes. |
Closing this in favor of handling these hard coded settings more flexibly via this issue: |
Sequencing a larger scenario seems to get most of the way there with when we encounter a 'Population' Key error. Unsure how to proceed with completed a modelrunner scenario.
Log from http://23.253.225.19:8888/worker_data/16c0d241-6cc5-4ea7-8d81-4cafa381986b/job_log.txt is below
The text was updated successfully, but these errors were encountered: