-
Notifications
You must be signed in to change notification settings - Fork 5
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
Models API #134
Comments
A simple proof of concept is available here: https://github.com/wpbonelli/modflow-devtools/tree/models-api If this seems worthwhile, flopy may be a better place for it because the API
|
I think we can build a registry in release time CI, release it with the package, and then devtools can provide access to models in
..without moving the input files here. This would also work for flopy example data. Though at some point it is probably still worth considering defining all examples in flopy python code, at which point it probably makes more sense to move this there. |
First draft of #134. API dynamically generated from a pooch registry. Alongside the registry a TOML file mapping model names to the set of model input files. These can be built and distributed with the package at release time. Then model input files can be downloaded at runtime. This approach gives us the flexibility to support input files stored anywhere on GitHub, e.g. in the test models repos. It does not provide access to models defined with flopy, since this package does not depend on flopy.
This will deprecate the test models fixtures when we have it. |
Demo programmatic access to example data/models via https://github.com/fatiando/pooch.
This could be convenient for
The text was updated successfully, but these errors were encountered: