QuantumAttemptStatus#
- class lsst.pipe.base.QuantumAttemptStatus(value, names=<not given>, *values, module=None, qualname=None, type=None, start=1, boundary=None)#
Bases:
EnumEnum summarizing an attempt to run a quantum.
Attributes Summary
The quantum failed with a hard error that prevented both logs and metadata from being written.
Task metadata was written for this attempt but logs were not.
This quantum was not executed because an upstream quantum failed.
Execution of the quantum failed gracefully.
This quantum was successfully executed.
The status of this attempt is unknown.
Whether the log dataset was produced.
Whether the task metadata dataset was produced.
Whether this status is rare enough that it should only be listed when it actually occurs.
A version of this status' name suitable for use as a title in a plot or table.
Attributes Documentation
- ABORTED = -4#
The quantum failed with a hard error that prevented both logs and metadata from being written.
This state is only set if information from higher-level tooling (e.g. BPS) is available to distinguish it from
UNKNOWN.
- ABORTED_SUCCESS = -2#
Task metadata was written for this attempt but logs were not.
This is a rare condition that requires a hard failure (i.e. the kind that can prevent a
finallyblock from running or I/O from being durable) at a very precise time.
- BLOCKED = 0#
This quantum was not executed because an upstream quantum failed.
Upstream quanta with status
UNKNOWN,FAILED, orABORTEDare considered blockers;ABORTED_SUCCESSis not.
- FAILED = -1#
Execution of the quantum failed gracefully.
This is always set if the task metadata dataset was not written but logs were, as is the case when a Python exception is caught and handled by the execution system.
This status guarantees that the task log dataset was produced but the metadata dataset was not.
- SUCCESSFUL = 1#
This quantum was successfully executed.
Quanta may be considered successful even if they do not write any outputs or shortcut early by raising
NoWorkFoundor one of its variants. They may even be considered successful if they raiseAnnotatedPartialOutputsErrorif the executor is configured to treat that exception as a non-failure. SeeQuantumSuccessCaveatsfor details on how these “successes with caveats” are reported.
- UNKNOWN = -3#
The status of this attempt is unknown.
This means no logs or metadata were written, and it at least could not be determined whether the quantum was blocked by an upstream failure (if it was definitely blocked,
BLOCKEDis set instead).
- has_log#
Whether the log dataset was produced.
- has_metadata#
Whether the task metadata dataset was produced.
- is_rare#
Whether this status is rare enough that it should only be listed when it actually occurs.
- title#
A version of this status’ name suitable for use as a title in a plot or table.