home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 554795681

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/3245#issuecomment-554795681 https://api.github.com/repos/pydata/xarray/issues/3245 554795681 MDEyOklzc3VlQ29tbWVudDU1NDc5NTY4MQ== 6815844 2019-11-17T22:38:51Z 2019-11-17T22:38:51Z MEMBER

Do we arrive at the consensus here for API to change the sparse or numpy array? xref #3542

To make it sparse array, to_sparse() would be better? How about or as_sparse()? + to_sparse() is probably consistent to todense() method + as_sparse() sounds similar to sparse's function, e.g. sparse.as_coo

To change the backend back from sparse array, to_dense() would be better? FYI, sparse uses todense().

I personally like as_sparse or as_numpy (or as_dense?), which sounds similar to as_type, which gives xarray object not dtype itself.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  484240082
Powered by Datasette · Queries took 0.5ms · About: xarray-datasette