ReassignCwfsCutoutsTask¶
- class lsst.ts.wep.task.ReassignCwfsCutoutsTask(**kwargs)¶
Bases:
PipelineTask
Cut out the donut postage stamps on corner wavefront sensors (CWFS)
Attributes Summary
Methods Summary
Empty (clear) the metadata for this Task and all sub-Tasks.
Get metadata for all tasks.
Get the task name as a hierarchical name including parent task names.
getName
()Get the name of the task.
Get a dictionary of all tasks as a shallow copy.
makeField
(doc)Make a
lsst.pex.config.ConfigurableField
for this task.makeSubtask
(name, **keyArgs)Create a subtask as a new instance as the
name
attribute of this task.run
(**kwargs)Run task algorithm on in-memory data.
runQuantum
(butlerQC, inputRefs, outputRefs)We need to be able to take pairs of detectors from the full set of detector exposures and run the task.
timer
(name[, logLevel])Context manager to log performance data for an arbitrary block of code.
Attributes Documentation
- canMultiprocess: ClassVar[bool] = True¶
Methods Documentation
- emptyMetadata() None ¶
Empty (clear) the metadata for this Task and all sub-Tasks.
- getFullMetadata() 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.timeMethod
is 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
- getName() str ¶
Get the name of the task.
Returns¶
- taskName
str
Name of the task.
See Also¶
getFullName : Get the full name of the task.
- taskName
- 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) ConfigurableField ¶
Make a
lsst.pex.config.ConfigurableField
for this task.Parameters¶
- doc
str
Help text for the field.
Returns¶
- configurableField
lsst.pex.config.ConfigurableField
A
ConfigurableField
for 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: Any) None ¶
Create a subtask as a new instance as the
name
attribute 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 ofConfigurableField
orRegistryField
.- name
- run(**kwargs: Any) Struct ¶
Run task algorithm on in-memory data.
This method should be implemented in a subclass. This method will receive keyword arguments whose names will be the same as names of connection fields describing input dataset types. Argument values will be data objects retrieved from data butler. If a dataset type is configured with
multiple
field set toTrue
then the argument value will be a list of objects, otherwise it will be a single object.If the task needs to know its input or output DataIds then it has to override
runQuantum
method instead.This method should return a
Struct
whose attributes share the same name as the connection fields describing output dataset types.Parameters¶
- **kwargs
Any
Arbitrary parameters accepted by subclasses.
Returns¶
- struct
Struct
Struct with attribute names corresponding to output connection fields.
Examples¶
Typical implementation of this method may look like:
def run(self, input, calib): # "input", "calib", and "output" are the names of the config # fields # Assuming that input/calib datasets are `scalar` they are # simple objects, do something with inputs and calibs, produce # output image. image = self.makeImage(input, calib) # If output dataset is `scalar` then return object, not list return Struct(output=image)
- **kwargs
- runQuantum(butlerQC: QuantumContext, inputRefs: InputQuantizedConnection, outputRefs: OutputQuantizedConnection)¶
We need to be able to take pairs of detectors from the full set of detector exposures and run the task. Then we need to put the outputs back into the butler repository with the appropriate butler dataIds.
For the
outputZernikesRaw
andoutputZernikesAvg
we only have one set of values per pair of wavefront detectors so we put this in the dataId associated with the extra-focal detector.
- timer(name: str, logLevel: int = 10) Iterator[None] ¶
Context manager to log performance data for an arbitrary block of code.
Parameters¶
- name
str
Name of code being timed; data will be logged using item name:
Start
andEnd
.- logLevel
int
A
logging
level constant.
Examples¶
Creating a timer context:
with self.timer("someCodeToTime"): pass # code to time
See Also¶
lsst.utils.timer.logInfo : Implementation function.
- name