LatissMonolithTaskConnections#
- class lsst.ts.wep.task.LatissMonolithTaskConnections(*, config=None)#
Bases:
PipelineTaskConnectionsConnections for LatissMonolithTask.
One quantum per CWFS pair, keyed on the extra-focal visit, as the ts_wep paired tasks and
donutBlitzMonolithare. The pairing happens at graph-build time inadjust_all_quanta: the default graph gives every exposure its own quantum holding its own raw; the intra-focal raw is then moved into its partner’s quantum and the intra quantum dropped. Keying on visit is what makes_log/_metadataper pair – with a per-night or per-run quantum every pair in a long-lived output run (rapid analysis reusesLATISS/runs/quickLook/N) would write the same dataId and the second pair would fail on the provenance datasets.visitalso impliesday_obs, so the calibration lookup is time-bounded.Attributes Summary
Mapping holding all connection attributes.
Class used for declaring PipelineTask prerequisite connections.
Class used for declaring PipelineTask prerequisite connections.
Class used for declaring PipelineTask prerequisite connections.
Class used for declaring PipelineTask prerequisite connections.
Class used for declaring PipelineTask prerequisite connections.
Set of dimension names that define the unit of work for this task.
Connection for output dataset.
Connection for output dataset.
Class used for declaring PipelineTask prerequisite connections.
Set with the names of all
InitInputconnection attributes.Set with the names of all
InitOutputconnection attributes.Set with the names of all
connectionTypes.Inputconnection attributes.Class used for declaring PipelineTask prerequisite connections.
Set with the names of all
Outputconnection attributes.Set with the names of all
PrerequisiteInputconnection attributes.Class used for declaring PipelineTask prerequisite connections.
Class used for declaring PipelineTask input connections.
Connection for output dataset.
Methods Summary
adjust_all_quanta(adjuster)Turn one-quantum-per-exposure into one-quantum-per-pair.
Attributes Documentation
- allConnections: Mapping[str, BaseConnection] = {'bias': PrerequisiteInput(name='bias', storageClass='ExposureF', doc='Combined bias calibration frame.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'camera': PrerequisiteInput(name='camera', storageClass='Camera', doc='Input camera geometry.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument',), isCalibration=True, deferLoad=False, minimum=1, lookupFunction=None), 'crosstalk': PrerequisiteInput(name='crosstalk', storageClass='CrosstalkCalib', doc='Intra-detector crosstalk coefficients.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'dark': PrerequisiteInput(name='dark', storageClass='ExposureF', doc='Combined dark calibration frame.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'defects': PrerequisiteInput(name='defects', storageClass='Defects', doc='Defect list; masks the bad LATISS column that otherwise outranks the donut.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'donutStampsExtra': Output(name='donutStampsExtra', storageClass='StampsBase', doc='Extra-focal donut postage stamps.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('visit', 'detector', 'instrument'), isCalibration=False), 'donutStampsIntra': Output(name='donutStampsIntra', storageClass='StampsBase', doc='Intra-focal donut postage stamps, stored under the extra-focal visit.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('visit', 'detector', 'instrument'), isCalibration=False), 'flat': PrerequisiteInput(name='flat', storageClass='ExposureF', doc='Combined flat calibration frames, one per physical_filter.', multiple=True, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector', 'physical_filter'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'linearizer': PrerequisiteInput(name='linearizer', storageClass='Linearizer', doc='Linearity correction calibration.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'ptc': PrerequisiteInput(name='ptc', storageClass='PhotonTransferCurveDataset', doc='Photon transfer curve dataset. Required by IsrTaskLSST.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('instrument', 'detector'), isCalibration=True, deferLoad=False, minimum=0, lookupFunction=None), 'raws': Input(name='raw', storageClass='Exposure', doc="Raw LATISS exposures of one CWFS pair: the extra-focal raw of this quantum's visit plus its intra-focal partner, attached by adjust_all_quanta.", multiple=True, deprecated=None, _deprecation_context='', dimensions=('instrument', 'exposure', 'detector'), isCalibration=False, deferLoad=True, minimum=1, deferGraphConstraint=False, deferBinding=False), 'zernikes': Output(name='zernikes', storageClass='AstropyQTable', doc='Zernike coefficients for the pair and an average row, with fit quality columns.', multiple=False, deprecated=None, _deprecation_context='', dimensions=('visit', 'detector', 'instrument'), isCalibration=False)}#
Mapping holding all connection attributes.
This is a read-only view that is automatically updated when connection attributes are added, removed, or replaced in
__init__. It is also updated after__init__completes to reflect changes ininputs,prerequisiteInputs,outputs,initInputs, andinitOutputs.
- bias#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- camera#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- crosstalk#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- dark#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- defaultTemplates = {}#
- defects#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- deprecatedTemplates = {}#
- dimensions: set[str] = {'detector', 'instrument', 'visit'}#
Set of dimension names that define the unit of work for this task.
Required and implied dependencies will automatically be expanded later and need not be provided.
This may be replaced or modified in
__init__to change the dimensions of the task. After__init__it will be afrozensetand may not be replaced.
- donutStampsExtra#
Connection for output dataset.
- donutStampsIntra#
Connection for output dataset.
- flat#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- initInputs: set[str] = frozenset({})#
Set with the names of all
InitInputconnection attributes.See
inputsfor additional information.
- initOutputs: set[str] = frozenset({})#
Set with the names of all
InitOutputconnection attributes.See
inputsfor additional information.
- inputs: set[str] = frozenset({'raws'})#
Set with the names of all
connectionTypes.Inputconnection attributes.This is updated automatically as class attributes are added, removed, or replaced in
__init__. Removing entries from this set will cause those connections to be removed after__init__completes, but this is supported only for backwards compatibility; new code should instead just delete the collection attributed directly. After__init__this will be afrozensetand may not be replaced.
- linearizer#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- outputs: set[str] = frozenset({'donutStampsExtra', 'donutStampsIntra', 'zernikes'})#
Set with the names of all
Outputconnection attributes.See
inputsfor additional information.
- prerequisiteInputs: set[str] = frozenset({'bias', 'camera', 'crosstalk', 'dark', 'defects', 'flat', 'linearizer', 'ptc'})#
Set with the names of all
PrerequisiteInputconnection attributes.See
inputsfor additional information.
- ptc#
Class used for declaring PipelineTask prerequisite connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.
Notes
Prerequisite inputs are used for datasets that must exist in the data repository before a pipeline including this is run; they cannot be produced by another task in the same pipeline.
In exchange for this limitation, they have a number of advantages relative to regular
Inputconnections:The query used to find them then during
QuantumGraphgeneration can be fully customized by providing alookupFunction.Failed searches for prerequisites during
QuantumGraphgeneration will usually generate more helpful diagnostics than those for regularInputconnections.The default query for prerequisite inputs relates the quantum dimensions directly to the dimensions of its dataset type, without being constrained by any of the other dimensions in the pipeline. This allows them to be used for temporal calibration lookups (which regular
Inputconnections cannot do at present) and to work aroundQuantumGraphgeneration limitations involving cases where naive spatial overlap relationships between dimensions are not desired (e.g. a task that wants all detectors in each visit for which the visit overlaps a tract, not just those where that detector+visit combination overlaps the tract).Prerequisite inputs may be optional (regular inputs are never optional).
- raws#
Class used for declaring PipelineTask input connections.
- Raises:
TypeError – Raised if
minimumis greater than one butmultiple=False.NotImplementedError – Raised if
minimumis zero for a regularInputconnection; this is not currently supported by our QuantumGraph generation algorithm.
- zernikes#
Connection for output dataset.
Methods Documentation
- adjust_all_quanta(adjuster)#
Turn one-quantum-per-exposure into one-quantum-per-pair.
Every exposure in the data query starts with its own quantum. An exposure whose
observation_reasoncontainsextrakeeps its quantum and receives the raw of the intra-focal exposure taken immediately before it (seq_num - 1on the same night, which is howlatiss_wep_aligntakes the pair). All other quanta are removed: intra exposures once their raw has been re-homed, and unpaired extras (whose partner was not in the query or is not markedintra), with a warning. This mirrorsReassignCwfsCutoutsFamTaskfor the LSSTCam FAM pipeline. A data query naming both exposures of the pair, e.g.exposure in (17, 18), is therefore all that is required; nothing needs to be said about which is which.- Parameters:
adjuster (
QuantaAdjuster)- Return type: