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

Remove high_water_threshold filter from RFC FIM processing #761

Merged

Conversation

shawncrawley
Copy link
Collaborator

This solves issue #760.

The three lines removed from rfc_based_5day_max_inundation.sql should have never been in there in the first place. They were added by oversight when refactoring code to use the new FIM Caching mechanism, as these lines are common to all NWM FIM products. However, since this is not a NWM FIM product, we should not be comparing the authoritative flood-status flows (from official RFC forecasts) to NWM recurrence flows.

Refs #760
The three lines removed from rfc_based_5day_max_inundation.sql should have never
been in there in the first place. They were added by oversight when refactoring code
to use the new FIM Caching mechanism, as these lines are common to all NWM FIM
products. However, since this is not a NWM FIM product, we should not be
comparing the authoritative flood-status flows (from official RFC forecasts) to NWM
recurrence flows.
@nickchadwick-noaa nickchadwick-noaa changed the base branch from prod to ti June 6, 2024 18:05
@nickchadwick-noaa nickchadwick-noaa merged commit 24bd2fc into ti Jun 6, 2024
1 check passed
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.

2 participants