issue_comments
5 rows where issue = 29453809 and user = 703554 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- HDF5 backend for xray · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
338459385 | https://github.com/pydata/xarray/issues/66#issuecomment-338459385 | https://api.github.com/repos/pydata/xarray/issues/66 | MDEyOklzc3VlQ29tbWVudDMzODQ1OTM4NQ== | alimanfoo 703554 | 2017-10-22T08:02:29Z | 2017-10-22T08:02:29Z | CONTRIBUTOR | Just to say thanks for the work on this, I've been looking at the h5netcdf code recently to understand better how dimensions are plumbed in netcdf4. I'm exploring refactoring all my data model classes in scikit-allel to build on xarray, I think the time is right, especially if xarray gets a Zarr backend too. On Sun, 22 Oct 2017 at 02:01, Stephan Hoyer notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HDF5 backend for xray 29453809 | |
90813596 | https://github.com/pydata/xarray/issues/66#issuecomment-90813596 | https://api.github.com/repos/pydata/xarray/issues/66 | MDEyOklzc3VlQ29tbWVudDkwODEzNTk2 | alimanfoo 703554 | 2015-04-08T06:04:53Z | 2015-04-08T06:04:53Z | CONTRIBUTOR | Thanks Stephan, I'll take a look. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HDF5 backend for xray 29453809 | |
42869488 | https://github.com/pydata/xarray/issues/66#issuecomment-42869488 | https://api.github.com/repos/pydata/xarray/issues/66 | MDEyOklzc3VlQ29tbWVudDQyODY5NDg4 | alimanfoo 703554 | 2014-05-12T18:29:57Z | 2014-05-12T18:29:57Z | CONTRIBUTOR | One other detail, I have an HDF5 group for each conceptual dataset, but then variables may be organised into subgroups. It would be nice if this could be accommodated, e.g., when opening an HDF5 group as an xray dataset, assume the dataset contains all variables in the group and any subgroups searched recursively. Again apologies I don't know if this is allowed in NetCDF4, will do the research. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HDF5 backend for xray 29453809 | |
42840763 | https://github.com/pydata/xarray/issues/66#issuecomment-42840763 | https://api.github.com/repos/pydata/xarray/issues/66 | MDEyOklzc3VlQ29tbWVudDQyODQwNzYz | alimanfoo 703554 | 2014-05-12T14:45:57Z | 2014-05-12T14:45:57Z | CONTRIBUTOR | Thanks @akleeman for the info, much appreciated. A couple of other points I thought maybe worth mentioning if you're considering wrapping h5py. First I've been using lzf as the compression filter in my HDF5 files. I believe h5py bundles the source for lzf. I don't know if lzf would be supported if accessing through the python netcdf API. Second, I have a situation where I have multiple datasets, each of which is stored in a separate groups, each of which has two dimensions (genome position and biological sample). The genome position scale is different for each dataset (there's one dataset per chromosome), however, the biological sample scale is actually common to all of the datasets. So at the moment I have a variable in the root group with the "samples" dimension scale, then each dataset group has it's own "position" dimension scale. You can represent all this with HDF5 dimension scales, but I've no idea if this is accommodated by NetCDF4 or could fit into the xray model. I could work around this by copying the samples variable into each dataset, but just thought I mention this pattern as something to be aware of. On Mon, May 12, 2014 at 3:04 PM, akleeman notifications@github.com wrote:
Alistair Miles Head of Epidemiological Informatics Centre for Genomics and Global Health http://cggh.org The Wellcome Trust Centre for Human Genetics Roosevelt Drive Oxford OX3 7BN United Kingdom Web: http://purl.org/net/aliman Email: alimanfoo@gmail.com Tel: +44 (0)1865 287721 _new number_ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HDF5 backend for xray 29453809 | |
42805550 | https://github.com/pydata/xarray/issues/66#issuecomment-42805550 | https://api.github.com/repos/pydata/xarray/issues/66 | MDEyOklzc3VlQ29tbWVudDQyODA1NTUw | alimanfoo 703554 | 2014-05-12T08:08:37Z | 2014-05-12T08:08:37Z | CONTRIBUTOR | I'm really enjoying working with xray, it's so nice to be able to think of my dimensions as named and labeled dimensions, no more remembering which axis is which! I'm not sure if this is relevant to this specific issue, but I am working for the most part with HDF5 files created using h5py. I'm only just learning about NetCDF-4, but I have datasets that comprise a number of 1D and 2D variables with shared dimensions, so I think my data is already very close to the right model. I have a couple of questions: (1) If I have multiple datasets within an HDF5 file, each within a separate group, can I access those through xray? (2) What would I need to add to my HDF5 to make it fully compliant with the xray/NetCDF4 model? Is it just a question of creating and attaching dimension scales or would I need to do something else as well? Thanks in advance. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HDF5 backend for xray 29453809 |
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 1