AnalyzerConfig#
Note
All Configs are derived from rastervision.pipeline.config.Config
, which itself is a pydantic Model.
- pydantic model AnalyzerConfig[source]#
Configure an
Analyzer
.Show JSON schema
{ "title": "AnalyzerConfig", "description": "Configure an :class:`.Analyzer`.", "type": "object", "properties": { "type_hint": { "title": "Type Hint", "default": "analyzer", "enum": [ "analyzer" ], "type": "string" } }, "additionalProperties": false }
- Config
extra: str = forbid
validate_assignment: bool = True
- Fields
- build(scene_group: Optional[Tuple[str, Iterable[str]]] = None) Analyzer [source]#
Build an instance of the corresponding type of object using this config.
For example, BackendConfig will build a Backend object. The arguments to this method will vary depending on the type of Config.
- get_bundle_filenames() List[str] [source]#
Returns the names of files that should be included in a model bundle.
The files are assumed to be in the analyze/ directory generated by the analyze command. Note that only the names, not the full paths should be returned.
- recursive_validate_config()#
Recursively validate hierarchies of Configs.
This uses reflection to call validate_config on a hierarchy of Configs using a depth-first pre-order traversal.
- revalidate()#
Re-validate an instantiated Config.
Runs all Pydantic validators plus self.validate_config().
Adapted from: https://github.com/samuelcolvin/pydantic/issues/1864#issuecomment-679044432
- update(*args, **kwargs)#
Update any fields before validation.
Subclasses should override this to provide complex default behavior, for example, setting default values as a function of the values of other fields. The arguments to this method will vary depending on the type of Config.
- validate_config()#
Validate fields that should be checked after update is called.
This is to complement the builtin validation that Pydantic performs at the time of object construction.