issue_comments
3 rows where issue = 1433534927 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- xarray.align Inflating Source NetCDF Data · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1302244548 | https://github.com/pydata/xarray/issues/7248#issuecomment-1302244548 | https://api.github.com/repos/pydata/xarray/issues/7248 | IC_kwDOAMm_X85NnqzE | dcherian 2448579 | 2022-11-03T15:00:47Z | 2022-11-03T15:00:47Z | MEMBER | I think perhaps the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray.align Inflating Source NetCDF Data 1433534927 | |
1301171446 | https://github.com/pydata/xarray/issues/7248#issuecomment-1301171446 | https://api.github.com/repos/pydata/xarray/issues/7248 | IC_kwDOAMm_X85Njkz2 | matthewyakubiw 92732695 | 2022-11-02T20:09:36Z | 2022-11-02T20:09:36Z | NONE |
This would be correct if we added that many 8MB data sets, but we just added one! So I'd expect the entire store to be roughly that size (8MB) before compression since in the code example above we are just adding one data array to the Zarr data store. Would you be able to clarify this calculation
So the reason why all the dimension sizes have grown is because we initialize the Zarr with the set of all possibilities that the coordinates might be (read somewhere that this is what you should do - initialize an empty Zarr with the coords/dimensions you will need). Then what I figured I needed to do was align the dimensions of the .nc file with that of the Zarr store, so that when the data array is added the coordinates and dimensions line up - this is why we see the dimensions grow. Is this the correct approach? I found the limitation/design of Without aligning, I would get error messages that complained about dimension sizes being different. Thanks again for your help! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray.align Inflating Source NetCDF Data 1433534927 | |
1301082744 | https://github.com/pydata/xarray/issues/7248#issuecomment-1301082744 | https://api.github.com/repos/pydata/xarray/issues/7248 | IC_kwDOAMm_X85NjPJ4 | max-sixty 5635139 | 2022-11-02T18:57:48Z | 2022-11-02T18:57:48Z | MEMBER | Even without looking at the size of the data, the dimensions of the array seem to have grown a lot! The size of the data seems consistent with that (i.e. Does looking at the values of the dimension that's grown to size 48 help — are those possibly different, even though you don't intend them to be, and causing it to be huge (but sparse!)? Does that make sense? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray.align Inflating Source NetCDF Data 1433534927 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 3