Skip to content

Head in leaky layer - #74

Merged
mbakker7 merged 34 commits into
devfrom
head_in_leaky_layer
Sep 7, 2026
Merged

mbakker7 merged 34 commits into
devfrom
head_in_leaky_layer

Conversation

@mbakker7

Copy link
Copy Markdown
Contributor

Compute variation of head in leaky layers through time. Include influx from overlying and underlying aquifers and loading efficiency.

Base automatically changed from dev to main June 26, 2026 07:52
@mbakker7
mbakker7 changed the base branch from main to dev August 31, 2026 08:58
@dbrakenhoff

Copy link
Copy Markdown
Contributor

Was this ready for review @mbakker7 ?

@dbrakenhoff dbrakenhoff mentioned this pull request Sep 2, 2026
4 of 5 tasks
@mbakker7

mbakker7 commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

Ready to review now!

@mbakker7
mbakker7 requested a review from dbrakenhoff September 5, 2026 18:00
Comment thread timflow/transient/model.py Outdated
Comment thread timflow/transient/model.py
h += htimml[:, np.newaxis]
return h

def headinvertical(self, x, y, z, t, aq=None, returneta=False):

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess timflow currently uses a lot of headinvertical and headalongline naming styles. Just wondering out loud here whether we want to continue this trend, or move to a slightly longer but more legible style: head_in_vertical, head_along_line, etc. Maybe something for a separate issue (or a 1.0 version ... 😇 ).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was (am) not very fond of underscores, but function and variable names sometimes get long and unreadable. And it seems that a more accepted style is to have underscores. So indeed something we may want to revisit when we are approaching 1.0.

@dbrakenhoff dbrakenhoff left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very cool! And looks good to me. I made two small (style/typo) changes, and asked a few general questions, but otherwise, fine to merge!

@dbrakenhoff
dbrakenhoff marked this pull request as ready for review September 7, 2026 09:25
@mbakker7
mbakker7 merged commit be67292 into dev Sep 7, 2026
11 checks passed
@mbakker7
mbakker7 deleted the head_in_leaky_layer branch September 7, 2026 19: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