Open johannct opened 5 years ago
Beyond the failures aesign matrix (1) must be smaller than number of data points (0)' bove (I lost track of the current situation so I need to check the dr1b-v1 logs again), this issue should capture the future decision as to whether we run skyCorrection or not eventually. In https://lsstc.slack.com/archives/C978LTJGN/p1561041974154300 the parameters set for Subaru in order to fix issues reported with skyCorrection there is recalled :
config.detection.doTempWideBackground = True
config.detection.tempWideBackground.binSize = 128
config.detection.tempWideBackground.useApprox = False
config.detection.reEstimateBackground = True
config.detection.background.binSize = 128
config.detection.background.useApprox = False
and the verbatim from Jim :
The relationship between those options and processCoadd is a red herring, but they may be of interest to obs_lsst. This gets back to the discussion about whether to do a large-scale or small-scale background subtraction and whether to run SkyCorrection: if you recall, I had warned during that discussion that HSC was unhappy with the impacts of large-scale backgrounds on the final catalogs, and we were leaning towards following up the large-scale SkyCorrection subtraction with a small-scale subtraction on the coadds, so the catalog we produce could have the benefits of small-scale subtraction while those interested in very extended objects could still re-insert the small-scale background model in order to make their own catalogs. These configs do exactly that, and were added very recently for the ongoing internal HSC DR. I should also note that these yield a very local background subtraction on the coadds, regarded by at least @rhl as probably too small.
This failure still present in 105 sensors in y3. See https://github.com/LSSTDESC/ImageProcessingPipelines/issues/111#issuecomment-504904524 . This is a small number, but it would be nice to know if something can be done, or if it is expected and entirely ok that skyCorrection fails sometimes. So do we need more forensic study @rearmstr ?
Example :