home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

8 rows where issue = 578427969 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

  • aaronspring 4
  • pgierz 3
  • dcherian 1

author_association 3

  • CONTRIBUTOR 4
  • NONE 3
  • MEMBER 1

issue 1

  • Custom Table when opening GRIB Files · 8 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1110774460 https://github.com/pydata/xarray/issues/3853#issuecomment-1110774460 https://api.github.com/repos/pydata/xarray/issues/3853 IC_kwDOAMm_X85CNRK8 aaronspring 12237157 2022-04-27T09:24:36Z 2022-04-27T09:24:36Z CONTRIBUTOR

It is possible to set ECCODES_DEFINITION_PATH in eccodes, see http://download.ecmwf.int/test-data/eccodes/html/namespaces.html. But the codetab you want to use here from MPIESM grb output is a CDO parameter table, see https://code.mpimet.mpg.de/projects/cdo/embedded/cdo.pdf#section.1.8, so in my understanding something CDO internal and likely not usable with eccodes/cfgrib.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
598035966 https://github.com/pydata/xarray/issues/3853#issuecomment-598035966 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5ODAzNTk2Ng== aaronspring 12237157 2020-03-12T06:58:55Z 2020-03-12T06:58:55Z CONTRIBUTOR

This was my workaround. https://github.com/aaronspring/pymistral/issues/19

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
598035459 https://github.com/pydata/xarray/issues/3853#issuecomment-598035459 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5ODAzNTQ1OQ== pgierz 2444231 2020-03-12T06:57:01Z 2020-03-12T06:57:01Z NONE

Me too! Then we have a good test case :-)

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
598031406 https://github.com/pydata/xarray/issues/3853#issuecomment-598031406 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5ODAzMTQwNg== aaronspring 12237157 2020-03-12T06:41:40Z 2020-03-12T06:41:40Z CONTRIBUTOR

I would use it with the echam6 and jsbach ‘.codes’ files in MPIESM.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
598020815 https://github.com/pydata/xarray/issues/3853#issuecomment-598020815 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5ODAyMDgxNQ== pgierz 2444231 2020-03-12T05:59:51Z 2020-03-12T05:59:51Z NONE

I can have a look at implementing this. Might be a nice opportunity to actually contribute to some of the packages I use every day ;-)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
597939300 https://github.com/pydata/xarray/issues/3853#issuecomment-597939300 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5NzkzOTMwMA== aaronspring 12237157 2020-03-12T00:02:35Z 2020-03-12T00:02:35Z CONTRIBUTOR

I would love that feature. Also found that pyngl docu but didn’t get it working...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
597491042 https://github.com/pydata/xarray/issues/3853#issuecomment-597491042 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5NzQ5MTA0Mg== pgierz 2444231 2020-03-11T07:50:43Z 2020-03-11T07:50:43Z NONE

Apparently this is possible by setting an environmental variable: http://www.pyngl.ucar.edu/NioFormats.shtml#GRIB1-user-defined-parameter-tables

So, if I have my codetable at /path/to/codetab; I can set NIO_GRIB_PTABLE_PATH=/path/to/codetab. I'm honestly not too happy with this solution. Would it be possible to add something like backend_env to open_dataset; where I can specify environmental variables that are active during opening, and then restore the environment afterwards?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969
596984913 https://github.com/pydata/xarray/issues/3853#issuecomment-596984913 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5Njk4NDkxMw== dcherian 2448579 2020-03-10T09:24:50Z 2020-03-10T09:24:50Z MEMBER

Is there a way to tell pynio to use a specific file?

If so, something like xr.open_dataset("/path/to/file.grb", engine="pynio", backend_kwargs=dict(code_table="/path/to/codetab")) should work

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Custom Table when opening GRIB Files 578427969

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 14.12ms · About: xarray-datasette