-
Notifications
You must be signed in to change notification settings - Fork 287
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
Remove fill-value checks from netcdf saver. #5833
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5833 +/- ##
==========================================
- Coverage 89.74% 89.73% -0.02%
==========================================
Files 92 92
Lines 22942 22898 -44
Branches 5464 5453 -11
==========================================
- Hits 20590 20547 -43
Misses 1620 1620
+ Partials 732 731 -1 ☔ View full report in Codecov by Sentry. |
Oh snap that's a full set of passing tests 😻 |
⏱️ Performance Benchmark Report: 4bac25aPerformance shifts
Full benchmark results
Generated by GHA run |
OK I've read through in detail and tested it myself. As far as I'm concerned this is ready to go. I accept that we would have liked to include some benchmarking to prove it but I suggest that comes in a second pull request IF we have the time before 3.9 is due. |
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.
@trexfeathers Looks good to me.
A couple of minor comments to service, then we can bank this 👍
…to lazystream_fix_5_nofvcheck
Thanks @bjlittle! |
WIP trial for simply removing the fill-value checking
N.B. some tests will now fail ... to be dealt with laterPros+cons
da.store
, which is officially recognised as having a memory-saving purpose "It stores values chunk by chunk so that it does not have to fill up memory"