pull_requests: 163879577

This data as json

id node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
163879577 MDExOlB1bGxSZXF1ZXN0MTYzODc5NTc3 1840 closed 0 Read small integers as float32, not float64 12229877 - [x] Closes #1842 - [x] Tests added - [x] Tests passed - [x] Passes ``flake8 xarray`` (now part of tests) - [x] Fully documented, including `whats-new.rst` for all changes Most satellites produce images with color depth in the range of eight to sixteen bits, which are therefore often stored as unsigned integers (with the quality mask in another variable). If you're lucky, they also have a `scale_factor` attribute and Xarray can automatically convert the integers to floats representing albedo. This is fantastically convenient, and avoids all the bit-depth bugs from misremembered specifications. However, loading data as float64 when float32 is sufficient *doubles* memory usage in IO (even on multi-TB datasets...). While immediately downcasting helps, it's no substitute for doing the right thing first. So this patch does some conservative checks, and if we can be sure float32 is safe we use that instead. 2018-01-19T03:40:51Z 2018-04-19T02:50:25Z 2018-01-23T20:15:29Z 2018-01-23T20:15:29Z 65e5f05938dc40c6e169377f8c0b6e7774d96866     0 8238eb6410576f406277f83b6f9e6a6feb3f8640 b55143d3a54d95f3d6a8356835bd27be369824da CONTRIBUTOR   13221727 https://github.com/pydata/xarray/pull/1840  

Links from other tables