pub const EXIT_POOR_QUALITY: u8 = 5;Expand description
A tune/simulate run was aborted because a driver reported a non-Good OPC quality
for a tuning-critical reading (finding 5 of the live-plant safety review): an initial
reading, the transition-to-manual setpoint capture, or an in-flight PV poll sample, and
(for the in-flight case) the global Config > OPC quality policy rejected Uncertain, or
the quality was Bad rather than merely Uncertain. The loop was restored to its pre-test
mode, exactly like EXIT_ABORTED/EXIT_TIMED_OUT. Distinct from both so a scheduler’s alerting can
tell “the plant data itself couldn’t be trusted” apart from a user-initiated stop or a
run that simply took too long. See commands::tune::TuneOutcome::PoorQuality and
AGENTS.md’s safety-quality section.