Re: [alma-sw-ssr] Definition pipelines

[Barry Clark <bclark@aoc.nrao.edu>]

Frederick Gueth wrote:

> 
> In the current draft, the calibration pipeline does not ignore the 
> observations of the astronomical source: it applies (in the sense: 
> store the appropriate quantity in the relevant header) the atmospheric 
> calibration to all incoming observations. 
> 
It is a matter of definition, but I would regard the processing of the
unknown sources as part of the Calibration phase of the Science and/or
Quick Look pipelines.  (This is in aid of setting machine priorities -
this has to be done on the Quick Look timescale, not on the same timescale
as the other items mentioned.)

> > products (depending on the type of observation and type of calibrator), and
> > places the results in a location where they can be accessed both by the
> > real-time system and by other reduction proceedures:  1) an antenna pointing
> > offset for all antennas. 2).  Tsys for all antennas as a function of time.
> > 3.) Sideband ratios for all antennas.  4.)  Antenna based flux calibration
> > (TSYSJY) from a flux calibrator.  5.)  Antenna based bandpass calibration.
> > 6.) Antenna based polarization leakage terms (with the usual indeterminate
> > offsets from a single observation).  7.) Antenna based IF phase differences
> > (from a strongly polarized calibrator).  8.) Antenna based phase calibration
> > (with noise and atmospheric rms).
> 
> The list should be left open in such a general description. For
> instance, 
> the focus offset or the antenna positions derived from a baseline
> measurement 
> are missing.
> 

I don't think these two functions are properly part of a pipeline.  They will
need a little human supervision, because of the very serious consequences
if they are a bit wrong.

But we need to specify that the Package will have tools to do these,
which I do not think we have there.