LSSTApplications
19.0.0-14-gb0260a2+72efe9b372,20.0.0+7927753e06,20.0.0+8829bf0056,20.0.0+995114c5d2,20.0.0+b6f4b2abd1,20.0.0+bddc4f4cbe,20.0.0-1-g253301a+8829bf0056,20.0.0-1-g2b7511a+0d71a2d77f,20.0.0-1-g5b95a8c+7461dd0434,20.0.0-12-g321c96ea+23efe4bbff,20.0.0-16-gfab17e72e+fdf35455f6,20.0.0-2-g0070d88+ba3ffc8f0b,20.0.0-2-g4dae9ad+ee58a624b3,20.0.0-2-g61b8584+5d3db074ba,20.0.0-2-gb780d76+d529cf1a41,20.0.0-2-ged6426c+226a441f5f,20.0.0-2-gf072044+8829bf0056,20.0.0-2-gf1f7952+ee58a624b3,20.0.0-20-geae50cf+e37fec0aee,20.0.0-25-g3dcad98+544a109665,20.0.0-25-g5eafb0f+ee58a624b3,20.0.0-27-g64178ef+f1f297b00a,20.0.0-3-g4cc78c6+e0676b0dc8,20.0.0-3-g8f21e14+4fd2c12c9a,20.0.0-3-gbd60e8c+187b78b4b8,20.0.0-3-gbecbe05+48431fa087,20.0.0-38-ge4adf513+a12e1f8e37,20.0.0-4-g97dc21a+544a109665,20.0.0-4-gb4befbc+087873070b,20.0.0-4-gf910f65+5d3db074ba,20.0.0-5-gdfe0fee+199202a608,20.0.0-5-gfbfe500+d529cf1a41,20.0.0-6-g64f541c+d529cf1a41,20.0.0-6-g9a5b7a1+a1cd37312e,20.0.0-68-ga3f3dda+5fca18c6a4,20.0.0-9-g4aef684+e18322736b,w.2020.45
LSSTDataManagementBasePackage
|
Functions | |
def | lookupStaticCalibration (datasetType, registry, quantumDataId, collections) |
def lsst.cp.pipe._lookupStaticCalibration.lookupStaticCalibration | ( | datasetType, | |
registry, | |||
quantumDataId, | |||
collections | |||
) |
A lookup function override for QuantumGraph generation that allows a PipelineTask to have an input dataset (usually a camera) that is formally a calibration with a validity range, without having a temporal data ID for the lookup, by asserting that there is in fact only dataset for all time. Parameters ---------- datasetType : `lsst.daf.butler.DatasetType` Dataset type to look up. registry : `lsst.daf.butler.Registry` Registry for the data repository being searched. quantumDataId : `lsst.daf.butler.DataCoordinate` Data ID for the quantum of the task this dataset will be passed to. This must include an "instrument" key, and should also include any keys that are present in ``datasetType.dimensions``. If it has an ``exposure`` or ``visit`` key, that's a sign that this function is not actually needed, as those come with the temporal information that would allow a real validity-range lookup. collections : `lsst.daf.butler.registry.CollectionSearch` Collections passed by the user when generating a QuantumGraph. Ignored by this function (see notes below). Returns ------- refs : `list` [ `DatasetRef` ] A zero- or single-element list containing the matching dataset, if one was found. Notes ----- This works by looking in the `~CollectionType.RUN` collection that `lsst.obs.base.Instrument.writeCuratedCalibrations` (currently!) uses, instead of the collections passed into it. This may be considered surprising by users (but will usually go unnoticed because the dataset returned _is_ actually in those given input colllections, too). It may stop working entirely once we have data repositories with multiple calibration collections; a better workaround or a more principled change to the PipelineTasks that use this function (which are by definition asking for something ill-defined) will ultimately be needed.
Definition at line 27 of file _lookupStaticCalibration.py.