-
Notifications
You must be signed in to change notification settings - Fork 7
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
Bug: KeyError during routes preprocessing of national wind blade datasets #198
Comments
Investigation: Reproduce error by running on Result:
Looks like the AR-originating routes with NANs for destination lat/longs are all going to future-deployment power plants (the The future-deployment plant in AR likewise has NAN lat/longs, as per route_list. So: The future-deployment plants have assumed locations at the ... This is probably related to f9fb9c8 The main fix there was to specify that only lat/long columns were being averaged, and I added a filter that only power plant locations should be included in that average. Therefore, states with no existing wind plants would have NAN lat/longs for future deployment plants (no existing lat/longs to average --> NAN output). Test fix: Change line 469 of compute_locations.py from
to
(I.e. reverting only the change made to that line in f9fb9c8 After re-running, the code proceeds past the AR error and no NANs are present in the route_list file. I'm not going to test all the way through to the end as it'll take too long and eat up processing power, but this particular bug should be resolved with the next couple of commits. |
…ure power plants are calculated even when no power plants currently exist
#198 removes power plant facility filter so average locations for fut…
Adds bugfix #198 to circularity futures dev branch
closed in release v1.3.3 |
Error output:
Specifically it looks like the problem cropped up in
router.get_route
, line 310, when it's used to get VKMT by county for all routes between facilities.This comes from running
master
on the national dataset files packaged with release v1.3.1 (and v1.3.2 - identical datasets).There is a node with ID 122978 at long = -82.505 lat = 35.5868 (see node_locations.csv row 122376). However this node does not show up in the locations_computed file produced from the run that threw the error - unclear if it wasn't processed yet or if the fact it's missing is the problem.
Plan for debugging:
Set up
issue-198
branch to investigate and implement fixRe run with a
set_trace
inget_route
to catch theKeyError
before it stops the code, then investigate further.The text was updated successfully, but these errors were encountered: