home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

7 rows where author_association = "NONE" and user = 865212 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, created_at (date), updated_at (date)

issue 4

  • Reusing coordinate doesn't show in the dimensions 3
  • (trivial) xarray.quantile silently resolves dask arrays 2
  • open_mfdataset() significantly slower on 0.9.1 vs. 0.8.2 1
  • xarray allows several types for netcdf attributes. Is it expected ? 1

user 1

  • acrosby · 7 ✖

author_association 1

  • NONE · 7 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1267558344 https://github.com/pydata/xarray/issues/7093#issuecomment-1267558344 https://api.github.com/repos/pydata/xarray/issues/7093 IC_kwDOAMm_X85LjWfI acrosby 865212 2022-10-04T20:46:32Z 2022-10-04T20:46:32Z NONE

I believe NetCDF, CF-Conventions, and xarray should all be considered independently. It is not necessarily the responsibility of xarray serialization to ensure a CF-complaint file...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  xarray allows several types for netcdf attributes. Is it expected ? 1388326248
517736527 https://github.com/pydata/xarray/issues/1499#issuecomment-517736527 https://api.github.com/repos/pydata/xarray/issues/1499 MDEyOklzc3VlQ29tbWVudDUxNzczNjUyNw== acrosby 865212 2019-08-02T15:08:24Z 2019-08-02T15:08:24Z NONE

I think I side with @jhamman now on this issue. Labeled access to this kind of dataarray and broadcasting operations are not useful in my cases, and working in straight numpy or pandas ends up making more sense. We just drop the appropriate variables upon opening the relevant files.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Reusing coordinate doesn't show in the dimensions 247697176
405990579 https://github.com/pydata/xarray/issues/1524#issuecomment-405990579 https://api.github.com/repos/pydata/xarray/issues/1524 MDEyOklzc3VlQ29tbWVudDQwNTk5MDU3OQ== acrosby 865212 2018-07-18T16:20:38Z 2018-07-18T16:20:38Z NONE

Thanks @shoyer I had forgotten that the dask implementation has its own problems anyway.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  (trivial) xarray.quantile silently resolves dask arrays 252548859
404613718 https://github.com/pydata/xarray/issues/1524#issuecomment-404613718 https://api.github.com/repos/pydata/xarray/issues/1524 MDEyOklzc3VlQ29tbWVudDQwNDYxMzcxOA== acrosby 865212 2018-07-12T18:51:42Z 2018-07-12T18:55:11Z NONE

Now that SciPy is going on, is there any momentum here for trying to add the dask implementation in someway? This is an issue for some of our workloads, would be great if someone was looking into it or could point me in the direction to start adapting the current source to support it.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  (trivial) xarray.quantile silently resolves dask arrays 252548859
326286406 https://github.com/pydata/xarray/issues/1499#issuecomment-326286406 https://api.github.com/repos/pydata/xarray/issues/1499 MDEyOklzc3VlQ29tbWVudDMyNjI4NjQwNg== acrosby 865212 2017-08-31T12:54:22Z 2017-08-31T12:54:22Z NONE

@jhamman I'm interested in helping, but I definitely can't be timely unless we can get a project here at work that I can leverage for time. What were you thinking for test coverage?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Reusing coordinate doesn't show in the dimensions 247697176
324975826 https://github.com/pydata/xarray/issues/1499#issuecomment-324975826 https://api.github.com/repos/pydata/xarray/issues/1499 MDEyOklzc3VlQ29tbWVudDMyNDk3NTgyNg== acrosby 865212 2017-08-25T16:49:07Z 2017-08-25T16:49:07Z NONE

This is important for some of my use cases, it's something we do a lot--as noted it is not forbidden by the netcdf format or CF standards.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Reusing coordinate doesn't show in the dimensions 247697176
293593843 https://github.com/pydata/xarray/issues/1301#issuecomment-293593843 https://api.github.com/repos/pydata/xarray/issues/1301 MDEyOklzc3VlQ29tbWVudDI5MzU5Mzg0Mw== acrosby 865212 2017-04-12T14:24:44Z 2017-04-12T14:25:29Z NONE

@friedrichknuth Did you try tests with the most recent version decode_times=True/False on a single file read?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  open_mfdataset() significantly slower on 0.9.1 vs. 0.8.2 212561278

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);
Powered by Datasette · Queries took 558.701ms · About: xarray-datasette