home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 662547659

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-662547659 https://api.github.com/repos/pydata/xarray/issues/3245 662547659 MDEyOklzc3VlQ29tbWVudDY2MjU0NzY1OQ== 2448579 2020-07-22T16:17:02Z 2020-07-22T16:17:02Z MEMBER

It seems like general consensus was (please correct me if any of this is wrong):

  1. .values will return np.asarray(obj.data) and respect the underlying library's choices: this will raise an error with cupy and that's OK.
  2. .plot() is a special case and should always coerce to numpy before passing data to matplotlib. plot currently uses .values so we should add a new function that always returns xarray objects with numpy arrays (with cupy as special case) and use that in plot.
  3. for now we are OK with special as_sparse, as_cupy, as_pint methods in xarray as long as all that logic is contained in one place: as_duck_array.py?
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  484240082
Powered by Datasette · Queries took 80.31ms · About: xarray-datasette