You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently propagating the ArrayProxy reported dtype unless an explicit output_dtype is set.
It would be more efficient to allow the user set a low memory flag such that the data type's itemsize is capped (e.g., float64 is cast into float32 and int64 into int32).
By performing the casting operation at access time, we would be sparing some memory (if I'm not wrong), especially when we arrive at map_coordinates.
WDTY @effigies? what would be an efficient way of capping the itemsize that works generically for any dtype?
The text was updated successfully, but these errors were encountered:
We are currently propagating the ArrayProxy reported dtype unless an explicit output_dtype is set.
It would be more efficient to allow the user set a low memory flag such that the data type's itemsize is capped (e.g., float64 is cast into float32 and int64 into int32).
By performing the casting operation at access time, we would be sparing some memory (if I'm not wrong), especially when we arrive at map_coordinates.
WDTY @effigies? what would be an efficient way of capping the itemsize that works generically for any dtype?
The text was updated successfully, but these errors were encountered: