Monitors may not be properly reading or populating database tables

[bhilbert4]

Recent runs of the monitors all seem to indicate that there is no query history for some common instrument/aperture pairs. It's highly unlikely that these apertures haven't before been used by the monitors, which makes me suspicious that there is some issue with either updating or reading database tables. Could be helpful to look into the database tables manually and see what's in them.

Logs from Jan 7, 2023 for the dark, bias, readnoise, and bad pixel monitors suggest that this may be a common problem.

[bhilbert4]

A check of the NIRCam dark monitor tables seems to show that things are ok. The monitor has only run with data once, spanning the date range of Jan 28, 2022 to Oct 23, 2022. Since that time, not enough new data has piled up in order to trigger the monitor. The Jan 7 log mentioned above supports this. So maybe we want to lower the threshold number of files for kicking off a monitor run?

[bhilbert4]

Database interactions are correct. More importantly, we have now switched to Django models for db interactions. The dark monitor is being switched over to use models in #1493