-
Notifications
You must be signed in to change notification settings - Fork 10
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
[asdf] Do not copy array data #456
Conversation
… flag effective again.
…om ndarray.name (which is used for asdf.NDarraytype wrapper).
Hello @marscher! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-08-02 17:06:44 UTC |
Codecov Report
@@ Coverage Diff @@
## master #456 +/- ##
=======================================
Coverage 96.85% 96.85%
=======================================
Files 88 88
Lines 5595 5599 +4
=======================================
+ Hits 5419 5423 +4
Misses 176 176
Continue to review full report at Codecov.
|
nice, does this work now with we should probably dig into the (asdf related) code for more |
Our unit tests switch the copy_arrays flag at least. But I doubt that the underlying functionality of mem mapping is really being tested. We can argue that this is already tested extensively upstream. |
that is certainly not tested, we just use these parameters to catch any errors that might flare up |
I got my memory profiler booted up anyways for another PR, so eventually I'll take a look. |
Changes
Because asdf does not handle time datatypes (correctly), there was a line of code within the serialization of xarray Variable to convert all ndarray like types from the asdf ndarray wrapper. This effectively prevents the use of the "copy_arrays" flag, since the
data got always copied.
Related Issues
Closes #454, #110
Checks