wpbonelli
wpbonelli
@aestrad-intera to clarify how to reproduce this, could you pull the develop branch and have a look at the test I added in #2532? The only difference I see is...
yeah, disv/u weren't covered. sorry @aestrad-intera we are discovering the state of all this as we go. does #2566 solve it for you?
@aestrad-intera please reopen if this does not solve the issue for you
Is it possible for you to share your model so we can reproduce the exact issue you're seeing?
@aestrad-intera any luck with @jlarsen-usgs's suggestion? and/or can you share a model we can reproduce this with?
@dannbuckley Thanks for this. Agreed that the mapping between the MF6 input spec and the Python/FloPy equivalent is not always clear. Your timing is excellent, we have just begun to...
@dannbuckley we are working on an `attrs`-based prototype right this moment, in fact!
do you mind editing the issue title? maybe "type hints for input specifications" or something reflecting the more general utility of typing annotations
@dannbuckley I had an initial look at how we might generate named tuples alongside the components they appear in and substitute them into docstrings and typehints, I think your suggestion...
I think merging those PRs auto-closed this, sorry @dbrakenhoff