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

UZF sometimes does not report UZET > 0 for cases where it seems like UZET should be greater than 0 #1542

Closed
rbwinst-usgs opened this issue Jan 8, 2024 · 1 comment
Labels

Comments

@rbwinst-usgs
Copy link

Describe the bug
In a model where the UZF ET is simulated and the head is below the cell top sometimes UZET is reported as 0 in the UZF budget csv file.

To reproduce
Steps to reproduce the behavior:
The attached file contains two models. The models are identical except that in importedOneTenth, the model top is 0.1 and in Imported1, the model top is 1. The heads in both models are always less than the top of the model by at least 0.1 m. However, the unsaturated zone ET is 0 in importedOneTenth but is greater than 0 in Imported1.

Expected behavior
Both models should have unsaturated zone ET values greater than 0.

imported.zip

@emorway-usgs
Copy link
Contributor

Hello @rbwinst-usgs, I took a look at this model and the UZF parameterization seemed a bit odd. The saturated water content was set to 0.95 with an initial water content of 0.90. As soon as the model is turned loose, this leads to a huge slug of UZ drainage to the saturated zone where the specific yield was specified as 0.2. This then leads to a rather large spike in gw heads well above land surface, and since the unsaturated zone becomes inundated, i.e., there is no unsat zn, there is no UZET. Resetting the UZF parameters to something more reasonable (see attached) seems to have led to the expected behavoir. Let me know if you still see something amiss.
Imported1.uzf.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants