Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: meas_algorithms, meas_photocal, obs_cfht, obs_sdss, obs_subaru, obs_test, pipe_tasks
-
Labels:None
-
Team:Data Access and Database
Description
There are some configuration issues associated with reference catalogs, including:
1) Determining the source of the reference catalog. This information is used in two ways:
- mapping the filter used to take an exposure to a filter in a reference catalog, for matching sources to reference objects (e.g. for astrometry and photometry)
- picking the correct set of colorterms based on the filter and type of CCD used for the science image and filters in the reference catalog
At present this information is encoded in the eups version name of the astrometry_net_data package used. This requires the use of eups and assumes astrometry.net index files. This is the most serious immediate issue.
2) Colorterm correction data is saved in obs_* packages as config files. This makes it harder to include a temporal component.
This ticket is a request for a cleaner solution.
The plan has been to wait for "the new butler", e.g. DM-2404 (taking this use case into account in its design) before designing the solution. However, if we need something sooner, one possibility for fixing the first problem is to put the source of the reference catalog into metadata attached to the reference catalog.
John Swinbank your reading of the ticket is exactly the opposite of what I intended when I wrote it. I'm sorry I was not clearer.
What I want is a clean solution for this problem. That implies not a short-term workaround, but a good, solid fix. I think it should be fixed in the new butler, and that this represents an unusual and important use case for that butler.
However, if somebody does have a better short-term solution, I'm willing to accept it.