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 bug in OLCI reader that caused multiple error messages to print #945
Conversation
…ted. Also a minor style fix for one line that was too long for flake8
Codecov Report
@@ Coverage Diff @@
## master #945 +/- ##
==========================================
+ Coverage 85.41% 85.84% +0.42%
==========================================
Files 172 172
Lines 26048 26222 +174
==========================================
+ Hits 22248 22509 +261
+ Misses 3800 3713 -87
Continue to review full report at Codecov.
|
…ding netcdf data. The default is netcdf4, which does not produce error messages.
Should we have the default engine to |
Good idea, I've changed it to |
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.
LGTM, thanks for cleaning up the deprecated stuff :) I just have a few cosmetic items to point out.
In issue #944 I describe how the OLCI reader prints numerous error messages to the screen during processing. This PR fixed the error messages by switching to the default
xarray
engine for netCDF4. I have also added functions that explicitly close thenetcdf
files at the end of the processing. This may or may not be needed (I'm not sure) but I thought I'd copy what theGOES-ABI
reader does here.Lastly, I also split one line of code onto two, which was previously giving a flake8 style error for being too long.
flake8 satpy