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
Loading both abi and nwcsaf-geo confuses satpy into sometimes trying the wrong composite #1112
Comments
While I acknowledge this is a real problem, I'm curious why you are loading these together in the same Scene? One quick workaround for the ABI versus NWCSAF-GEO composites is to load them separately. That doesn't help in the case of a reader that lists multiple sensors though. |
I'm loading them together because the fogpy fls_day composite for ABI needs both:
|
So the not super-easy workaround:
|
This is also needed for the |
Yes agree. |
Correct. I didn't yet come to make the issue @gerritholl. I found the bug/issue while preparing my presentation for yesterday, so was too busy. Thanks for posting it. Sorry for discovering it again! |
We have talked in the past about possibly defining multi-sensor composites in these special cases like As mentioned on slack, the correct fix for this particular case is to fix the nwcsaf-geo reader's |
satpy/satpy/readers/nwcsaf_nc.py Lines 80 to 92 in e91b6c7
@djhoese As far as I can see this is what is tried here? |
That won't work for this particular problem. The |
As far as fogpy is concerned, it's not actually a multi-sensor composite, but it's still a multi-reader composite. But multiple sensors on the same platform should also be possible now that not only LEO but also GEO satellites are starting to have a more diverse set of instruments. |
Describe the bug
When I load both ABI data and NWCSAF-GEO data, satpy loads composites files from
abi.yaml
,visir.yaml
, andseviri.yaml
(with #1111, alsoahi.yaml
). When I subsequently try to load a composite such asoverview
, depending on which composite file was loaded first, it either succeeds (ifabi.yaml
was loaded first) or fails (ifseviri.yaml
was loaded first).To Reproduce
Expected behavior
I expect that this code consistently executes without error messages.
Actual results
Text output of actual results or error messages including full tracebacks if applicable.
Sometimes it fails, sometimes it succeeds. This appear to depend on the order in which the composites are loaded, which appears non-deterministic.
Example of when it succeeds (
abi.yaml
loaded beforeseviri.yaml
):Example of when it fails (
seviri.yaml
loaded beforeabi.yaml
):Environment Info:
Writers
cf: ok
geotiff: ok
mitiff: ok
ninjotiff: cannot find module 'satpy.writers.ninjotiff' (No module named 'pyninjotiff')
scmi: ok
simple_image: ok
Extras
cartopy: ok
geoviews: ok
Additional context
PR #1111 explicitly lists abi and ahi as sensors for which the NWCSAF-GEO can work, this does not solve the problem.
The text was updated successfully, but these errors were encountered: