|
1 | 1 | # todo |
2 | 2 |
|
3 | | -## perf |
| 3 | +- deduplicate data trees |
4 | 4 |
|
5 | | -### memory |
6 | | - |
7 | | -Need to deduplicate data trees. |
8 | 5 | Each component should get a view into the root (as far as it's aware) tree |
9 | 6 | unless it's the root (i.e. simulation) itself, or it's not attached to any |
10 | 7 | parent context, in which case it's the root of its own tree. |
11 | 8 |
|
12 | | -### speed |
13 | | - |
14 | | -Need faster dimension resolution. |
15 | | -We know the path from simulation to dis and tdis, no reason to search for it. |
16 | | - |
17 | | -## api |
18 | | - |
19 | | -### components |
| 9 | +- subcomponent accessors |
20 | 10 |
|
21 | 11 | I think for access by name we want dict style e.g. `gwf["chd1"]`, |
22 | | -like imod-python does it. |
| 12 | +like imod-python does it? |
23 | 13 |
|
24 | 14 | By type, e.g. `gwf.chd`, where it's either a single component, |
25 | 15 | or a dict by name (or auto-increment index) for multipackages? |
26 | 16 |
|
27 | | -## docs |
28 | | - |
29 | | -Reproduce flopy3 quickstart. |
30 | | -Keep it minimal, just show an equivalent with the prototype. |
| 17 | +- first class dimension support |
31 | 18 |
|
32 | | -More detailed demo notebook. |
33 | | -Compare/contrast implementations and different patterns in |
34 | | -more detail. |
| 19 | +Right now array variables just declare their expected dimension. And the |
| 20 | +dimensions are looked up by unguided search across the data tree's vars, |
| 21 | +from the root down. Let variables declare themselves as dimensions? With |
| 22 | +optional coordinate arrays autogenerated in the right size and added to |
| 23 | +the dataset? And allow local vs global dimensions? |
0 commit comments