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

[8pt] Leveed area being inundated by branch #1021

Closed
CarsonPruitt-NOAA opened this issue Oct 31, 2023 · 1 comment · Fixed by #1059
Closed

[8pt] Leveed area being inundated by branch #1021

CarsonPruitt-NOAA opened this issue Oct 31, 2023 · 1 comment · Fixed by #1059
Assignees
Labels
bug Something isn't working FIM4

Comments

@CarsonPruitt-NOAA
Copy link
Collaborator

HUC 01080205 branch 7703000014 is inundating behind a levee system in Hartford, CT.

Image

@CarsonPruitt-NOAA CarsonPruitt-NOAA added the bug Something isn't working label Oct 31, 2023
@mluck mluck self-assigned this Dec 26, 2023
@mluck mluck added the FIM4 label Dec 28, 2023
@mluck
Copy link
Contributor

mluck commented Dec 28, 2023

src/mask_dem.py has been modified so that a levelpath that crosses through a levee-protected area is only able to inundate the levee-protected area within the catchment of the levelpath (not the entire levee-protected area). Compared with the initial image in this issue, the image below shows branch inundation only within the levelpath catchment (highlighted in yellow), resulting in much less inundation in the levee-protected area. Note that the levee-protected areas upstream of the levelpath are completely masked as they are outside of the levelpath catchment, but this is consistent with the fact that we mask branch 0. Inundation is based on 100yr recurrence flows.
image

A closer view of the branch inundation (blue) in the levelpath catchment (yellow) in the levee-protected area (dotted).
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working FIM4
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants