Re: [alma-sw-ssr] Pipeline Requirements new version

[Robert Lucas <lucas@iram.fr>]

Peter, Frederic

I attach comments to pipeline v3.2; these are mainly minor (phrasing).

Regards

Robert
-- 
Robert LUCAS,            Institut de Radioastronomie Millimetrique
300 rue de la Piscine,  F-38406 St Martin d'Heres Cedex   (FRANCE)
Tel +33 (0)4 76 82 49 42                  Fax +33 (0)4 76 51 59 38 
E-mail: mailto:lucas@iram.fr                http://iram.fr/~lucas/
$Header: /home/lucas/ALMA/Software/SSR/Requirements/pipeline_3.2Comments.txt,v 1.3 2001/08/29 14:00:32 lucas Exp lucas $

p1. title: Mention DRAFT somewhere in title?

p4. s1.1

- 'four different groups'
- 'Each group should has lot of operations' -> plural in all following
- Each of these groups has different functions...

p4. real-time ... 4th level itemize: add side band ratio determination.
 astromical calibration: add somewhere: 
  - preliminary phase and amplitude calibration calibration (for quick look)
  

p4. quick Look Operations 
  o quick calibration 
    - produces uv tables: this an implementation issue. say `apply
      preliminary phase and amplitude calibration'

p5. 
 science imaging operations
  say: `final after completion of part of project'

p5.
 o "produces and archives uv tables of calibrated visibilities": this
 is in contradiction with archive section where we archive calibration
 data, not calibrated data.

p5. s1.2 astronomical source : arbitrary

p5. s1.3 3rd - 
  will polarisation leakage calibration require a time interpolation? 

p5. s1.3 last paragraph
  The third category will be handled partly as real-time calibration
  operations (...)  as Quick Look operations (...) and as final
  Science Operations.

p6. 2-0.0-R3 "All data processing shall operate ..." or "The pipeline ..."

p6. 2-0.0-R6 "any step" is difficult. At least add "an entire series
  of _previous_ operations" (I doupt we can avoid redoing the
  operations subsequent to the incriminated step). In fact it is a
  question of implementation of the software whether it is optimum to
  `compute backwards' steps, or go back to previous states.

p7. Real Time Calibration Operations

p7. 3-0.0-R1 Real Time calibration operations shall ...

p7. 3-0.0-R2 Whenever the results of the real time calibration allows ...

p7. 3-2.0-R1 The pipeline shall reduce, ...

p7. 3-2.0-R1.1 The receiver sideband ratios.

p7. 3-2.0-R1.2 The temperature scale calibration data, ... 

p7. 3-2.0-R1.3 The bandpass calibration data.

p7. 3-2.0-R2 For all observations... the pipeline shall:

p7. 3-2.0-R2.1 This is not the only solution, one may also defer the
  actual conversion to later stages, and keep only the conversion
  factor (Tsys) as a function of frequency.

p7. 3-2.0-R2.2 Sorry I had missed this. The first is not a pipeline
  operation; it is part of the data acquisition (in anyway it is not
  the phase but the complex data). 


p8. 3-2.0-R3 last paragraph: 
  "they must also made available to later science calibration operations...

p8 3-3.0-R1 'The pipeline shall ...'

p8 3-3.0-R2 ditto
            and note contradiction with 3-2.0-R2.1 which does the same thing.
            ->same comment

p8. 3.4.0-R1 The Pipeline...
    delay measurements

p8. 3.4.0-R1 telescope parameter file: this is an implementation issue (may be
    in a data base). I would say `archived and made available ...'

p8. 3.4.0-R2/3/4 The Pipeline...

p9. 3-4.0-R5 The Pipeline...

p9. 3-4.0-R5 Add the same req. for point sources of known flux or
    small sources of known visibility model  and aperture efficiency?

p9. 3-4.0-R6 Skydip already mentioned in R5 (I think it should be only
    here).  
    - I'm not sure single dish (transmitter) holography can be
    handled by the pipeline as it will probably not be done on the
    site (?)

p10. s4: Quick Look Operations

p10. 4-0.0-R3 `various real time calibration results'

p10. 4-0.0-R3 last paragraph: replace `observer' by `staff astronomer'

p10. 4-0.0-R5.5 say '(from theory, using actual system temperatures)'

p11. 4-0.0-R6.3 AoD -> Staff astronomer (for consistency). 

p11. 4-0.0-R6.5 or at actually observed positions 
     (... not necessarily rectangular)
     
p11. 4-0.0-R8.5 phase and amplitude closure (useful to detect decorrelation).
                both really useful for calibrators only.

p11. 4-0.0-R9 resulting map shall be displayed


p11. 4-0.0-R9.2 AoD -> Staff astronomer (for consistency). 


p12. 5-0.0-R2 The pipeline shall find ...

p12. 5-1.0-R1/2/3 The pipeline shall find ...
 
p12. 5-2.0-R2 AoD -> Staff astronomer (for consistency). 

p13. s6 Science Imaging Operations

p13 6-1.0-R1/2/4/5 The Pipeline shall ....  

p13 6-1.0-R2 ... find in the Archive the visibilities and calibration
    data obtained ...

p13 6-1.0-R4 ... , plus the continuum measurements, if required.

p13 6-1.0-R5 ..., as well as continuum emission, if required.

p14 6-1.0-R5 subtraction of continuum ... may be required.

p14 6-1.0-R8.4 combination of single-dish and interferometer data.

p14. 6-2.0-R1 For single dish data, the pipeline shall:

p14. 6-2.0-R1.1 it shall use calibration data produced by science
     calibration operations.

p14. 6-2.0-R1.2 find in teh Archive previous observations and
   calibration data, ...