Since DB_MAPCOR parents are very bright, the real ``parent'' sources should be detected in all three bands. However, the pipeline has trouble cleanly detecting and band-merging each component of close visual multiple stars, sometimes resulting in single-band detections of one or more component stars and occasionally a set of false ``detections'' between the components.
DB_MAPCOR interpolates a better magnitude when
a parent source was not detected in one band, as follows:
j_m = 2.695 * h_m - 1.695 * k_m
h_m = 0.370 * j_m - 0.630 * k_m
k_m = 1.598 * h_m - 0.587 * j_m
However, when a parent source was not detected in two bands, it does not attempt to use the parent to find artifacts. There are 12 of these single-band parents that have no other ``good'' parent duplicate source in the database; all but one are members of close visual multiples. (``Good'' parents are found in the set of released scans, not already marked as artifacts, and have detections in two or three bands.) These parents and their unmarked artifacts are listed in section 2 below with comments and images.
MAPCOR used these sources as ``parents'' in one band during pipeline processing, so some of their artifacts have been flagged in that band; but since DB_MAPCOR did not used them as ``parents'', some diffraction spike artifacts found in nearby scans were not flagged. Only 28 artifacts from these parents are found in the PSC, for two reasons:
In the images below, the positions of the skipped parents are marked with a green star,
and the positions of the missed diffraction spike artifacts
are marked with a red ``x''.
A source described as a ``good extraction'' is found in the set of released scans,
is not already marked as an artifact, and has detections in two or three bands.
The Src column indicates whether the source is a skipped parent, ``par'',
or a missed artifact, ``art''.
The missed artifacts include both the current cc_flg values
and the values that they would have received
if the parents had not been skipped, cc_true;
the parents have blanks in cc_true.
From Davy Kirkpatrick's Sloane correlation analysis, I've identified a bug in v3 MAPCOR persistence searches. MAPCOR read in Read1 parents in the "low-coverage area", the start and end of the scan before and after the 6-frame-deep "full coverage" area. It used these sources as possible parents to find artifacts that could extend into the full-coverage area. (It then discarded these low-coverage sources and did not pass them on to the rest of the pipeline.)
However, there was a bug in the search for Read2-Read1 persistence sources when the parent was in the low-coverage area at the beginning of a south-going scan, and the predicted position of its first persistence source was north of (i.e. before) the first Read2-Read1 source in the scan. (MAPCOR used the minimum and maximum y coordinates of the Read2-Read1 sources to define the Read2-Read1 "full coverage" area, so its full coverage area was almost always smaller than the actual 6-frame sky coverage area.) When the predicted position was north of MAPCOR's "full coverage" area, the initial persistence search would recognize this and set a flag that would prevent MAPCOR from doing further Read2-Read1 persistence searches at later -- in this case, more southern -- frame positions. My intent with this flag was to stop searching when moving away from the full-coverage area, but unfortunately in this case it actually is moving into the full-coverage area.
This bug does not affect persistence searches with parents in, or less than 1 frame away from, MAPCOR's Read2-Read1 full-coverage area, or in north-going scans. It also does not affect searches for Read1 persistence sources, nor any other type of artifact searches (e.g., glints, diffraction spikes, etc.).
As far as I know, only one of these sources has been found so far during v3 analysis. Because the data on the number of frames searched for persistence has not been kept in the database, I can't find an easy way to count the number of sources missing persistence probabilities because of this bug. Therefore, at Gene Kopan's suggestion, I counted the number of sources in the working database and the catalog with persistence parents in the low-coverage area to get an idea of the scope of the problem. In the table below, pprob is the persistence probability, WDB is the working database table, and PSC is the point source catalog.
Approximately half of all survey scans, the north-going scans, were not affected by this bug. A more precise count gives us 35309 north-going scans and 35403 south-going scans in the WDB, and 29830 north-going scans and 29901 south-going scans in the PSC scan set. In both cases, the fractions of north- and south-going scans are each 0.50, to within 0.001. If we assume that the north- and south-going scans are distributed randomly over the sky, half of the WDB and PSC sources should be found in north-going scans and the other half in south-going scans. This means that approximately half of this type of persistence sources were flagged correctly, and half were not.
To guess how many unreliable sources, with true pprob > 0.5, and persistence-affected sources, with true pprob <= 0.5, were unflagged, we could get the upper limits from the sources that do have pprob values in the PSC and WDB and have persistence parents from the low-coverage area (see the first two lines of the table below). Only 20-25% of these pprob <= 0.5 sources in the WDB are also found in the PSC, probably because most of them are real sources that happen to fall on a persistence position and thus have duplicate extractions in neighboring scans. These duplicates are likely to be farther from the scan edges and therefore would be selected in the duplicate-resolution processing, and they will either have full-coverage persistence parents if their scans run in the same direction as the scans with low-coverage parents, or will not fall on a persistence position if their scans run in the opposite direction.
However, not all parents will be able to create more than one persistence source, as required for this bug to occur. The numbers of low-coverage parents creating more than one persistence source in the DB are found in the third and fourth lines of the table, and the numbers of persistence sources created or affected by these parents are found in the fifth and sixth lines. Unfortunately, we can only get these counts one band at a time, so the "any band" category is left blank. Since approximately 76% of the sources in the PSC are 3-band sources, these counts will certainly overestimate the number of persistence sources from low-coverage parents.
Assuming that approximately half of this type of persistence sources
were flagged correctly, and half were not, and
ignoring the fact that most of the sources are 3-band, not single-band,
the last two lines of the table are a reasonable estimate of
the maximum number of missed persistence sources.
A maximum of 94364 WDB sources
should have had pprob > 0.5;
if about 17%, 24%, and 19% of them in the
J, H, and Ks bands respectively are in the PSC,
the catalog contains approximately 5621, 9965, and 3758
missed persistence artifacts in J, H, and Ks,
or 19344 total.
This is 0.0041% of the total number of sources in the PSC (470992970).
The maximum number of missed WDB sources
that should have had pprob <= 0.5 is approximately 117092;
the PSC contains approximately 4130, 10492, and 9273 of these sources
in J, H, and Ks, or 23895 total.
This is 0.0051% of the total sources in the PSC.
Because of the assumptions made here,
these numbers are definitely overestimates
by at most a factor of 3.
| # of sources in WDB | # of sources in PSC (# in PSC / # in WDB) | ||||||||
| J band | H band | Ks band | any band | J band | H band | Ks band | any band | ||
| pprob > 0.5 | 53629 | 53643 | 30954 | 83226 | -- | -- | -- | -- | |
| pprob <= 0.5 | 36162 | 60593 | 67009 | 106636 | 7336 (0.20) | 15364 (0.25) | 14550 (0.22) | 24084 (0.23) | |
| parents w/ > 1 src having pprob > 0.5 | 9692 | 10723 | 6208 | -- | -- | -- | -- | -- | |
| parents w/ > 1 src having pprob <= 0.5 | 7930 | 12861 | 15556 | -- | 1392 (0.18) | 3159 (0.25) | 3139 (0.20) | -- | |
| srcs from parents w/ > 1 src having pprob > 0.5 | 33063 | 41521 | 19780 | -- | -- | -- | -- | -- | |
| srcs from parents w/ > 1 src having pprob <= 0.5 | 24362 | 44618 | 48112 | -- | 4130 (0.17) | 10492 (0.24) | 9273 (0.19) | -- | |