-
Notifications
You must be signed in to change notification settings - Fork 16
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
Faces and centers #73
Comments
Yep, doing the rename makes sense. |
Thanks @ayan-usgs! FYI I am experimenting a new API and ways to make all slices and computations lazy: http://nbviewer.jupyter.org/gist/ocefpaf/28d9279479022454bb99 It is not ideal yet because of a masking issue. If I can figure that out things will be much easier for sci-wms. |
Can you cross- reference the PR that did the rename? I am a bit lost. |
The rename happened in #72. The variables were named |
I |
Sorry. Didn't totally re-read the question... 😭 |
@ayan-usgs, when browsing the namespace one can easily find everything that is related to nodes with
sgrid.node<tab>
(sgrid.node_coordinates
,sgrid.node_dimensions
,sgrid.node_lon
,sgrid.node_lat
, andsgrid.node_padding
). However, when doing the same for the center we only findsgrid.center_lon
andsgrid.center_lat
.Does it make sense to rename the
sgrid.face_{coordinate, dimensions, padding}
tosgrid.center_{coordinate, dimensions, padding}
? Note thatsgrid.faces
is always none!The text was updated successfully, but these errors were encountered: