issue_comments
7 rows where issue = 272415954 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Error when using engine='scipy' reading CM2.6 ocean output · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
456593474 | https://github.com/pydata/xarray/issues/1704#issuecomment-456593474 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDQ1NjU5MzQ3NA== | dcherian 2448579 | 2019-01-22T22:48:21Z | 2019-01-22T22:48:21Z | MEMBER | Closing in favour of #1823 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
346028156 | https://github.com/pydata/xarray/issues/1704#issuecomment-346028156 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0NjAyODE1Ng== | jbusecke 14314623 | 2017-11-21T13:35:38Z | 2017-11-21T13:35:38Z | CONTRIBUTOR | Yes that would be phenomenal. It would be absolutely sufficient for this to be an optional step that needs to be activated with e.g. xr.open_mfdataset(filelist, full_check=True). In my particular use case I encountered very long load times, and it would be great if in any such problematic cases there would be an easy way to activate a suite of verbose checks to quickly identify problems. For normal use these could be largely deactivated to achieve a fast and streamlined readin? Sent from my iPhone
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
345919689 | https://github.com/pydata/xarray/issues/1704#issuecomment-345919689 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0NTkxOTY4OQ== | jhamman 2443309 | 2017-11-21T05:17:14Z | 2017-11-21T05:17:14Z | MEMBER | @jbusecke -
In your case, what would that have looked like? Many users have actually requested that xarray provide a more streamlined reader function that does less checking. Perhaps it would have been useful for you to have xarray raise an error when it encountered files that weren't consistent (either in the variable, dimensions, or coordinates)? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
344352515 | https://github.com/pydata/xarray/issues/1704#issuecomment-344352515 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0NDM1MjUxNQ== | jbusecke 14314623 | 2017-11-14T18:28:51Z | 2017-11-14T18:28:51Z | CONTRIBUTOR | I believe I solved the issue: It turns out the reason for the slow performance were inconsistencies in between different files (added data_vars and coords). Specifying I am not sure if that is a feasible option, but would it be possible to implement a check for such errors that displays a warning? The error regarding |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
343352694 | https://github.com/pydata/xarray/issues/1704#issuecomment-343352694 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0MzM1MjY5NA== | shoyer 1217238 | 2017-11-10T02:02:51Z | 2017-11-10T02:02:51Z | MEMBER | Can you figure out which variable name it's erroring on? Try dropping into a debugger (e.g., It is not immediately obvious to me what the issue is with this file, but I suspect this is probably a SciPy issue given that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
343344036 | https://github.com/pydata/xarray/issues/1704#issuecomment-343344036 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0MzM0NDAzNg== | jbusecke 14314623 | 2017-11-10T01:11:00Z | 2017-11-10T01:11:00Z | CONTRIBUTOR | Ok I just tried to read the files with the new RC. Same error. here is the output of commit: None python: 3.6.3.final.0 python-bits: 64 OS: Linux OS-release: 2.6.32-642.15.1.el6.x86_64 machine: x86_64 processor: x86_64 byteorder: little LC_ALL: None LANG: en_US LOCALE: en_US.ISO8859-1 xarray: 0.10.0rc1 pandas: 0.21.0 numpy: 1.13.3 scipy: 0.19.1 netCDF4: 1.3.1 h5netcdf: None Nio: None bottleneck: None cyordereddict: None dask: 0.15.4 matplotlib: 2.1.0 cartopy: 0.15.1 seaborn: 0.8.1 setuptools: 36.6.0 pip: 9.0.1 conda: None pytest: 3.2.3 IPython: 6.2.1 sphinx: None ``` and here is an // global attributes: :filename = "01980101.ocean.nc" ; :title = "CM2.6_miniBling" ; :grid_type = "mosaic" ; :grid_tile = "1" ; :history = "Tue Feb 25 16:32:17 2014: ncks --64bit --hdr_pad 15000 -A ocean.0198.ann2d.nc ocean.0198.ann.nc\n", "Tue Feb 25 16:23:35 2014: ncks --64bit --hdr_pad 15000 -A frazil_2d.nc ocean.0198.ann2d.nc\n", "Tue Feb 25 16:23:32 2014: ncra -O -v nv,time_bounds,geolat_c,geolat_t,geolon_c,geolon_t,st_edges_ocean,sw_edges_ocean,frazil_2d 01980101.ocean.nc frazil_2d.nc" ; :nco_openmp_thread_number = 1 ; :NCO = "4.1.0" ; } ``` I am unsure if I am allowed to share them publicly, is there another way to diagnose what is going on? Thanks a lot! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
343030828 | https://github.com/pydata/xarray/issues/1704#issuecomment-343030828 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0MzAzMDgyOA== | shoyer 1217238 | 2017-11-09T02:46:09Z | 2017-11-09T02:46:09Z | MEMBER | Can you share an example file? Note that there are some performance improvements for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 |
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 4