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

Fix/noise zones #450

Merged
merged 5 commits into from
Apr 25, 2022
Merged

Fix/noise zones #450

merged 5 commits into from
Apr 25, 2022

Conversation

johpiip
Copy link
Contributor

@johpiip johpiip commented Mar 14, 2022

Fixes #449

@johpiip johpiip requested a review from zptro March 14, 2022 12:44
Copy link
Collaborator

@zptro zptro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem could be solved by setting traffic to at least 0.01 here:

traffic = sum([link[mode] for mode in self.light_modes])

instead of here:

traffic = max(traffic, 0.01)

Then cross_traffic would also be at least 0.01, which would prevent noise from going below zero.

Scripts/utils/calc_noise.py Outdated Show resolved Hide resolved
@johpiip
Copy link
Contributor Author

johpiip commented Apr 4, 2022

Nice! I forgot about this when I had to hurry assessments but great that you did not. :) Should we make a test run or did you do that already?

@zptro
Copy link
Collaborator

zptro commented Apr 4, 2022

Nice! I forgot about this when I had to hurry assessments but great that you did not. :) Should we make a test run or did you do that already?

Yes, we should probably do a 2040 test run.

@johpiip
Copy link
Contributor Author

johpiip commented Apr 14, 2022

@zptro I tested this and it works! Those links which had a noise zone width of 5 still have it. Ve0 scenario does not crash when writing links.

@zptro zptro merged commit 4262eac into olusanya Apr 25, 2022
@zptro zptro deleted the fix/noise-zones branch April 25, 2022 07:35
johpiip added a commit that referenced this pull request Jul 5, 2022
* Fix/noise zones (#450)

* Print nodes to better debug errors

* Print 5 meter noise buffers for negative values

* Set `cross_traffic` minimum value to 0.01

* Add error message

* Revert zone width change

Co-authored-by: Jens West <jens.west@hsl.fi>

* Update `HELMET_VERSION` (#451)

* Speed up histogram incrementation by changing lookup method (#452)

* Fix floating-point number error (#455)

Co-authored-by: Jens West <jens.west@hsl.fi>
johpiip added a commit that referenced this pull request Sep 25, 2022
* Fix/noise zones (#450)

* Print nodes to better debug errors

* Print 5 meter noise buffers for negative values

* Set `cross_traffic` minimum value to 0.01

* Add error message

* Revert zone width change

Co-authored-by: Jens West <jens.west@hsl.fi>

* Update `HELMET_VERSION` (#451)

* Speed up histogram incrementation by changing lookup method (#452)

* Fix floating-point number error (#455)

* Fix bicycle trips CBA (#463)

Fix incorrect linking of bicycle trips in CBA Excel sheet that causes travel time saving of leisure trips being calculated based on work trips data.

* Remove hard-coded area-based bounds from `Purpose` (#459)

* Remove hard-coded area-based bounds from `Purpose`

Introduce more general sub-bounds that can define separate parameters
for arbitrary number of sub-regions instead of two

* Generalize transit trips per month accordingly

* Add helpful comment

Co-authored-by: Jens West <jens.west@hsl.fi>
Co-authored-by: Sami Mäkinen <47142755+samakinen@users.noreply.github.com>
Co-authored-by: Jens West <jens.west@traficom.fi>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Modeller exception: LinkPrinting run ended with exception
2 participants