Skip to content

Release v0.1.0: first timflow release!#27

Merged
dbrakenhoff merged 68 commits intomainfrom
dev
Feb 10, 2026
Merged

Release v0.1.0: first timflow release!#27
dbrakenhoff merged 68 commits intomainfrom
dev

Conversation

@dbrakenhoff
Copy link
Contributor

@dbrakenhoff dbrakenhoff commented Jan 30, 2026

To-do before merging and releasing:

  • fix docs timeout

dbrakenhoff and others added 30 commits January 29, 2026 10:46
- use this bessselnumba module everywhere.
- move bessel tests to test root dir
- make steady/transient versions inherit from base
- fix all plotting to accept axes
- add layer kwarg to all element plot funcs
 - rename ttim -> timflow/timflow.transient
 - rename timml to timflow/timflow.steady
- move some stuff
- add docstrings
- rename timml and ttim
- modify imports to fs and ft
- move about section
- improve ttim docs structure
- apply new plotting everywhere
- add logo
- rename example output figures
- update ci
- new xsections section for timflow.transient
- add sep argument for plotting parameters in cross-section on same line or separated by newlines
- improve plotting of hstar for transient models
- add inhomogeneity names option for cross-section models
- add support for plotting capzones for multiple wells at once.
- add support for plotting capzones based on well names
@dbrakenhoff
Copy link
Contributor Author

@mbakker7, after adding the ttim --> timflow notebook I think this is ready for another check.

  • I updated all element names:
    • DitchLineSink --> Ditch
    • HeadLineSink --> River
    • LeakyLineDoublet --> LeakyWall
    • ImpLineDoublet --> ImpermeableWall
  • update all import statements to use either tfs or tft
  • remove bessel docs and move the bessel notebook to benchmarks
  • make the other bessel test notebook part of the test suite, and generated new data with the current set of bessel functions as benchmark data.
  • improved plotting further
  • add option to pass multiple wells to plot capture zones, and allow wells to be referenced by label instead of passing in the well object.

@mbakker7
Copy link
Contributor

mbakker7 commented Feb 9, 2026

I think this is ready to go when all the tests pass. It is time for our first full release!

@mbakker7
Copy link
Contributor

mbakker7 commented Feb 9, 2026

Readthedocs builds! BUT.
What still goes wrong in the readthedocs:

  1. For all 6 pumping test examples, the figure doesn't show up. Probably some wrong reference thing. Run fine locally.
  2. Two synthetic pumping tests are now moved to the benchmark tab. They have new names that don't start with a number anymore, but in the lists and in the TOC they still have a preceding number. Very odd. Seems like it is cached somewhere.

@mbakker7
Copy link
Contributor

mbakker7 commented Feb 9, 2026

Figures (static?) are still not showing up in pumping tests readthedocs

@dbrakenhoff
Copy link
Contributor Author

Figures (static?) are still not showing up in pumping tests readthedocs

Yeah, trying to figure this one out...

@mbakker7
Copy link
Contributor

mbakker7 commented Feb 9, 2026

We read and show the neuman.png figure in one of the benchmark problems. We use matplotlib to show it. That could be a work-around.

@mbakker7
Copy link
Contributor

mbakker7 commented Feb 9, 2026

@dbrakenhoff, since you are looking into this. Any reason the outcome of the final three checks is not reported?

@dbrakenhoff
Copy link
Contributor Author

@dbrakenhoff, since you are looking into this. Any reason the outcome of the final three checks is not reported?

This seems to be something odd that is maybe related to modifying the github workflow files. I was hoping this would disappear on merge to main :). If not, I think I'll have to add and remove all the status checks in github settings somewhere.

@dbrakenhoff
Copy link
Contributor Author

@mbakker7
Copy link
Contributor

mbakker7 commented Feb 9, 2026

Any thought on what to do with those three tests for which the status is not reported?

@dbrakenhoff
Copy link
Contributor Author

| Any thought on what to do with those three tests for which the status is not reported?

Merge first, then see if they still exist on a next PR. I have been messing with the github action workflows a bit so maybe it's still remembering something from before. So hopefully it resolves itself, otherwise I can try to remove the status checks and add them again. But let's see if it just resolves itself first.

@dbrakenhoff
Copy link
Contributor Author

github is experiencing some difficulties so these test fails are related to that I think...

Copy link
Contributor

@mbakker7 mbakker7 left a comment

Choose a reason for hiding this comment

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

Looks great. Ready to go!

@dbrakenhoff dbrakenhoff merged commit cc687b7 into main Feb 10, 2026
23 of 24 checks passed
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