This list includes "difficult" stars.
Difficult stars are the ones that had matching collisions. In other words, the same Gaia star
was matched to more than one AGASC star. Difficult stars are divided in equivalence classes,
based on which stars it collided. Often these stars are duplicates in AGASC, but not always.
The purpose of this report is to check whether outliers can be caused by misidentification.
When looking at the report for a given outlier, consider that if the true match is a star with no
proper motion in Gaia, then there should be an AGASC star matched to this Gaia star. Is there one?
If you double-click on a report's figure, it will zoom out and show you all AGASC stars around.
Notable examples:
-
181023536-et-al . The most difficult one.
-
11931168 . Two stars in AGASC matched to two in Gaia, but
they are difficult. The table values are masked. NEED TO CHECK.
-
980817608 . Three stars in AGASC, but only one in Gaia.
Two of the AGASC stars are from GSC2.3 and are separated by 6 arcsec. The other star is a
Tycho2 star right in between. The Gaia star matches the Tycho2 star. Sounds like a spurious
binary system identification in GSC2.3, which should correspond to the single Tycho star.
-
5253584 . Three stars in AGASC matched to one in Gaia.
Two of the three are Tycho2 stars at the exact same location. The third is an older catalog.
-
77996162 . Four stars in AGASC matched to two in Gaia.
-
23877032 . Three stars in AGASC matched to one in Gaia.
Two are duplicates.
-
102499593 . Two stars in AGASC matched to three in Gaia.
[102499592, 102499593, 102499594]. One star is a duplicate. Fortunately, this is the one that
is matched to a third Gaia star, and is removed based on p-value. It could have happened that
the duplicate gets a better p-value than one of the other two, so one of the other two is not
updated, and the duplicate is updated instead. Duplicates must be removed from the match candidates.
Stars