8000 Regularization weight factor (wfmin/wfinit) · Issue #591 · pypest/pyemu · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Regularization weight factor (wfmin/wfinit) #591

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

Open
VirkNu opened this issue May 8, 2025 · 1 comment
Open

Regularization weight factor (wfmin/wfinit) #591

VirkNu opened this issue May 8, 2025 · 1 comment

Comments

@VirkNu
Copy link
VirkNu commented May 8, 2025

This is not so much a pyemu question and more a general PEST question, But I don't know anyone else to ask.

I have a highly parameterized groundwater model and I do parameter estimation in PEST++ with preferred homogeneity regularization. According to what I’ve read (Pest manual, roadmaps etc.) the best practice is, in short, to run the inversion with a low PHIMLIM/PHIMACCEPT first and then increase the two iteratively until parameters are realistic and the fit is ok.

After doing this I reached a PHIMLIM that I feel should be obtainable without unrealistic parameters, but PEST would still reduce the regularization weight factor and reach my target PHI in a few iterations while giving me weird parameter values.

So as an experiment I tried to keep my PHIMLIM/ACCEPT at the level I felt should be obtainable, but increased my starting weight factor (WFINIT) and minimum weight factor (WFMIN) to enforce a higher level of regularization.

This took PEST a lot more iterations and it tried to transgress the lower WFMIN limit, but it reached the acceptable PHI and the parameter values were okay.

So my question is what do I miss out on by doing it the “experimental way” rather than the best practice. Is it problematic and why?

Cheers Kim

@jtwhite79
Copy link
Collaborator

the dynamic regularization solve is some tricky business and I think the "regularization continue" option in pest_hp might be to help with this issue. I wonder if you take some smaller steps on the way to phimlim if that might help? So maybe a larger eigthresh and/or larger lambda values so slow down the first couple of upgrades since, in many cases, that first upgrade can be pretty aggressive...

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

No branches or pull requests

2 participants
0