-
Notifications
You must be signed in to change notification settings - Fork 2
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
Run automated CME detection on dates #347
Comments
The non-heartbeat alerts for 20150314:
There was no summary alert sent for the 2nd CME. Maybe the data ended and the process quit while the CME was occurring, and then it quit instead of sending the summary? |
Non-heartbeat alerts for 20160101:
This looks OK. |
Non-heartbeat alerts for 20210715:
This also looks OK. |
Non-heartbeat alerts for 20220201:
For some reason, it sent a new summary alert (74 in total) every 5 or 10 seconds (or occasionally up to a minute) from 012327 to 0140207, almost 17 minutes. |
All the test dates are staged in |
20140211:
|
20140313:
|
Non-heartbeat alerts for 20140924:
|
Non-heartbeat alerts for 20210709:
|
Non-hearbeat alerts for 20220511:
|
Non-heartbeat alerts for 20220830:
|
Non-heartbeat alerts for 20240330:
|
Process and run automated CME detection code on the following dates:
Mike - these new dates (20140211 thru 20220830) have NaNs in .csv file. Need new version.
Send alerts to @jburkepile.
Issues seen in above tests
The text was updated successfully, but these errors were encountered: