-
Notifications
You must be signed in to change notification settings - Fork 0
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
Run sgeop #189
Run sgeop #189
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These parenx
differences are wild. Is that maybe due to the input data for parenx
still having the service roads?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, i think so. we have an open issue about re-running parenx #130 so i hope this will be fixed by that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(and the evaluation notebook is still under construction, for now i only updated some variable names but have not changed much about the underlying analysis, separate PR will follow for that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we handle #130 prior this PR? Or simply rerun this notebook again in another PR after that PR?
I started typing this before reading your message above.
resolves #183