issue_comments

Table actions

2 rows where author_association = "NONE" and issue = 341321742 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • ENH: Adapt scipy example to imageio · 2 ✖

author_association 1

  • NONE · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
519780523 https://github.com/pydata/xarray/pull/2287#issuecomment-519780523 https://api.github.com/repos/pydata/xarray/issues/2287 MDEyOklzc3VlQ29tbWVudDUxOTc4MDUyMw== pep8speaks 24736507 2019-08-09T05:11:39Z 2019-08-09T05:11:39Z NONE

Hello @liuyenting! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 22:48: W504 line break after binary operator Line 136:13: E265 block comment should start with '# '

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: Adapt scipy example to imageio 341321742
405293927 https://github.com/pydata/xarray/pull/2287#issuecomment-405293927 https://api.github.com/repos/pydata/xarray/issues/2287 MDEyOklzc3VlQ29tbWVudDQwNTI5MzkyNw== y3nr1ng 2089799 2018-07-16T15:50:48Z 2018-07-16T16:10:09Z NONE

if xarray's rasterio backend wouldn't be a better template for an imageio backend instead.

I started with rasterio in the beginning, since TIFF-like containers are not modifiable, cache is crucial. However, it is my understanding, and please correct me if I am wrong, that rasterio backend is aimed at being a read-only I/O for xarray without having the extensibility for write ability, and I'm really eager to keep the ability to aggregate multiple files through dask, as well as saving data through imageio transparently (if plausible) :p

On second thought, maybe open_rasterio type of approach with to_zarr for saving is more preferable? But what are the possible approaches for open_mfdataset (and the potential of using dask for out-of-memory file I/O)?

For example, can imageio open any file which resembles a Dataset (i.e.: more than one variable with different datatypes), or would a DataArray be enough?

Generally, image containers opened by imageio represents a single Dataset only, which is why I default names to their readout sequences. However, there are indeed cases where multiple variables exist, such as pyramids of image sequences, each pyramid layer represents a different resolution for the sequence.

I must admit that a single DataArray is more applicable to the general usage.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: Adapt scipy example to imageio 341321742

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]);