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/source/api_reference.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,17 +65,17 @@ The user can now plot the time series for a given location and times, without ha
65
65
Duck Typing
66
66
-----------
67
67
68
-
The Grid objects (Grid, Time, Depth) are for the most part "duck typed", rather than strict subclassing. Though there are base classes that provide shared functionality.
68
+
The Grid objects (Grid, Time, Depth) are for the most part "duck typed", rather than strict subclassing, though there are base classes that provide shared functionality.
69
69
70
-
We are trying to be clear about the "public" vs "private" API by using leading underscores for methods and attributes not intended for external use.
70
+
We are trying to be clear about the "public" vs "private" API by using leading underscores for methods and attributes not intended for external use, but it's not as consitent as it should be.
71
71
72
72
73
73
Lazy loading / data arrays
74
74
--------------------------
75
75
76
76
Many of the datasets users need to work with can be quite large. As a result it is impractical to load entire datasets into memory at once. ``gridded`` for the most part shifts the burden of handling lazy loading to external libraries, and does this by keeping data stored in a "numpy array-like" objects. Users can use pure numpy arrays, or any object that "acts" like a numpy array. This should allow ``gridded`` to work with netcdf variables, hdf5 arrays, dask arrays, etc.
77
77
78
-
In practice, there is no clear definition of "array-like", so ``gridded`` has defined its own definition, based on features we know we need. But it is assumed that nd indexing behaves that same as numpy arrays -- as there is no way to easily confirm that. This is a goal, but in fact, only numpy arrays and ``netCDF4 Variables`` have been implimented and tested. In the future, we may use ``xarray`` as a single abstration layer, rather than rolling our own.
78
+
In practice, there is no clear definition of "array-like", so ``gridded`` has defined its own definition, based on features we know we need. But it is assumed that nd indexing behaves that same as numpy arrays -- as there is no way to easily confirm that. This is a goal, but in fact, only numpy arrays and ``netCDF4 Variables`` have been implemented and tested. In the future, we may use ``xarray`` as a single abstraction layer, rather than rolling our own.
79
79
80
80
To support that, we support converting and testing for array-like with:
81
81
@@ -85,7 +85,7 @@ and
85
85
86
86
``gridded.utils.isarraylike()``
87
87
88
-
Those utilities will be updated as new needs arrise.
88
+
Those utilities will be updated as new needs arise.
0 commit comments