-
Notifications
You must be signed in to change notification settings - Fork 27
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
Periodic missing satellite sectors #129
Comments
Try upgrading to 6.15.0. It fixed that issue for me. Using Ubuntu 22.04. |
Excellent! Thank you Mr. Sebenste. Hopefully it goes smoothly, I"m always afraid something will get overwritten. |
Well shoot, that didn't work. Still getting a missing VIS sector about once per day. I do wonder if maybe my product queue and the registry values are not correct. I noticed that doing:
Sometimes the last value is large like 11,000 seconds (well above 3600), but sometimes, it drops to like 50, which is well below the 3600 seconds in registry. I upped the cache to 2 GB from the default 500 mb. Strangely, it seems to use disk space, whereas I thought it was going to be stored in RAM.
The 500 MB queue just seems really low IMO, at least for 2024. I wonder if there is a place to find updated/recommended configurations for LDM nowadays? |
Wait, you only had 500 MB? You need 20 GB for that feed alone... |
That's good to know Mr. Sebenste, thank! I assumed the values were "good" since they came straight from Unidata, and (surprisingly?) things seemed to run "fairly well" even with only that much. So I'll up the 2048M Any other major things that should be upped from defaults? I have a feeling this may fix the missing sectors. Those satellite files are large, and somtimes the "last" one comes in so late, the next image time is already processing.
|
That should do it! You should be good to go. |
LDM 6.14.5 on Debian
Issue: Despite a strong signal, on some days we get missing satellite sectors, especially goes channel 02 / VIS.
Other channels like 09 and 14 always arrive.
Seems between 12-18Z are the most common times for this to occur.
For example, this file may be missing: TIRE02_KNES_031416_PAI.nc
Other places online do not show the missing sector.
Any ideas what may be happening?
Does LDM have any sort of retry mechanism, or, perhaps a way to prioritize data types, assuming it could be a processing issue?
Have you ever heard of this issue?
Here is our pqact.goes:
The text was updated successfully, but these errors were encountered: