Repeat Sources Due to Check-pointing
The legacypipe code applied a series of check-points in case of failures during processing. Unfortunately, when the code resumed after a check-point failure, it sometimes produced a duplicate of the same source. These duplicates can be identified because they have identical coordinates and fluxes but a different OBJID. An example repeated source is here:
This source has the following attributes in catalog-level DR5 data:
|Attribute||Source 1||Source 2|
(i.e. fluxes and coordinates are identical but OBJID is different).
In DR6, we estimate that there are many thousands of duplicates spread across 264 bricks. The full list of DR6 bricks that contain duplicates, and the number of duplicates in each brick, is available here.
One brick was processed with a different pipeline version
Brick 1228p810 was processed with a different stack of codes, as detailed at the bottom of the description page.