-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix a bug that caused big-endian dask arrays to not be reprojected correctly #487
Conversation
@@ -53,7 +53,7 @@ def _dask_to_numpy_memmap(dask_array, tmp_dir): | |||
|
|||
memmapped_array = np.memmap( | |||
memmap_path, | |||
dtype=zarr_array.dtype, | |||
dtype=float, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The memmap was read later on assuming it was native float
.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #487 +/- ##
==========================================
+ Coverage 90.90% 91.00% +0.10%
==========================================
Files 25 25
Lines 1077 1078 +1
==========================================
+ Hits 979 981 +2
+ Misses 98 97 -1 ☔ View full report in Codecov by Sentry. |
I think I need to check the case where |
But for now I think it should work @keflavich |
Yes, this solves the problem; I didn't realize there was a dask reader/converter built in to reproject. I'll rebase #474 against this and remove the hack I implemented. |
I'm surprised I didn't run into this sooner, but this should fix the endianness issue @keflavich - can you confirm?