ConfigChoiceField¶
-
class
lsst.pex.config.ConfigChoiceField(doc, typemap, default=None, optional=False, multi=False, deprecated=None)¶ Bases:
lsst.pex.config.FieldA configuration field (
Fieldsubclass) that allows a user to choose from a set ofConfigtypes.Parameters: - doc :
str Documentation string for the field.
- typemap :
dict-like A mapping between keys and
Config-types as values. See Examples for details.- default :
str, optional The default configuration name.
- optional :
bool, optional When
False,lsst.pex.config.Config.validatewill fail if the field’s value isNone.- multi :
bool, optional If
True, the field allows multiple selections. In this case, set the selections by assigning a sequence to thenamesattribute of the field.If
False, the field allows only a single selection. In this case, set the active config by assigning the config’s key from thetypemapto the field’snameattribute (see Examples).- deprecated : None or
str, optional A description of why this Field is deprecated, including removal date. If not None, the string is appended to the docstring for this Field.
See also
ChoiceField,ConfigDictField,ConfigField,ConfigurableField,DictField,Field,ListField,RangeField,RegistryFieldNotes
ConfigChoiceFieldinstances can allow either single selections or multiple selections, depending on themultiparameter. For single-selection fields, set the selection with thenameattribute. For multi-selection fields, set the selection though thenamesattribute.This field is validated only against the active selection. If the
activeattribute isNoneand the field is not optional, validation will fail.When saving a configuration with a
ConfigChoiceField, the entire set is saved, as well as the active selection.Examples
While the
typemapis shared by all instances of the field, each instance of the field has its own instance of a particular sub-config type.For example,
AaaConfigis a config object>>> from lsst.pex.config import Config, ConfigChoiceField, Field >>> class AaaConfig(Config): ... somefield = Field("doc", int) ...
The
MyConfigconfig has aConfigChoiceFieldfield calledchoicethat maps theAaaConfigtype to the"AAA"key:>>> TYPEMAP = {"AAA", AaaConfig} >>> class MyConfig(Config): ... choice = ConfigChoiceField("doc for choice", TYPEMAP) ...
Creating an instance of
MyConfig:>>> instance = MyConfig()
Setting value of the field
somefieldon the “AAA” key of thechoicefield:>>> instance.choice['AAA'].somefield = 5
Selecting the active configuration
Make the
"AAA"key the active configuration value for thechoicefield:>>> instance.choice = "AAA"
Alternatively, the last line can be written:
>>> instance.choice.name = "AAA"
(If the config instance allows multiple selections, you’d assign a sequence to the
namesattribute instead.)ConfigChoiceFieldinstances also allow multiple values of the same type:>>> TYPEMAP["CCC"] = AaaConfig >>> TYPEMAP["BBB"] = AaaConfig
Attributes Summary
supportedTypesMethods Summary
freeze(instance)Make this field read-only (for internal use only). rename(instance)Rename the field in a Config(for internal use only).save(outfile, instance)Save this field to a file (for internal use only). toDict(instance)Convert the field value so that it can be set as the value of an item in a dict(for internal use only).validate(instance)Validate the field (for internal use only). Attributes Documentation
-
supportedTypes= {<class 'complex'>, <class 'int'>, <class 'float'>, <class 'bool'>, <class 'str'>}¶
Methods Documentation
-
freeze(instance)¶ Make this field read-only (for internal use only).
Parameters: - instance :
lsst.pex.config.Config The config instance that contains this field.
Notes
Freezing is only relevant for fields that hold subconfigs. Fields which hold subconfigs should freeze each subconfig.
Subclasses should implement this method.
- instance :
-
rename(instance)¶ Rename the field in a
Config(for internal use only).Parameters: - instance :
lsst.pex.config.Config The config instance that contains this field.
Notes
This method is invoked by the
lsst.pex.config.Configobject that contains this field and should not be called directly.Renaming is only relevant for
Fieldinstances that hold subconfigs.Fieldsthat hold subconfigs should rename each subconfig with the full field name as generated bylsst.pex.config.config._joinNamePath.- instance :
-
save(outfile, instance)¶ Save this field to a file (for internal use only).
Parameters: Notes
This method is invoked by the
Configobject that contains this field and should not be called directly.The output consists of the documentation string (
lsst.pex.config.Field.doc) formatted as a Python comment. The second line is formatted as an assignment:{fullname}={value}.This output can be executed with Python.
-
toDict(instance)¶ Convert the field value so that it can be set as the value of an item in a
dict(for internal use only).Parameters: Returns: - value : object
The field’s value. See Notes.
Notes
This method invoked by the owning
Configobject and should not be called directly.Simple values are passed through. Complex data structures must be manipulated. For example, a
Fieldholding a subconfig should, instead of the subconfig object, return adictwhere the keys are the field names in the subconfig, and the values are the field values in the subconfig.
-
validate(instance)¶ Validate the field (for internal use only).
Parameters: - instance :
lsst.pex.config.Config The config instance that contains this field.
Raises: - lsst.pex.config.FieldValidationError
Raised if verification fails.
Notes
This method provides basic validation:
- Ensures that the value is not
Noneif the field is not optional. - Ensures type correctness.
- Ensures that the user-provided
checkfunction is valid.
Most
Fieldsubclasses should calllsst.pex.config.field.Field.validateif they re-implementvalidate.- instance :
- doc :