home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 717266102

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/4541#issuecomment-717266102 https://api.github.com/repos/pydata/xarray/issues/4541 717266102 MDEyOklzc3VlQ29tbWVudDcxNzI2NjEwMg== 14314623 2020-10-27T14:03:34Z 2020-10-27T14:03:34Z CONTRIBUTOR

Thanks @mathause , I was wondering how much of a performance trade off .fillna(0) is on a dask array with no nans, compared to the check.

I favor this, since it allows slicing before the calculation is triggered: I have a current situation where I do a bunch of operations on a large multi-model dataset. The weights are time and member dependent and I am trying to save each member separately. Having the calculation triggered for the full dataset is problematic and fillna(0) avoids that (working with a hacked branch where I simply removed the check for nans)

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