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 - NoWorkFoundwas raised by- PipelineTaskConnnections.adjustQuantum.- No predicted outputs (except logs and metadata) were produced. - At least one predicted output was not produced. - A subclass of - NoWorkFoundwas raised.- AnnotatedPartialOutputsErrorwas raised by- PipelineTask.runQuantumand the execution system was instructed to consider this a qualified success.- UnprocessableDataErrorwas raised by- PipelineTask.runQuantum.- UpstreamFailureNoWorkFoundwas raised by- PipelineTask.runQuantum.- Attributes Documentation - ADJUST_QUANTUM_RAISED = 8¶
- NoWorkFoundwas raised by- PipelineTaskConnnections.adjustQuantum.- This indicates that if a new - QuantumGraphhad 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 original- QuantumGraph) were not actually produced.- NO_WORKand- ALL_OUTPUTS_MISSINGare also set whenever this flag is set.
 - ALL_OUTPUTS_MISSING = 2¶
- No predicted outputs (except logs and metadata) were produced. - ANY_OUTPUTS_MISSINGis 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 - NoWorkFoundwas raised.- This does not necessarily imply that - ANY_OUTPUTS_MISSINGis not set, since a- PipelineTask.runQuantumimplementation could raise it after directly writing all of its predicted outputs.
 - PARTIAL_OUTPUTS_ERROR = 64¶
- AnnotatedPartialOutputsErrorwas raised by- PipelineTask.runQuantumand the execution system was instructed to consider this a qualified success.
 - UNPROCESSABLE_DATA = 32¶
- UnprocessableDataErrorwas raised by- PipelineTask.runQuantum.- NO_WORKis also set whenever this flag is set.
 - UPSTREAM_FAILURE_NO_WORK = 16¶
- UpstreamFailureNoWorkFoundwas raised by- PipelineTask.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_WORKis also set whenever this flag is set.