[alma-sw-ssr] Pipeline and offline comments

["Brian Glendenning" <bglenden@nrao.edu>]

Not many - probably that means that I've read earlier drafts of the
documents too recently and am hence "blind" to them.

Cheers,
Brian

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Pipeline
=====

p.0 The Canadian proposal should be read with an eye to missing requirements
(which we might or might not agree with, but should be discussed)

p.6 2-0.0-R2 I would only require the reduction script for the science
operation. I can imagine the calibration pipeline might work in some direct
programmatic fashion (i.e., call subroutines!) and only record the results.

p.6 s-0.0-R3 should we say that the flagging must be reversible in a
post-processing system here?

p.7 s3 Shouldn't the third "dashed" point be handled by the science
calibration operation (rather than RT)

p.7 3-0.0-R1 Should "scan" be observation here?

p.11 s5 It should be mentioned (probably as a general requirement) that the
output goes in the archive. Similarly for s6.

Off-line
=====

(Sections 2.4.3 - 2.4.5, 2.5 - 2.7 only)

p.20 OL-4.5-R1 I don't understand this? I thought WVR (etc) was already
applied (or not) to the data, and hence would be impossible not to use
(other than by throwing a top-level switch: use/don't use) the corrected
data.

p.21 OL-5.1-R4.1 List the weightings? (Natural, Uniform, Briggs I assume).

p.23 OL-5.3-R2.2 A standard set of ALMA primary beams must be distributed
with the package.

p.24 OL-6.1-Rxx A line catalog should be distributed with the package and
used "appropriately"? Maybe this is covered by OL-6.2-R8.3 (although the
usefulness isn't just tied to data cubes)

p.24 OL-6.2-R1 Cube rotations need not be orthogonal to cube faces.

p.25 OL-6.2 R3.3 seems more like a priority 3 to me. Maybe because I don't
understand what it means.

p.25 OL-6.2-R4 It should be possible to calculate moments along any axis.

p.25 OL-6.2-R7.1 (I'd say 1D & 2D are priority 1, ND is priority 2).

p.26 OL-6.2-R7.13 I don't understand this.

p.26 OL-6.2-R8.3 I would have thought this to be at least priority 2 (at
least for the listed examples).

p.27 OL-7.2-R1 "immediate" isn't reasonable if there is a lot of data. More
objective to say so many pixels or points per second. Similarly for R2
(unzooming might require going back to the data).

p.30 OL-7.5-R8 by "arbitrary" I assume you mean not aligned with a cube face
(which should be priority 1).