Release v0.1.0: first timflow release!#27
Conversation
- 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
move to one bessel module
- 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
|
@mbakker7, after adding the ttim --> timflow notebook I think this is ready for another check.
|
and update to timflow
For now just 2 examples for confined, leaky, slug test. More to come after first release.
|
I think this is ready to go when all the tests pass. It is time for our first full release! |
|
Readthedocs builds! BUT.
|
|
Figures (static?) are still not showing up in pumping tests readthedocs |
Yeah, trying to figure this one out... |
|
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. |
|
@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. |
|
Alright, images are showing up: https://timflow--27.org.readthedocs.build/en/27/transient/04pumpingtests/confined1_oude_korendijk.html |
|
Any thought on what to do with those three tests for which the status is not reported? |
|
| 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. |
|
github is experiencing some difficulties so these test fails are related to that I think... |
mbakker7
left a comment
There was a problem hiding this comment.
Looks great. Ready to go!
To-do before merging and releasing: