pipeline.hifa.tasks.importdata package¶
Submodules¶
pipeline.hifa.tasks.importdata.almaimportdata module¶
-
class
pipeline.hifa.tasks.importdata.almaimportdata.
ALMAImportData
(inputs)[source]¶ Bases:
pipeline.h.tasks.importdata.importdata.ImportData
-
Inputs
¶ alias of
ALMAImportDataInputs
-
Results
¶ alias of
ALMAImportDataResults
-
-
class
pipeline.hifa.tasks.importdata.almaimportdata.
ALMAImportDataInputs
(context, vis=None, output_dir=None, asis=None, process_caldevice=None, session=None, overwrite=None, nocopy=None, bdfflags=None, lazy=None, save_flagonline=None, dbservice=None, createmms=None, ocorr_mode=None, asimaging=None, minparang=None)[source]¶ Bases:
pipeline.h.tasks.importdata.importdata.ImportDataInputs
-
asis
¶ 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])
-
createmms
¶ 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])
-
dbservice
¶ 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])
-
minparang
¶ 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])
-
-
class
pipeline.hifa.tasks.importdata.almaimportdata.
ALMAImportDataResults
(mses=None, setjy_results=None)[source]¶ Bases:
pipeline.h.tasks.importdata.importdata.ImportDataResults
pipeline.hifa.tasks.importdata.dbfluxes module¶
-
pipeline.hifa.tasks.importdata.dbfluxes.
buildparams
(name, date, frequency)[source]¶ Inputs are all strings with the format: NAME=3c279&DATE=04-Apr-2014&FREQUENCY=231.435E9&WEIGHTED=true&RESULT=1
-
pipeline.hifa.tasks.importdata.dbfluxes.
buildurl
(service_url, obs_time, frequency, sourcename)[source]¶
-
pipeline.hifa.tasks.importdata.dbfluxes.
flux_nosourcexml
(ms)[source]¶ Call the flux service and get the frequencies from the ms if no Source.xml is available
-
pipeline.hifa.tasks.importdata.dbfluxes.
fluxservice
(service_url, obs_time, frequency, sourcename)[source]¶ - Usage of this online service requires:
service_url - url for the db service
obs_time - for getting the date
frequency_text - we will get the frequency out of this in Hz
source - we will get source.name from this object
-
pipeline.hifa.tasks.importdata.dbfluxes.
get_setjy_results
(mses)[source]¶ Get flux values from the database service reverting to the Source tables XML for backup values and store the values in the context
-
pipeline.hifa.tasks.importdata.dbfluxes.
log_result
(source, spw, asdm_I, catalogue_I, spix, age, url, version, status_code, data_conditions)[source]¶
pipeline.hifa.tasks.importdata.qa module¶
-
class
pipeline.hifa.tasks.importdata.qa.
ALMAImportDataListQAHandler
[source]¶ Bases:
pipeline.infrastructure.pipelineqa.QAPlugin
-
child_cls
¶ alias of
pipeline.hifa.tasks.importdata.almaimportdata.ALMAImportDataResults
-
result_cls
¶ alias of
collections.abc.Iterable
-
-
class
pipeline.hifa.tasks.importdata.qa.
ALMAImportDataQAHandler
[source]¶ Bases:
pipeline.infrastructure.pipelineqa.QAPlugin
-
child_cls
= None¶
-
result_cls
¶ alias of
pipeline.hifa.tasks.importdata.almaimportdata.ALMAImportDataResults
-
-
pipeline.hifa.tasks.importdata.qa.
ous_parallactic_range
(mses: List[pipeline.domain.measurementset.MeasurementSet], field_name: str, intent: str)[source]¶ Get the parallactic angle range across all measurement sets for field f when observed with the specifiedintent.
- Parameters
mses – MeasurementSets to process
f – Field to inspect
intent – observing intent to consider
- Returns
angular range expressed as (min angle, max angle) tuple
-
pipeline.hifa.tasks.importdata.qa.
parallactic_angle_at_epoch
(f: pipeline.domain.field.Field, e: dict) → float[source]¶ Get the instantaneous parallactic angle for field f at epoch e.
- Parameters
f – Field domain object
e – CASA epoch
- Returns
angular separation in degrees
-
pipeline.hifa.tasks.importdata.qa.
parallactic_range_for_field
(ms: pipeline.domain.measurementset.MeasurementSet, f: pipeline.domain.field.Field, intent: str) → Tuple[float, float][source]¶ Get the parallactic angle range for field f when observed with the specified intent.
- Parameters
ms – MeasurementSet to process
f – Field to inspect
intent – observing intent to consider
- Returns
angular range expressed as (min angle, max angle) tuple
pipeline.hifa.tasks.importdata.renderer module¶
Created on 5 Sep 2014
@author: sjw
-
class
pipeline.hifa.tasks.importdata.renderer.
T2_4MDetailsALMAImportDataRenderer
(uri='almaimportdata.mako', description='Register measurement sets with the pipeline', always_rerender=False)[source]¶ Bases:
pipeline.h.tasks.importdata.renderer.T2_4MDetailsImportDataRenderer