PatchMatchedMeasurementTask¶
-
class
lsst.faro.measurement.PatchMatchedMeasurementTask(config, *args, **kwargs)¶ Bases:
lsst.faro.base.CatalogMeasurementBaseTaskAttributes Summary
canMultiprocessMethods Summary
emptyMetadata()Empty (clear) the metadata for this Task and all sub-Tasks. getFullMetadata()Get metadata for all tasks. getFullName()Get the task name as a hierarchical name including parent task names. getName()Get the name of the task. getResourceConfig()Return resource configuration for this task. getTaskDict()Get a dictionary of all tasks as a shallow copy. makeField(doc)Make a lsst.pex.config.ConfigurableFieldfor this task.makeSubtask(name, **keyArgs)Create a subtask as a new instance as the nameattribute of this task.run(**kwargs)Run the MetricTask on in-memory data. runQuantum(butlerQC, inputRefs, outputRefs)Do Butler I/O to provide in-memory objects for run. timer(name, logLevel)Context manager to log performance data for an arbitrary block of code. Attributes Documentation
-
canMultiprocess= True¶
Methods Documentation
-
emptyMetadata() → None¶ Empty (clear) the metadata for this Task and all sub-Tasks.
-
getFullMetadata() → lsst.pipe.base._task_metadata.TaskMetadata¶ Get metadata for all tasks.
Returns: - metadata :
TaskMetadata The keys are the full task name. Values are metadata for the top-level task and all subtasks, sub-subtasks, etc.
Notes
The returned metadata includes timing information (if
@timer.timeMethodis used) and any metadata set by the task. The name of each item consists of the full task name with.replaced by:, followed by.and the name of the item, e.g.:topLevelTaskName:subtaskName:subsubtaskName.itemName
using
:in the full task name disambiguates the rare situation that a task has a subtask and a metadata item with the same name.- metadata :
-
getFullName() → str¶ Get the task name as a hierarchical name including parent task names.
Returns: - fullName :
str The full name consists of the name of the parent task and each subtask separated by periods. For example:
- The full name of top-level task “top” is simply “top”.
- The full name of subtask “sub” of top-level task “top” is “top.sub”.
- The full name of subtask “sub2” of subtask “sub” of top-level task “top” is “top.sub.sub2”.
- fullName :
-
getResourceConfig() → Optional[ResourceConfig]¶ Return resource configuration for this task.
Returns: - Object of type
ResourceConfigorNoneif resource - configuration is not defined for this task.
- Object of type
-
getTaskDict() → Dict[str, weakref.ReferenceType[lsst.pipe.base.task.Task]]¶ Get a dictionary of all tasks as a shallow copy.
Returns: - taskDict :
dict Dictionary containing full task name: task object for the top-level task and all subtasks, sub-subtasks, etc.
- taskDict :
-
classmethod
makeField(doc: str) → lsst.pex.config.configurableField.ConfigurableField¶ Make a
lsst.pex.config.ConfigurableFieldfor this task.Parameters: - doc :
str Help text for the field.
Returns: - configurableField :
lsst.pex.config.ConfigurableField A
ConfigurableFieldfor this task.
Examples
Provides a convenient way to specify this task is a subtask of another task.
Here is an example of use:
class OtherTaskConfig(lsst.pex.config.Config): aSubtask = ATaskClass.makeField("brief description of task")
- doc :
-
makeSubtask(name: str, **keyArgs) → None¶ Create a subtask as a new instance as the
nameattribute of this task.Parameters: - name :
str Brief name of the subtask.
- keyArgs
Extra keyword arguments used to construct the task. The following arguments are automatically provided and cannot be overridden:
- “config”.
- “parentTask”.
Notes
The subtask must be defined by
Task.config.name, an instance ofConfigurableFieldorRegistryField.- name :
-
run(**kwargs)¶ Run the MetricTask on in-memory data.
Parameters: - **kwargs
Keyword arguments matching the inputs given in the class config; see
lsst.pipe.base.PipelineTask.runfor more details.
Returns: - struct :
lsst.pipe.base.Struct A
Structcontaining at least the following component:measurement: the value of the metric (lsst.verify.MeasurementorNone). This method is not responsible for adding mandatory metadata (e.g., the data ID); this is handled by the caller.Nonemay be used to indicate that a metric is undefined or irrelevant instead of raisingNoWorkFound.
Raises: - lsst.verify.tasks.MetricComputationError
Raised if an algorithmic or system error prevents calculation of the metric. Examples include corrupted input data or unavoidable exceptions raised by analysis code. The
MetricComputationErrorshould be chained to a more specific exception describing the root cause.Not having enough data for a metric to be applicable is not an error, and should raise
NoWorkFound(see below) instead of this exception.- lsst.pipe.base.NoWorkFound
Raised if the metric is ill-defined or otherwise inapplicable to the data. Typically this means that the pipeline step or option being measured was not run.
-
runQuantum(butlerQC, inputRefs, outputRefs)¶ Do Butler I/O to provide in-memory objects for run.
This specialization of runQuantum performs error-handling specific to MetricTasks.
-
timer(name: str, logLevel: int = 10) → Iterator[None]¶ Context manager to log performance data for an arbitrary block of code.
Parameters: See also
timer.logInfo
Examples
Creating a timer context:
with self.timer("someCodeToTime"): pass # code to time
-