LSSTApplications
10.0+286,10.0+36,10.0+46,10.0-2-g4f67435,10.1+152,10.1+37,11.0,11.0+1,11.0-1-g47edd16,11.0-1-g60db491,11.0-1-g7418c06,11.0-2-g04d2804,11.0-2-g68503cd,11.0-2-g818369d,11.0-2-gb8b8ce7
LSSTDataManagementBasePackage
|
Base class for plugin registries. More...
Classes | |
class | Configurable |
Class used as the actual element in the registry. More... | |
Public Member Functions | |
def | register |
Register a Plugin class with the given name. More... | |
def | makeField |
Base class for plugin registries.
The Plugin class allowed in the registry is defined in the ctor of the registry.
Single-frame and forced plugins have different registries.
Definition at line 56 of file pluginRegistry.py.
def lsst.meas.base.pluginRegistry.PluginRegistry.makeField | ( | self, | |
doc, | |||
default = None , |
|||
optional = False , |
|||
multi = False |
|||
) |
def lsst.meas.base.pluginRegistry.PluginRegistry.register | ( | self, | |
name, | |||
PluginClass, | |||
shouldApCorr = False , |
|||
apCorrList = () |
|||
) |
Register a Plugin class with the given name.
The same Plugin may be registered multiple times with different names; this can be useful if we often want to run it multiple times with different configuration.
[in] | name | name of plugin class. This is used as a prefix for all fields produced by the Plugin, and it should generally contain the name of the Plugin or Algorithm class itself as well as enough of the namespace to make it clear where to find the code. For example "base_GaussianFlux" indicates an algorithm in meas_base that measures Gaussian Flux and produces fields such as "base_GaussianFlux_flux", "base_GaussianFlux_fluxSigma" and "base_GaussianFlux_flag". |
[in] | shouldApCorr | if True then this algorithm measures a flux that should be aperture corrected. This is shorthand for apCorrList=[name] and is ignored if apCorrList is specified. |
[in] | apCorrList | list of field name prefixes for flux fields that should be aperture corrected. If an algorithm produces a single flux that should be aperture corrected then it is simpler to set shouldApCorr=True. But if an algorithm produces multiple such fields then it must specify apCorrList, instead. For example modelfit_CModel produces 3 such fields: apCorrList=("modelfit_CModel_exp", "modelfit_CModel_exp", "modelfit_CModel_def") If apCorrList is non-empty then shouldApCorr is ignored. |
Definition at line 90 of file pluginRegistry.py.