makeCoaddTempExp.py with doApplyUberCal=True to use meas_mosaic outputs fail to build warps despite the input data exist. A small example to reproduce on lsst-dev is:
makeCoaddTempExp.py /datasets/hsc/repo/ --rerun RC/w_2019_14/DM-18300:private/user/name --id tract=9615 filter=HSC-G patch=4,8 --selectId ccd=0..8^10..103 visit=26050^26036^26060^26032
|
This doesn't really "fail" (and no logs in ERROR or FATAL level) but instead gives many confusing/misleading warnings and produce no outputs:
WARN 2019-04-08T01:32:59.059 makeCoaddTempExp (DataId(initialdata={'tract': 9615, 'filter': 'HSC-G', 'patch': '4,8'}, tag=set()))(makeCoaddTempExp.py:341)- Calexp DataId(initialdata={'ccd': 103, 'visit': 26032, 'pointing': 1179, 'filter': 'HSC-G', 'field': 'SSP_WIDE', 'dateObs': '2015-03-25', 'taiObs': '2015-03-25', 'expTime': 150.0, 'tract': 9615}
|
, tag=set()) not found; skipping it: 'NoneType' object has no attribute'getInstFluxAtZeroMagnitude'
|
The log is misleading; this is DM-16537 about the generic exceptions. I troubleshoot a bit and trace to this line
https://github.com/lsst/meas_mosaic/blob/6e395ac11a625c877374f99e2bed771b427835b6/python/lsst/meas/mosaic/updateExposure.py#L103
where a non-empty header is obtained but no photoCalib is returned (that photCalib is None there). Feels like a bug in afw or meas_mosaic files; I paused there to file this ticket. Besides the bug, it'd be nice if the None calib is caught earlier.
Bug
Hsin-Fang Chiang
created issue -
Hsin-Fang Chiang
made changes -