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
gatherer mixing satellite granules if timeout isn't reached #69
Comments
My solution has been to use different topics for each satellite: |
yes, but it feels like a workaround, doesn't it? |
Maybe a little. This is the way I'd plan my chains in any case. Now all the messages are more explicit having different topics for different data. |
I think this is related so I'm adding it here rather than as a new issue. I have a Metop-B granule from 2021-02-05 07:04:03 which is added to an Antarctica region and a Metop-C granule from 2021-02-05 07:10:03 — exactly six minutes later — over the Arctica region. My granule duration is three minutes. For subsequent granules at 07:13:03, 07:16:03 etc., rather than adding the Metop-B granule to Antarctica and Metop-C to Arctica, it's adding either Metop-B or Metop-C to both Arctica and Antarctica, and the other to neither. Extract from my logfiles:
To diagnose this more easily I used additional logging from #77. |
When gatherer is waiting for granules from eg npp, and noaa 20 granules are comming in, they are collected together with the npp granules.
The text was updated successfully, but these errors were encountered: