QuantumSuccessCaveats¶
- class lsst.pipe.base.QuantumSuccessCaveats(value, names=<not given>, *values, module=None, qualname=None, type=None, start=1, boundary=None)¶
Bases:
Flag
Flags that add caveats to a “successful” quantum.
Quanta can be considered successful even if they do not produce some of their expected outputs (and even if they do not produce all of their expected outputs), as long as the condition is sufficiently well understood that downstream processing should succeed.
Attributes Summary
NoWorkFound
was raised byPipelineTaskConnnections.adjustQuantum
.No predicted outputs (except logs and metadata) were produced.
At least one predicted output was not produced.
A subclass of
NoWorkFound
was raised.AnnotatedPartialOutputsError
was raised byPipelineTask.runQuantum
and the execution system was instructed to consider this a qualified success.UnprocessableDataError
was raised byPipelineTask.runQuantum
.UpstreamFailureNoWorkFound
was raised byPipelineTask.runQuantum
.Attributes Documentation
- ADJUST_QUANTUM_RAISED = 8¶
NoWorkFound
was raised byPipelineTaskConnnections.adjustQuantum
.This indicates that if a new
QuantumGraph
had been generated immediately before running this quantum, that quantum would not have even been included, because required inputs that were expected to exist by the time it was run (in the originalQuantumGraph
) were not actually produced.NO_WORK
andALL_OUTPUTS_MISSING
are also set whenever this flag is set.
- ALL_OUTPUTS_MISSING = 2¶
No predicted outputs (except logs and metadata) were produced.
ANY_OUTPUTS_MISSING
is also set whenever this flag is set.
- ANY_OUTPUTS_MISSING = 1¶
At least one predicted output was not produced.
- NO_WORK = 4¶
A subclass of
NoWorkFound
was raised.This does not necessarily imply that
ANY_OUTPUTS_MISSING
is not set, since aPipelineTask.runQuantum
implementation could raise it after directly writing all of its predicted outputs.
- PARTIAL_OUTPUTS_ERROR = 64¶
AnnotatedPartialOutputsError
was raised byPipelineTask.runQuantum
and the execution system was instructed to consider this a qualified success.
- UNPROCESSABLE_DATA = 32¶
UnprocessableDataError
was raised byPipelineTask.runQuantum
.NO_WORK
is also set whenever this flag is set.
- UPSTREAM_FAILURE_NO_WORK = 16¶
UpstreamFailureNoWorkFound
was raised byPipelineTask.runQuantum
.This exception is raised by downstream tasks when an upstream task’s outputs were incomplete in a way that blocks it from running, often because the upstream task raised
AnnotatedPartialOutputsError
.NO_WORK
is also set whenever this flag is set.