LSST Applications g0f08755f38+9c285cab97,g1635faa6d4+13f3999e92,g1653933729+a8ce1bb630,g1a0ca8cf93+bf6eb00ceb,g28da252d5a+0829b12dee,g29321ee8c0+5700dc9eac,g2bbee38e9b+9634bc57db,g2bc492864f+9634bc57db,g2cdde0e794+c2c89b37c4,g3156d2b45e+41e33cbcdc,g347aa1857d+9634bc57db,g35bb328faa+a8ce1bb630,g3a166c0a6a+9634bc57db,g3e281a1b8c+9f2c4e2fc3,g414038480c+077ccc18e7,g41af890bb2+fde0dd39b6,g5fbc88fb19+17cd334064,g781aacb6e4+a8ce1bb630,g80478fca09+55a9465950,g82479be7b0+d730eedb7d,g858d7b2824+9c285cab97,g9125e01d80+a8ce1bb630,g9726552aa6+10f999ec6a,ga5288a1d22+2a84bb7594,gacf8899fa4+c69c5206e8,gae0086650b+a8ce1bb630,gb58c049af0+d64f4d3760,gc28159a63d+9634bc57db,gcf0d15dbbd+4b7d09cae4,gda3e153d99+9c285cab97,gda6a2b7d83+4b7d09cae4,gdaeeff99f8+1711a396fd,ge2409df99d+5e831397f4,ge79ae78c31+9634bc57db,gf0baf85859+147a0692ba,gf3967379c6+41c94011de,gf3fb38a9a8+8f07a9901b,gfb92a5be7c+9c285cab97,w.2024.46
LSST Data Management Base Package
|
Classes | |
class | ForcedMeasurementConfig |
class | ForcedMeasurementTask |
class | ForcedPlugin |
class | ForcedPluginConfig |
Base classes for forced measurement plugins and the driver task for these. In forced measurement, a reference catalog is used to define restricted measurements (usually just fluxes) on an image. As the reference catalog may be deeper than the detection limit of the measurement image, we do not assume that we can use detection and deblend information from the measurement image. Instead, we assume this information is present in the reference catalog and can be "transformed" in some sense to the measurement frame. At the very least, this means that `~lsst.afw.detection.Footprint`\ s from the reference catalog should be transformed and installed as Footprints in the output measurement catalog. If we have a procedure that can transform "heavy" Footprints (ie, including pixel data), we can then proceed with measurement as usual, but using the reference catalog's ``id`` and ``parent`` fields to define deblend families. If this transformation does not preserve heavy Footprints (this is currently the case, at least for CCD forced photometry), then we will only be able to replace objects with noise one deblend family at a time, and hence measurements run in single-object mode may be contaminated by neighbors when run on objects with ``parent != 0``. Measurements are generally recorded in the coordinate system of the image being measured (and all slot-eligible fields must be), but non-slot fields may be recorded in other coordinate systems if necessary to avoid information loss (this should, of course, be indicated in the field documentation). Note that the reference catalog may be in a different coordinate system; it is the responsibility of plugins to transform the data they need themselves, using the reference WCS provided. However, for plugins that only require a position or shape, they may simply use output `~lsst.afw.table.SourceCatalog`\'s centroid or shape slots, which will generally be set to the transformed position of the reference object before any other plugins are run, and hence avoid using the reference catalog at all. Command-line driver tasks for forced measurement include `ForcedPhotCcdTask`, and `ForcedPhotCoaddTask`.