issue_comments
2 rows where user = 18623439 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
272582585 | https://github.com/pydata/xarray/issues/486#issuecomment-272582585 | https://api.github.com/repos/pydata/xarray/issues/486 | MDEyOklzc3VlQ29tbWVudDI3MjU4MjU4NQ== | godfrey4000 18623439 | 2017-01-14T00:17:05Z | 2017-01-14T00:17:05Z | NONE | I'm ready to start working on this project. I already have a prototype regridding class that I developed as part of another project. Working on that, I discovered these points: - regridding takes a long time because the lattices can be huge - the design should accomodate parallel processing on a cluster - data needs to be normalized first (deal with missing values, etc.) - the user will want choices Some of these choices are: - the destination lattice - the interpolation algorithm - subset of the dimension space As the first step in a strategy to achieve this with a sequence of realizable goals, I plan to implement a regridding of just the latitude and longitude dimensions. Is there a style guide that I can/should follow? Something like this: https://google.github.io/styleguide/pyguide.html? Does it or something else define naming conventions? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API for multi-dimensional resampling/regridding 96211612 | |
271447717 | https://github.com/pydata/xarray/issues/486#issuecomment-271447717 | https://api.github.com/repos/pydata/xarray/issues/486 | MDEyOklzc3VlQ29tbWVudDI3MTQ0NzcxNw== | godfrey4000 18623439 | 2017-01-10T00:07:16Z | 2017-01-10T00:07:16Z | NONE | I have an immediate need in this area. My objective is to create a tool that will enable arithmetic on variables defined on lattices whose points don't coincide. Through my attempts thus far, it has become clear that I need data structures that incorporate spacial indexing and lattice indexing. Since I have to tackle this issue to proceed, I thought I should follow the thinking discussed in this forum, so that it may be useful to others. |
{ "total_count": 4, "+1": 4, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API for multi-dimensional resampling/regridding 96211612 |
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