-
Notifications
You must be signed in to change notification settings - Fork 1
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
Consider a more obvious stale data warning #2
Comments
Happened again today, this time due to a lag in the AWS data; all updates (on the AWS side, not me) stopped around 16:00 UTC, but I didn't notice until around 19:00 UTC. |
The sticky part of this is that the code is completely fine, it's just the datasource goes slightly stale and no new files are found. As I sit here it seems like they're trickling in to AWS again, though slowly. Looking around, places like the CoD site still have data flowing; I think they're using the Unidata source(s) but from a cursory look, those are much more hands-on to get up and running. Specifically I was able to download and compile their LDM tool, but I didn't bother to try to configure it. That really is screaming for containerization since it's so specific in its setup. And from a cursory google search - here's the official container :) and https://www.unidata.ucar.edu/data/goesr.html Ultimately I don't want to open unless we really have to consider it. I'm content to just slap a warning on it and let the users fall back to their favorite alternate source, since the purpose of NightWatch wasn't to build a weather data site. |
It works! At (or around) 19:49 UTC I picked up an image from 18:44 UTC, and it didn't have the errorStamp on it. Closing this as it seems to be working fine now. |
Final note: After literally almost a day of searching through various NOAA websites, I think I found something important: https://www.ospo.noaa.gov/Operations/messages.html This must be the place that is uploading the AWS data, because they list the following:
and they gave the following updates:
that almost exactly corresponds to the gaps I just saw, so I'll check back here periodically when there are problems. OPS: 😧 |
I only noticed issue #1 because I wanted to see the longer term radar data for the current storm, and I realized that the plot was showing clear skies when I could literally hear the rain pounding on my house/roof.
There should therefore probably be a much more obvious "HEY THERE'S NO DATA TO PLOT" type of indication, or individual status indicators for each major subsystem. TBD which is easier and which is actually better.
The text was updated successfully, but these errors were encountered: