[Webservice] Use AW status on myMdC for warnings that prevent launching correction

Description

We're already using the AW status if e.g. one detector is corrected successfully and another isn't. But if we can't launch any corrections, there are a couple of warning cases we currently report to myMdC as errors:

• If we can't see any detectors needing correction in the run folder
• If we're skipping correction on a dark run

There's also a CONFIG_NOT_FOUND message with a WARN prefix, but it's not used anywhere.

In theory, both of these cases are totally fine and not a cause for concern. But if they occur unexpectedly, it might be that the DAQ is misconfigured, and there might be data that's missing compared to what people expect.

How Has This Been Tested?

TBD

Types of changes

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the code style of this project.

Reviewers

@schmidtp @ahmedk

Thanks! LGTM

I figured out that some of the runs in the CALLAB proposal let me test this:

Unfortunately the tooltip message on the run list page is kind of misleading for this case - calibrated data is not available in the proc folder, we're just claiming that's OK.

Do we go with this anyway, and maybe ask Luis to tweak the message? Or use another state? 'NA' (Not Available) seems like the closest, but might also risk re-triggering calibration, IIRC. Or request a new state for these cases?

resolved all threads

merged

mentioned in commit 6f3f34e7

changed milestone to %3.13.0