Fix Version/s: None
Team:Data Release Production
Recently, while processing MADCASH (observations of local dwarf galaxies), I noticed a vast improvement in astrometric matching when I set:
We should make these the default for HSC.
DM-9870 Release hscPipe 5.0-beta1
This is basically one of the major problems with the current matcher set up. Turns out in denser fields 50 bright stars is too few to successfully match on.
One quick question before I approve this change, have you tried excluding saturated and interpolated objects from the source sample? I found that in dense stellar fields the first 50 objects by brightness are all saturated and causes the matcher to fail or give bad fits. I'm likely going to change the matcherSourceSelector to exclude these objects completely and instead rely on a S/N cut to pull in more objects if needed. Would be interesting to hear if you also have problem with saturated objects.
Unfortunately no. You'd have to change the ordering of the isUseable and isGood flags in matchOptimsiticBTask or just switch isUseable for isGood. I'm going to hopefully implement this change as part of
DM-9750. I'll mark this ticket as reviewed. These are the visit numbers you sent me previously correct? I'll take a look at them once I start my validating my replacement matcher against a large volume of data.
This passed Jenkins.
Chris Morrison [X], would you mind giving this simple change a quick look, as I believe you grok this stuff.