FormatterFactory¶
- class lsst.daf.butler.FormatterFactory¶
Bases:
object
Factory for
Formatter
instances.Attributes Summary
Configuration key associated with default write parameter settings.
Configuration key associated with write recipes.
Methods Summary
getFormatter
(entity, *args, **kwargs)Get a new formatter instance.
getFormatterClass
(entity)Get the matching formatter class.
getFormatterClassWithMatch
(entity)Get the matching formatter class along with the registry key.
getFormatterWithMatch
(entity, *args, **kwargs)Get a new formatter instance along with the matching registry key.
Retrieve the look up keys for all the registry entries.
registerFormatter
(type_, formatter, *[, ...])Register a
Formatter
.registerFormatters
(config, *, universe)Bulk register formatters from a config.
Attributes Documentation
- defaultKey = LookupKey(name='default',)¶
Configuration key associated with default write parameter settings.
- writeRecipesKey = LookupKey(name='write_recipes',)¶
Configuration key associated with write recipes.
Methods Documentation
- getFormatter(entity: DatasetType | DatasetRef | StorageClass | str, *args: Any, **kwargs: Any) Formatter ¶
Get a new formatter instance.
- Parameters:
- entity
DatasetRef
,DatasetType
,StorageClass
, orstr
Entity to use to determine the formatter to return.
StorageClass
will be used as a last resort ifDatasetRef
orDatasetType
instance is provided. Supports instrument override if aDatasetRef
is provided configured with aninstrument
value for the data ID.- args
tuple
Positional arguments to use pass to the object constructor.
- **kwargs
Keyword arguments to pass to object constructor.
- entity
- Returns:
- formatter
Formatter
An instance of the registered formatter.
- formatter
- getFormatterClass(entity: DatasetType | DatasetRef | StorageClass | str) Type ¶
Get the matching formatter class.
- Parameters:
- entity
DatasetRef
,DatasetType
,StorageClass
, orstr
Entity to use to determine the formatter to return.
StorageClass
will be used as a last resort ifDatasetRef
orDatasetType
instance is provided. Supports instrument override if aDatasetRef
is provided configured with aninstrument
value for the data ID.
- entity
- Returns:
- formatter
type
The class of the registered formatter.
- formatter
- getFormatterClassWithMatch(entity: DatasetType | DatasetRef | StorageClass | str) Tuple[LookupKey, Type[Formatter], Dict[str, Any]] ¶
Get the matching formatter class along with the registry key.
- Parameters:
- entity
DatasetRef
,DatasetType
,StorageClass
, orstr
Entity to use to determine the formatter to return.
StorageClass
will be used as a last resort ifDatasetRef
orDatasetType
instance is provided. Supports instrument override if aDatasetRef
is provided configured with aninstrument
value for the data ID.
- entity
- Returns:
- getFormatterWithMatch(entity: DatasetType | DatasetRef | StorageClass | str, *args: Any, **kwargs: Any) Tuple[LookupKey, Formatter] ¶
Get a new formatter instance along with the matching registry key.
- Parameters:
- entity
DatasetRef
,DatasetType
,StorageClass
, orstr
Entity to use to determine the formatter to return.
StorageClass
will be used as a last resort ifDatasetRef
orDatasetType
instance is provided. Supports instrument override if aDatasetRef
is provided configured with aninstrument
value for the data ID.- args
tuple
Positional arguments to use pass to the object constructor.
- **kwargs
Keyword arguments to pass to object constructor.
- entity
- Returns:
- registerFormatter(type_: LookupKey | str | StorageClass | DatasetType, formatter: str, *, overwrite: bool = False, **kwargs: Any) None ¶
Register a
Formatter
.- Parameters:
- type_
LookupKey
,str
,StorageClass
orDatasetType
Type for which this formatter is to be used. If a
LookupKey
is not provided, one will be constructed from the supplied string or by using thename
property of the supplied entity.- formatter
str
or class of typeFormatter
Identifies a
Formatter
subclass to use for reading and writing Datasets of this type. Can be aFormatter
class.- overwrite
bool
, optional If
True
an existing entry will be replaced by the new value. Default isFalse
.- **kwargs
Keyword arguments to always pass to object constructor when retrieved.
- type_
- Raises:
- ValueError
Raised if the formatter does not name a valid formatter type and
overwrite
isFalse
.
- registerFormatters(config: Config, *, universe: DimensionUniverse) None ¶
Bulk register formatters from a config.
- Parameters:
- config
Config
formatters
section of a configuration.- universe
DimensionUniverse
, optional Set of all known dimensions, used to expand and validate any used in lookup keys.
- config
Notes
The configuration can include one level of hierarchy where an instrument-specific section can be defined to override more general template specifications. This is represented in YAML using a key of form
instrument<name>
which can then define templates that will be returned if aDatasetRef
contains a matching instrument name in the data ID.The config is parsed using the function
processLookupConfigs
.The values for formatter entries can be either a simple string referring to a python type or a dict representing the formatter and parameters to be hard-coded into the formatter constructor. For the dict case the following keys are supported:
formatter: The python type to be used as the formatter class.
- parameters: A further dict to be passed directly to the
writeParameters
Formatter constructor to seed it. These parameters are validated at instance creation and not at configuration.
Additionally, a special
default
section can be defined that uses the formatter type (class) name as the keys and specifies default write parameters that should be used whenever an instance of that class is constructed.formatters: default: lsst.daf.butler.formatters.example.ExampleFormatter: max: 10 min: 2 comment: Default comment calexp: lsst.daf.butler.formatters.example.ExampleFormatter coadd: formatter: lsst.daf.butler.formatters.example.ExampleFormatter parameters: max: 5
Any time an
ExampleFormatter
is constructed it will use those parameters. If an explicit entry later in the configuration specifies a different set of parameters, the two will be merged with the later entry taking priority. In the example abovecalexp
will use the default parameters butcoadd
will override the value formax
.Formatter configuration can also include a special section describing collections of write parameters that can be accessed through a simple label. This allows common collections of options to be specified in one place in the configuration and reused later. The
write_recipes
section is indexed by Formatter class name and each key is the label to associate with the parameters.formatters: write_recipes: lsst.obs.base.formatters.fitsExposure.FixExposureFormatter: lossless: ... noCompression: ...
By convention a formatter that uses write recipes will support a
recipe
write parameter that will refer to a recipe name in thewrite_recipes
component. TheFormatter
will be constructed in theFormatterFactory
with all the relevant recipes and will not attempt to filter by looking atwriteParameters
in advance. See the specific formatter documentation for details on acceptable recipe options.