home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

10 rows where author_association = "MEMBER" and user = 1839645 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 3

  • DataArray creation prone to errors when data shares dimension shapes 5
  • DOC: from examples to tutorials 3
  • Html repr 2

user 1

  • choldgraf · 10 ✖

author_association 1

  • MEMBER · 10 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1439022617 https://github.com/pydata/xarray/issues/3564#issuecomment-1439022617 https://api.github.com/repos/pydata/xarray/issues/3564 IC_kwDOAMm_X85Vxb4Z choldgraf 1839645 2023-02-21T20:01:04Z 2023-02-21T20:01:04Z MEMBER

Oops I think the url just changed

https://chrisholdgraf.com/blog/2019/2019-10-22-xarray-neuro/

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DOC: from examples to tutorials 527323165
565605904 https://github.com/pydata/xarray/issues/3564#issuecomment-565605904 https://api.github.com/repos/pydata/xarray/issues/3564 MDEyOklzc3VlQ29tbWVudDU2NTYwNTkwNA== choldgraf 1839645 2019-12-13T20:57:01Z 2019-12-13T20:58:09Z MEMBER

For larger datasets, rather than storing them in github, a good approach is to create an archive on zenodo.org from which the data can be pulled.

Another note from MNE - we have a "datasets" sub-module that knows how to pull a few datasets from various online repositories (and in different structures). These store in a local folder (by default, ~/mne_data I believe) and then they get fast-loaded after the first download. Many of the datasets are then stored in online repositories like OSF (https://osf.io/rxvq7/).

For datasets that aren't gigantic it's a pretty nice system. https://mne.tools/stable/overview/datasets_index.html?highlight=datasets

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DOC: from examples to tutorials 527323165
557633282 https://github.com/pydata/xarray/issues/3564#issuecomment-557633282 https://api.github.com/repos/pydata/xarray/issues/3564 MDEyOklzc3VlQ29tbWVudDU1NzYzMzI4Mg== choldgraf 1839645 2019-11-22T18:04:50Z 2019-11-22T18:04:50Z MEMBER

In case it's helpful for inspiration, we took a similar approach with the MNE-Python package (neuro electrophysiology package):

https://mne.tools/stable/index.html

Maybe there are at least 3 levels in there, actually:

  • Examples - short vignettes that highlight one very specific piece of functionality, key-words for the example should be ctrl-fable in the title
  • Tutorials - in-depth guides through a common part of workflow that xarray wishes to enable, with more explanation and detail
  • Domain use-cases - examples of how xarray can facilitate use-cases in particular fields. Probably cover at a high-level many of the steps that multiple tutorials cover in-depth. More for "inspiration and buy-in" than in-depth learning.

Does that make sense?

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DOC: from examples to tutorials 527323165
546076945 https://github.com/pydata/xarray/pull/3425#issuecomment-546076945 https://api.github.com/repos/pydata/xarray/issues/3425 MDEyOklzc3VlQ29tbWVudDU0NjA3Njk0NQ== choldgraf 1839645 2019-10-24T19:54:44Z 2019-10-24T21:08:19Z MEMBER

Actually, no that's totally out of date now haha. Thanks for reminding me I should update that

edit: realized I should have said what I'm actually using - I'm using this:https://jupyterbook.org/features/page.html

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Html repr 510294810
546062969 https://github.com/pydata/xarray/pull/3425#issuecomment-546062969 https://api.github.com/repos/pydata/xarray/issues/3425 MDEyOklzc3VlQ29tbWVudDU0NjA2Mjk2OQ== choldgraf 1839645 2019-10-24T19:16:27Z 2019-10-24T19:17:03Z MEMBER

this is awesome! I was so excited about it that I updated my little blog post with the latest xarray master https://predictablynoisy.com/xarray-explore-ieeg

I was a little sad at the gigantic repr that came out of my DataArray, and now it is nice and tidy html!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Html repr 510294810
244228425 https://github.com/pydata/xarray/issues/727#issuecomment-244228425 https://api.github.com/repos/pydata/xarray/issues/727 MDEyOklzc3VlQ29tbWVudDI0NDIyODQyNQ== choldgraf 1839645 2016-09-01T22:10:56Z 2016-09-01T22:10:56Z MEMBER

whoops - that's what I get for not putting this on my to-do list...totally forgot about this issue. My bad, but thanks for fixing!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray creation prone to errors when data shares dimension shapes 128903340
175758184 https://github.com/pydata/xarray/issues/727#issuecomment-175758184 https://api.github.com/repos/pydata/xarray/issues/727 MDEyOklzc3VlQ29tbWVudDE3NTc1ODE4NA== choldgraf 1839645 2016-01-27T17:31:12Z 2016-01-27T17:31:12Z MEMBER

Cool - I'll make a PR in the next week or two...I know this isn't a big change but have a few deadlines in the coming days.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray creation prone to errors when data shares dimension shapes 128903340
175742179 https://github.com/pydata/xarray/issues/727#issuecomment-175742179 https://api.github.com/repos/pydata/xarray/issues/727 MDEyOklzc3VlQ29tbWVudDE3NTc0MjE3OQ== choldgraf 1839645 2016-01-27T16:56:51Z 2016-01-27T16:56:51Z MEMBER

So it looks like the relevant code is somewhere around here, no? Is "auto-coords" done in many other places in the codebase?

And as far as future behavior, do you imagine just changing the utils.is_dict_like bits so that instead of doing magical stuff under the hood, they just throw an error from now on?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray creation prone to errors when data shares dimension shapes 128903340
175417379 https://github.com/pydata/xarray/issues/727#issuecomment-175417379 https://api.github.com/repos/pydata/xarray/issues/727 MDEyOklzc3VlQ29tbWVudDE3NTQxNzM3OQ== choldgraf 1839645 2016-01-27T05:53:02Z 2016-01-27T05:53:02Z MEMBER

Lemme take a look at the code tomorrow. I'm pretty new to xarray but I've been meaning to learn it a bit more :-) On Jan 26, 2016 9:51 PM, "Stephan Hoyer" notifications@github.com wrote:

Any interest in putting together a PR? :)

On Tue, Jan 26, 2016 at 9:46 PM, Chris Holdgraf notifications@github.com wrote:

That sounds like a fair plan to me - throwing errors etc definitely complicates things more than just deprecating the option :)

On Tue, Jan 26, 2016 at 8:58 PM, Joe Hamman notifications@github.com wrote:

So I would support deprecating supplying dict-like coordinates without explicitly provided dims. It's more magic than we really need. This line is in the relevant code path.

I've also run into this and I'm [image: :+1:] on this solution.

— Reply to this email directly or view it on GitHub https://github.com/pydata/xarray/issues/727#issuecomment-175399404.

— Reply to this email directly or view it on GitHub https://github.com/pydata/xarray/issues/727#issuecomment-175414737.

— Reply to this email directly or view it on GitHub https://github.com/pydata/xarray/issues/727#issuecomment-175415408.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray creation prone to errors when data shares dimension shapes 128903340
175414737 https://github.com/pydata/xarray/issues/727#issuecomment-175414737 https://api.github.com/repos/pydata/xarray/issues/727 MDEyOklzc3VlQ29tbWVudDE3NTQxNDczNw== choldgraf 1839645 2016-01-27T05:46:36Z 2016-01-27T05:46:36Z MEMBER

That sounds like a fair plan to me - throwing errors etc definitely complicates things more than just deprecating the option :)

On Tue, Jan 26, 2016 at 8:58 PM, Joe Hamman notifications@github.com wrote:

So I would support deprecating supplying dict-like coordinates without explicitly provided dims. It's more magic than we really need. This line is in the relevant code path.

I've also run into this and I'm [image: :+1:] on this solution.

— Reply to this email directly or view it on GitHub https://github.com/pydata/xarray/issues/727#issuecomment-175399404.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray creation prone to errors when data shares dimension shapes 128903340

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