-
Notifications
You must be signed in to change notification settings - Fork 303
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
Handle valid range and valid_range correctly for two types of HY2 SCAT l2b hdf5 data #2211
Handle valid range and valid_range correctly for two types of HY2 SCAT l2b hdf5 data #2211
Conversation
Add a corrected green composite for FCI and use this in the true color RGB. The problem is the same as for AHI, in that the "green" channel misses the chlorophyl peak making our green planet look rather brown as if all the forests have burnt :(
Move the GreenCorrector to the new module satpy.composites.spectral, as it applies to FCI as well as to AHI. Adapt AHI and FCI composites using this corrector. Improve documentation for the corrector.
Add the new file that was missing in the previous commit and that was causing test failures.
Some small fixes for the green corrector based on feedback from Dave.
Hm, I don't understand why the tests are failing. When I run the tests locally, they pass. |
Often that would mean missing dependencies on CI, but can't see how that would be the case in this one if the tests have been passing before the PR 🤔 |
Ah, ok. Setting up python 3.8 I get the test to fail. Now I have something to debug. |
No, it is not the python version but xarray version. upgrading to Hm, do I use it wrong or is there a bug in xarray? |
In the docs it says it will take the
I think In your other case:
|
Ah, thanks. |
Now the test for this change pass as far as I can see. But there is another test failing. Hm what changed now? |
This is a known failure that I need to fix. Someone already added an |
Yeah, that was my guess also. Should I add this in this PR? Or does it need to be in a separate PR? Then I can at least make an issue? |
If this PR is straight forward and ready to be merged besides the failing test then I'm OK with you adding it here. I think 1e-4 is good enough, but I'd have to search for the other contributor who already fixed it. In another PR I saw yet another test failing, but I don't see that here so we'll have to see what happens. |
OK, I ran the reader tests locally, and a lot is failing, mainly the same issue:
I think this is better cleaned up separately |
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.
Thanks for fixing this. Could you add a test for this?
Fix ici after mws merge
Update seadas_l2 reader to handle alternative NetCDF file format
…rods Fix CLAVR-x configuration in 'awips_tiled' writer to be backwards compatible
updates: - [github.com/pre-commit/mirrors-mypy: v0.981 → v0.982](pre-commit/mirrors-mypy@v0.981...v0.982)
So, I have come up with an idea to, what to call it, override
By doing this the original test fails for none NSOAS data as they are expected to do. I hope I can do this and adding my fix to the code as already in the PR. |
[pre-commit.ci] pre-commit autoupdate
I'm still not sure what the original issue is but if you think this helps then try it out and let's see how it goes. FYI |
…longlong/satpy into issue2208-hy2-scat-l2b-h5-valid-range
Codecov Report
@@ Coverage Diff @@
## main #2211 +/- ##
==========================================
+ Coverage 94.13% 94.15% +0.01%
==========================================
Files 293 294 +1
Lines 45079 45203 +124
==========================================
+ Hits 42437 42559 +122
- Misses 2642 2644 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
@TAlonglong could you try to clean up the history here? there are a lot of old commits hanging around, and that makes is particularly difficult to review |
yeah, I think I did some merge from the main or rebase that messed this up. I never get these things right. I don't understand how I could clean this up. I will need to have a look around to see if I can figure something out. |
I would suggest maybe creating a new branch off of current |
Okay, so I partly did what David suggested. But there was mess of try and fail code, so cherry picking became difficult. So I ended up to create a diff patch and apply that to a new branch #2268 Please feel free to close this PR if that work out. |
I merged #2268, so closing this |
There was a mixture of where attributes were taken from, both data and self[key]
Adding keep_attrs when using xarray.where let us keep the attributes so we can use attributes from that instead of self[key]
valid range
attribute #2208AUTHORS.md
if not there already