You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/md/models.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# Models API
2
2
3
-
The `modflow_devtools.models` module provides programmatic access to MODFLOW 6 example models via [Pooch](https://www.fatiando.org/pooch/latest/index.html).
3
+
The `modflow_devtools.models` module provides programmatic access to MODFLOW 6 example models via a `Models` registry class. There is one "official" registry, aimed at users and developers — developers may create additional instances e.g. to load models from the local filesystem.
4
+
5
+
This module leans heavily on [Pooch](https://www.fatiando.org/pooch/latest/index.html), but it has strong opinions about how to train (configure) it.
4
6
5
7
## Listing models
6
8
@@ -51,7 +53,7 @@ with TemporaryDirectory() as td:
51
53
52
54
If the target directory doesn't exist, it will be created.
53
55
54
-
## Developers
56
+
## Creating a registry
55
57
56
58
The `make_registry.py` script is responsible for generating a registry text file and a mapping between files and models. This script should be run in the CI pipeline at release time before the package is built. The generated registry file and model mapping are used to create a pooch instance for fetching model files, and should be distributed with the package.
0 commit comments