issue_comments
12 rows where issue = 1681353195 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- xr.open_dataset() reading ubyte variables as float32 from DAP server · 12 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1525705799 | https://github.com/pydata/xarray/issues/7782#issuecomment-1525705799 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85a8GxH | kmuehlbauer 5821660 | 2023-04-27T13:33:50Z | 2023-04-27T13:33:50Z | MEMBER |
TL;DR: NETCDF3 detail to allow (signal) unsigned integer, still used in recent formats
A conventional way to indicate whether a byte, short, or int variable is meant to be interpreted as unsigned, even for the netCDF-3 classic model that has no external unsigned integer type, is by providing the special variable attribute _Unsigned with value "true". However, most existing data for which packed values are intended to be interpreted as unsigned are stored without this attribute, so readers must be aware of packing assumptions in this case. In the enhanced netCDF-4 data model, packed integers may be declared to be of the appropriate unsigned type. My suggestion would be to nudge the user by issuing warnings and link to new to be added documentation on the topic. This could be in line with the cf-coding conformance checks which have been discussed yesterday in the dev-meeting. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1523618985 | https://github.com/pydata/xarray/issues/7782#issuecomment-1523618985 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85a0JSp | dcherian 2448579 | 2023-04-26T15:29:14Z | 2023-04-26T15:29:14Z | MEMBER | Thanks for the in-depth investigation!
Do we know why this is so?
:+1: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1522997083 | https://github.com/pydata/xarray/issues/7782#issuecomment-1522997083 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85axxdb | kmuehlbauer 5821660 | 2023-04-26T08:28:39Z | 2023-04-26T08:28:39Z | MEMBER | This is how netCDF4-python handles this data with different parameters:
First, the dataset was created with As we can see from the above output, in netCDF4-python If Xarray is trying to align with netCDF4-python it should separate We would need a similar approach here for Xarray with additional kwargs |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520804745 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520804745 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85apaOJ | kmuehlbauer 5821660 | 2023-04-24T20:47:43Z | 2023-04-24T20:47:43Z | MEMBER | @dcherian The main issue here is that we have two different CF things which are applied, Unsigned and _FillValue/missing_value. For netcdf4-python the values would just be masked and the dtype would be preserved. For xarray it will be cast to float32 because of the _FillValue/missing_value. I agree, moving the Unsigned Coder out of mask_and_scale should help in that particular case. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520550980 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520550980 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85aocRE | dcherian 2448579 | 2023-04-24T17:18:37Z | 2023-04-24T19:55:11Z | MEMBER |
The current approach seeems OK no? It seems like the bug is that
EDIT: I mean that each coder checks whether it is applicable, so we already do that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520514792 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520514792 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85aoTbo | kmuehlbauer 5821660 | 2023-04-24T16:52:30Z | 2023-04-24T16:52:30Z | MEMBER | @dcherian Yes, that would work. We would want to check the different attributes and apply the coders only as needed. That might need some refactoring. I'm already wrapping my head around this for several weeks now. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520434316 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520434316 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85an_yM | dcherian 2448579 | 2023-04-24T15:55:48Z | 2023-04-24T15:55:48Z | MEMBER |
Do these two have to be linked? I wonder if we can handle the filling later : https://github.com/pydata/xarray/blob/2657787f76fffe4395288702403a68212e69234b/xarray/coding/variables.py#L397-L407 It seems like this code is setting fill values to the right type for CFMaskCoder which is the next step |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520409398 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520409398 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85an5s2 | Articoking 90768774 | 2023-04-24T15:39:50Z | 2023-04-24T15:39:50Z | CONTRIBUTOR | Your suggestion worked perfectly, thank you very much! Avoiding using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520363622 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520363622 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85anuhm | kmuehlbauer 5821660 | 2023-04-24T15:10:24Z | 2023-04-24T15:11:00Z | MEMBER | Then you are somewhat deadlocked. You might be able to achieve what want by using I'll add a code example tomorrow if no one beats me to it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520341470 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520341470 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85anpHe | Articoking 90768774 | 2023-04-24T14:58:36Z | 2023-04-24T14:58:36Z | CONTRIBUTOR | Thank you for your quick reply. Adding the It would save me quite a lot of processing time since using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520277594 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520277594 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85anZha | kmuehlbauer 5821660 | 2023-04-24T14:31:00Z | 2023-04-24T14:31:00Z | MEMBER | @Articoking As both variables have a _FillValue attached xarray converts these values to NaN effectively casting to float32 in this case. You might inspect the You can deactivate the automatic conversion by adding kwarg There is more information in the docs https://docs.xarray.dev/en/stable/user-guide/io.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 | |
1520222850 | https://github.com/pydata/xarray/issues/7782#issuecomment-1520222850 | https://api.github.com/repos/pydata/xarray/issues/7782 | IC_kwDOAMm_X85anMKC | welcome[bot] 30606887 | 2023-04-24T14:04:15Z | 2023-04-24T14:04:15Z | NONE | Thanks for opening your first issue here at xarray! Be sure to follow the issue template! If you have an idea for a solution, we would really welcome a Pull Request with proposed changes. See the Contributing Guide for more. It may take us a while to respond here, but we really value your contribution. Contributors like you help make xarray better. Thank you! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xr.open_dataset() reading ubyte variables as float32 from DAP server 1681353195 |
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