You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Nov 5th 2024 in daily a tile was observed on two exposures. The first was good, but the second had low exposure time (aborted) and was only run through sky subtractions. The column coloring is all correct but the status shows as "unknown" and is colored orange for the skysub exposure. Below is a screenshot. We should fix the dashboard to do the correct thing in this case.
The text was updated successfully, but these errors were encountered:
The issue was that for this tile and 2 other examples I found, the skysub exposure was not in the processing_table for the tile but was rather in the unprocessed_table.
My hypothesis is that desi_proc_night was run without --daily mode, such that the script would not submit skysub jobs. However, that doesn't explain why the outputs exist on disk, as I would have expected them to have been removed if the tile was purged.
Because I don't have an explanation for the root cause, I will leave this ticket open, even if the issue is not in the dashboard.
Other recent examples of this issue are nights 20241205 (expid 266913), 20241206 (expid 267061), and 20241209 (expid 267511), all of which were LASTSTEP=skysub. We're starting to build up several false positive orange alerts per month, so let's revisit this to try to identify and fix the underlying cause.
On Nov 5th 2024 in daily a tile was observed on two exposures. The first was good, but the second had low exposure time (aborted) and was only run through sky subtractions. The column coloring is all correct but the status shows as "unknown" and is colored orange for the skysub exposure. Below is a screenshot. We should fix the dashboard to do the correct thing in this case.
The text was updated successfully, but these errors were encountered: