issue_comments

Table actions

4 rows where issue = 710357592 and user = 22067021 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • banesullivan · 4 ✖

issue 1

  • xarray / vtk integration · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1163460954 https://github.com/pydata/xarray/issues/4470#issuecomment-1163460954 https://api.github.com/repos/pydata/xarray/issues/4470 IC_kwDOAMm_X85FWQFa banesullivan 22067021 2022-06-22T18:20:39Z 2022-06-22T18:20:39Z CONTRIBUTOR

do you want to add this to the ecosystem page in the docs?

I'd love to! Thanks for the suggestion @keewis! I'll track this in https://github.com/pyvista/pyvista-xarray/issues/21 to contribute after I make my next round of improvements to pyvista-xarray

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray / vtk integration 710357592
1159196576 https://github.com/pydata/xarray/issues/4470#issuecomment-1159196576 https://api.github.com/repos/pydata/xarray/issues/4470 IC_kwDOAMm_X85FF--g banesullivan 22067021 2022-06-17T20:10:39Z 2022-06-17T20:10:39Z CONTRIBUTOR

Following up to mention that I've developed pyvista-xarray which provides an interface between vtkRectilinearGrids and xarrays DataArrays via PyVista: https://github.com/pyvista/pyvista-xarray

This is very much in its early stages and I’m hoping to take it quite a bit further. But first, I’d love to gather feedback and find how it works or doesn’t work for the types of data folks have.

At present, this accessor is specifically for rectilinear-style grids but if you have some other types of data, do share so that I can work towards supporting it in pyvista-xarray by opening an issue or discussion over there.

(there is limited support for vtkStructuredGrids as well)

 
{
    "total_count": 3,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 3,
    "rocket": 0,
    "eyes": 0
}
   xarray / vtk integration 710357592
1068428147 https://github.com/pydata/xarray/issues/4470#issuecomment-1068428147 https://api.github.com/repos/pydata/xarray/issues/4470 IC_kwDOAMm_X84_rutz banesullivan 22067021 2022-03-15T20:17:25Z 2022-03-15T20:17:25Z CONTRIBUTOR

I think a first step would be to make a data accessor between xarray and VTK/PyVista in accordance with https://xarray.pydata.org/en/stable/internals/extending-xarray.html

This keeps coming up again and again for me. @RichardScottOZ, if you're interested in kicking this off, I'd be happy to chat and help implement this and then outline some future direction for this sort of "integration"

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray / vtk integration 710357592
700184650 https://github.com/pydata/xarray/issues/4470#issuecomment-700184650 https://api.github.com/repos/pydata/xarray/issues/4470 MDEyOklzc3VlQ29tbWVudDcwMDE4NDY1MA== banesullivan 22067021 2020-09-28T17:46:21Z 2020-09-28T17:46:21Z CONTRIBUTOR

I'm really excited about this effort, thanks @rabernat! One thing I'd like to do before I forget is mention a project from the Software Underground (SWUNG) to create a new subsurface package: https://github.com/softwareunderground/subsurface

Over there, we are working to create a set of low-level data structures for sharing spatial data between various subsurface modeling/analysis software (e.g. GemPy, SimPEG, PyGIMLi, Fatiando, Welly, and more) with close ties to PyVista (VTK) for 3D visualization. At present, we are using xarray as the base data container for structured data types. This morning, @rabernat gave me some great insight into how xarray can be used to contain unstructured data as well and so I will be investigating how to do that so we leverage xarray as the base data container all around in subsurface. Then with subsurface's close ties to PyVista, there comes a bridge between xarray and VTK (via PyVista).

cc @Leguark and @prisae

This would be a proof of concept for the round-trip data interoperability going between xarray and VTK leaving us with some good lessons on what the value would be of a direct interface between VTK and xarray for better handling of large data and leveraging Dask.

Either way, it'd be awesome to have the subsurface development team in the loop here as there appears to be a lot of shared goals

 
{
    "total_count": 3,
    "+1": 3,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray / vtk integration 710357592

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