-
Type:
Bug
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:1
Running reduceArc.py as follows:
reduceArc.py /projects/HSC/PFS/Subaru/ --calib /scratch/hassans/CALIB-20220504 --rerun hassans/calib/arc --id visit=68100 arm =r --config reduceExposure.isr.doFlat=False reduceExposure.isr.doApplyGains=True fitDetectorMap.doSlitOffsets=True reduceExposure.repair.doCosmicRay=False
Results in an error in accessing the appropriate CALIB detectormap:
lsst.daf.persistence.butlerExceptions.NoResults: No locations for get: datasetType:detectorMap dataId:DataId(initialdata={'visit': 68100, 'arm': 'r', 'dateObs': '2021-09-19', 'site' : 'S', 'category': 'A', 'spectrograph': 1, 'field': 'THROUGHFOCUS', 'ccd': 1, 'filter': 'r', 'expTime': 10.0, 'dataType': 'COMPARISON', 'taiObs': '2021-09-19T09:18:46.800', 'pfsDesignId': 512368543363980592, 'slitOffset': 0.0}, tag=set())
Even those the valid detectormap exists:
$ ls -l /scratch/hassans/CALIB-20220504/DETECTORMAP/pfsDetectorMap-068100-r1.fits -rw-rw-r--. 1 hassans astro 2136960 May 4 13:31 /scratch/hassans/CALIB-20220504/DETECTORMAP/pfsDetectorMap-068100-r1.fits
As suggested by Paul during a slack chat, looking at the detectormap table of the calib registry:
id|arm|ccd|spectrograph|calibDate|calibTime|visit0|validStart|validEnd 18|r|1|1|2021-09-19|2021-09-19T09:18:46.800|68100|2021-09-19T09:18:46.800000|2037-12-31T00:00:00
It appears that the problem is when the start of the validity range matches exactly to the calibTime value.
- relates to
-
PIPE2D-1023 Convert calibs to "validityUntilSuperseded" mode
-
- Done
-