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

KeyError: (0,0,0) in setup_spnetwork() #36

Closed
Gyrolyn opened this issue Jul 11, 2023 · 5 comments
Closed

KeyError: (0,0,0) in setup_spnetwork() #36

Gyrolyn opened this issue Jul 11, 2023 · 5 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@Gyrolyn
Copy link

Gyrolyn commented Jul 11, 2023

hello guys and thank you for making this code this is a problem i'm having for a project i'm importing a small network from pyrosm and trying to use UE on it but it gives keyerror: (0,0,0) to me
issue report.zip

@jdlph
Copy link
Owner

jdlph commented Jul 11, 2023

Thank you for reporting this issue! Please include a screenshot of the error from your terminal along with the version number of Path4GMNS for this particular run.

@Gyrolyn
Copy link
Author

Gyrolyn commented Jul 12, 2023

i'm using jupyter notebook but i have added a screenshot of output error in zip file

@jdlph
Copy link
Owner

jdlph commented Jul 15, 2023

The current implementation of setup_spnetwork() in class Assignment requires the zone id's to be consecutive integers. This is one of the known issues. For the time being, you may want to change the zone ids in node.csv and demand.csv according to the aforementioned requirement.

I will leave this issue open until a permanent fix is developed.

@jdlph jdlph added bug Something isn't working enhancement New feature or request labels Jul 15, 2023
@jdlph jdlph changed the title key error: (0,0,0) KeyError: (0,0,0) in setup_spnetwork() Jul 15, 2023
@jdlph
Copy link
Owner

jdlph commented Jul 15, 2023

The issue has been fixed under 8b9aff4. This fix simply drops the consecutive requirement but still needs the zone id's to be integers. It will be included in the next release (i.e., v0.9.4).

I attached the screenshot of a smooth run by executing your script after this fix for your reference. Thank you again for reporting this issue!

image

@jdlph jdlph closed this as completed Jul 15, 2023
@jdlph
Copy link
Owner

jdlph commented Aug 16, 2023

v0.9.5 further drops the previous requirement that the zone id's to be integers. Now zone id's can be any arbitrary values. Detailed update can be found under cce76e6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants