pipeline.hsd.tasks.applycal package¶
Submodules¶
pipeline.hsd.tasks.applycal.applycal module¶
-
class
pipeline.hsd.tasks.applycal.applycal.
HpcSDApplycal
(inputs)[source]¶ Bases:
pipeline.infrastructure.sessionutils.ParallelTemplate
-
Inputs
¶ alias of
HpcSDApplycalInputs
-
Task
¶ alias of
SDApplycal
-
get_result_for_exception
(*args, **kw)¶
-
-
class
pipeline.hsd.tasks.applycal.applycal.
HpcSDApplycalInputs
(context, output_dir=None, vis=None, field=None, spw=None, antenna=None, intent=None, parang=None, applymode=None, flagbackup=None, flagsum=None, flagdetailedsum=None, parallel=None)[source]¶ Bases:
pipeline.hsd.tasks.applycal.applycal.SDApplycalInputs
-
property
parallel
¶
-
property
-
class
pipeline.hsd.tasks.applycal.applycal.
SDApplycal
(inputs)[source]¶ Bases:
pipeline.h.tasks.applycal.applycal.Applycal
Applycal executes CASA applycal tasks for the current context state, applying calibrations registered with the pipeline context to the target measurement set.
Applying the results from this task to the context marks the referred tables as applied. As a result, they will not be included in future on-the-fly calibration arguments.
-
Inputs
¶ alias of
SDApplycalInputs
-
-
class
pipeline.hsd.tasks.applycal.applycal.
SDApplycalInputs
(context, output_dir=None, vis=None, field=None, spw=None, antenna=None, intent=None, parang=None, applymode=None, flagbackup=None, flagsum=None, flagdetailedsum=None)[source]¶ Bases:
pipeline.h.tasks.applycal.applycal.ApplycalInputs
ApplycalInputs defines the inputs for the Applycal pipeline task.
-
flagdetailedsum
¶ VisDependentProperty is a Python data descriptor that standardises the behaviour of pipeline Inputs properties and lets them create default values more easily.
On reading a VisDependentProperty (ie. using the dot prefix: inputs.solint), one of two things happens:
If a NullMarker is found - signifying that no user input has been provided - and a ‘getter’ function has been defined, the getter function will be called to provide a default value for that measurement set.
If a user has overridden the value (eg. inputs.solint = 123), that value will be retrieved.
The value, either the default from step 1 or user-provided from step 2, is run through the optional postprocess function, which gives a final opportunity to change the value depending on the state/value of other properties.
A VisDependentProperty can be made read-only by specifying ‘readonly=True’ when creating the instance.
A VisDependentProperty can be hidden from the containing Inputs string representation by setting ‘hidden=True’ when creating the instance. This will hide the property from the web log and CLI getInputs calls.
Each VisDependentProperty has a set of values it considers equivalent to null. When the user sets the VDP value to one of these null values, the VDP machinery converts this to a private NullObject marker that signifies the property is now unset, resulting in the default value being returned next time the property is read. Developers can specify which values should be converted to NullObject by specifying null_input at creation time, e.g.,
solint = @VisDependentProperty(default=5, null_input=[None, ‘’, ‘RESET’, -1])
-
intent
¶ VisDependentProperty is a Python data descriptor that standardises the behaviour of pipeline Inputs properties and lets them create default values more easily.
On reading a VisDependentProperty (ie. using the dot prefix: inputs.solint), one of two things happens:
If a NullMarker is found - signifying that no user input has been provided - and a ‘getter’ function has been defined, the getter function will be called to provide a default value for that measurement set.
If a user has overridden the value (eg. inputs.solint = 123), that value will be retrieved.
The value, either the default from step 1 or user-provided from step 2, is run through the optional postprocess function, which gives a final opportunity to change the value depending on the state/value of other properties.
A VisDependentProperty can be made read-only by specifying ‘readonly=True’ when creating the instance.
A VisDependentProperty can be hidden from the containing Inputs string representation by setting ‘hidden=True’ when creating the instance. This will hide the property from the web log and CLI getInputs calls.
Each VisDependentProperty has a set of values it considers equivalent to null. When the user sets the VDP value to one of these null values, the VDP machinery converts this to a private NullObject marker that signifies the property is now unset, resulting in the default value being returned next time the property is read. Developers can specify which values should be converted to NullObject by specifying null_input at creation time, e.g.,
solint = @VisDependentProperty(default=5, null_input=[None, ‘’, ‘RESET’, -1])
-
pipeline.hsd.tasks.applycal.renderer module¶
Created on 24 Oct 2014
@author: sjw
-
pipeline.hsd.tasks.applycal.renderer.
FlagTotal
¶ alias of
pipeline.hsd.tasks.applycal.renderer.FlagSummary
-
class
pipeline.hsd.tasks.applycal.renderer.
T2_4MDetailsSDApplycalRenderer
(uri='applycal.mako', description='Apply calibrations from context', always_rerender=False)[source]¶ Bases:
pipeline.h.tasks.applycal.renderer.T2_4MDetailsApplycalRenderer