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
{{ message }}
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
Testing http://desi-1.kpno.noao.edu:9090 using code from desispec #702 (now tag 0.25.0) and qlf #253, mostly looking at Observing History window and drill-downs.
There are no drill down plots or numbers for:
HDUS
XYSHIFTS
CHECKARC
CHECKFLAT
SKYRBAND
At minimum these should include the measured number and the valid range. Without that, there can be an error listed but no way to tell what went wrong, or even what the value was that is triggering the warning/error.
The text was updated successfully, but these errors were encountered:
HDU checks whether file exists or not so we have no references to show.
CHECKARC, CHECKFLAT and SKYRBAND are on http://desi-1.kpno.noao.edu:9090/
XYSHIFTS has a small problem of missing keys on mergedQA #253 (comment)
Check HDUs: the point of this metric should be to check for the drastic error that an HDU that is supposed to be in the raw data file isn't, i.e. we're missing an entire camera of data. The drill down would show which HDUs exist and flag those that are supposed to exist but don't. However, I don't see how you could tell that from the QL output; see desihub/desispec#708.
CHECKARC, CHECKFLAT, SKYRBAND: I now see drill downs for those, thanks. I'll open separate tickets for QL to make those meaningful values.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Testing http://desi-1.kpno.noao.edu:9090 using code from desispec #702 (now tag 0.25.0) and qlf #253, mostly looking at Observing History window and drill-downs.
There are no drill down plots or numbers for:
At minimum these should include the measured number and the valid range. Without that, there can be an error listed but no way to tell what went wrong, or even what the value was that is triggering the warning/error.
The text was updated successfully, but these errors were encountered: