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

fix HantushWellModel #313

Merged
merged 3 commits into from
Aug 30, 2021
Merged

fix HantushWellModel #313

merged 3 commits into from
Aug 30, 2021

Conversation

dbrakenhoff
Copy link
Member

@dbrakenhoff dbrakenhoff commented Aug 19, 2021

Short Description

  • Add support in HantushWellModel.get_tmax() for when k0rho --> 0.0 to return large response time (100 yrs), instead of np.inf.
  • Relax upper bound for parameter b in HantushWellModel. Bounds used to be scaled with max distance between well and oseries, now the upper bound uses minimum distance instead.

This should allow wells at large distances to be added without constraining parameter b by those large distances.

Question: Is 100 years a reasonable large number, or too large?

Checklist before PR can be merged:

  • closes issue
  • is documented internal change
  • PEP8 compliant code
  • tests passed
  • Example Notebook (for new features)
  • API changes documented in Release Notes

- add option if k0rho -> 0 to return a large number (100 yrs)
- this should allow relaxing of parameter bounds for b
@dbrakenhoff
Copy link
Member Author

Just had a thought we could also maybe solve this with maxtmax in get_t(). I'll take a look...

@dbrakenhoff
Copy link
Member Author

The thought was wrong. So no changes.

@raoulcollenteur raoulcollenteur merged commit 40d1366 into dev Aug 30, 2021
@raoulcollenteur raoulcollenteur deleted the hantushwm branch August 30, 2021 13:03
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.

None yet

2 participants