Skip to content

Do not set meteorological data to 0 at lakes anymore#514

Merged
rubencalje merged 4 commits intodevfrom
Do-not-set-meteorological-data-to-0-at-lakes-anymore
Nov 18, 2025
Merged

Do not set meteorological data to 0 at lakes anymore#514
rubencalje merged 4 commits intodevfrom
Do-not-set-meteorological-data-to-0-at-lakes-anymore

Conversation

@rubencalje
Copy link
Collaborator

@rubencalje rubencalje commented Sep 18, 2025

This fixes issue #497.
This PR adds the method copy_meteorological_data_from_ds which does not set the meteorological data in ds at the lake-locations to 0 anymore. The method clip_meteorological_data_from_ds is still available for backwards compatibility, but a warning is shown to the user, that this method is deprecated.

This change is only important when lakes fall dry, as MODFLOW 6 sets the evaporation and precipitation from the RCH and EVT packages to 0 in cells below active lakes already. When this data is set to 0 in the model dataset as well, there is no rainfall or evaporation applied to the cell when the lake falls dry, which is not what we want.

@rubencalje rubencalje requested a review from OnnoEbbens October 8, 2025 13:51
@github-project-automation github-project-automation bot moved this from Todo to In Progress in NHFLO Oct 9, 2025
@rubencalje
Copy link
Collaborator Author

Tests fail unrelated to this PR

@rubencalje rubencalje merged commit 4ea4795 into dev Nov 18, 2025
2 of 3 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in NHFLO Nov 18, 2025
@rubencalje rubencalje deleted the Do-not-set-meteorological-data-to-0-at-lakes-anymore branch December 17, 2025 11:22
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