issues: 500949040
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 500949040 | MDU6SXNzdWU1MDA5NDkwNDA= | 3361 | Recommendations for domain-specific accessor documentation | 1956032 | closed | 0 | 6 | 2019-10-01T14:48:39Z | 2020-08-09T22:45:48Z | 2020-08-09T22:45:48Z | CONTRIBUTOR | Hi, I'm currently working on an ocean domain specific accessor for a machine learning technique (https://github.com/gmaze/pyxpcm/tree/nfeatures). I thus wonder whether the xarray/pangeo community has recommendations about how to do this appropriately ? Right now, I simply have an API auto-generated page, see: https://pyxpcm-dev.readthedocs.io/en/latest/api.html#xarray-dataset-accessor-the-pyxpcm-name-space |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3361/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |