-
Notifications
You must be signed in to change notification settings - Fork 92
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
FATES-Hydro fails upon restart when using alternate soil water transfer functions #1157
Comments
@jennykowalcz the fact that it is not crashing on the prior line might indicate that it is a problem for the site_hydr%rootuptake_sl on the soil levels below nlevsoil? Does it still crash if you change it to:
|
@ckoven Good idea! I just tried this but unfortunately it still crashes upon restart with the same error. |
Commenting to clarify that so far I have only encountered this error in drier regions outside of the Amazon Basin. |
Quickly tried a couple of alternate soil water transfer functions with PR 1164 and I have not encountered this restart issue. With Van Genuchten the simulation ran successfully. With "smooth1_campbell_type" it crashed around 12 years (not upon restart) with an error about FATES_ROOTWGT_SOILMATPOT. I don't think we need to worry about this since this PR is working fine with the default hard-coded soil water transfer function, but just documenting for the record. Closing this issue since the restart error appears to be resolved. |
Hi all! I have been trying FATES-Hydro no-comp pan-Amazon simulations with 2 evergreen PFTs. After encountering this error I have been trying runs with alternate soil water transfer functions (specifically, smooth1_campbell_type and van_genuchten_type), but this seems to make FATES-Hydro fail upon restart.
This appears to be separate from the other FATES-Hydro restart error (issue 1151) and is not fixed by the related PR (1156). I also get this error when using the hydro stability PR.
The error message is pointing here where the root water uptake rate is calculated.
The text was updated successfully, but these errors were encountered: