The filter node has stopped several times in the past while processing the alerts against the watchmaps, including yesterday. One of the active watchmap files has MOCORDER=29 corresponding to a resolution of 0.00003 arcsec. Warning messages are printed out by the filter node, and I think these bad MOC files are causing the failure. In any case, we should not be blindly accepting any file that is uploaded, we should test that its a proper MOC file.
This PR has
code to check for bad files (in common/src/bad_fits.py).
checks files each midnight before use in the filter node (in `services/make_area_files.py')
checks uploaded files and may produce error message (in webserver/lasair/apps/watchmap/views.py)
Merging it requires no database, settings, or cron changes, just restarting the webserver.
The filter node has stopped several times in the past while processing the alerts against the watchmaps, including yesterday. One of the active watchmap files has MOCORDER=29 corresponding to a resolution of 0.00003 arcsec. Warning messages are printed out by the filter node, and I think these bad MOC files are causing the failure. In any case, we should not be blindly accepting any file that is uploaded, we should test that its a proper MOC file.
This PR has
common/src/bad_fits.py).webserver/lasair/apps/watchmap/views.py)Merging it requires no database, settings, or cron changes, just restarting the webserver.