Changeset 4563 for trunk/doc/modules/CameraImages.tex

Timestamp:

Jul 15, 2005, 11:42:13 AM (21 years ago)

Author:

Paul Price

Message:

Fixes following Gene's comments

File:

• trunk/doc/modules/CameraImages.tex (modified) (7 diffs)

trunk/doc/modules/CameraImages.tex

@@ -157 +157 @@
 faster.  The cell also contains metadata containers for the concepts
 and analysis, a link to the parent, and pointers to the various FITS
-data, if that corresponds to this level.
+data, if that corresponds to this level.  A boolean indicates whether
+the cell is of interest, allowing it to be excluded from analysis.
 
 \begin{verbatim}
@@ -173 +174 @@
     psArray *readouts;                 // The readouts (referred to by number)
     pmChip *parent;                    // Parent chip
+    bool valid;                        // Do we bother about reading and working with this cell?
     // FITS data
     const char *extname;               // Extension name, if it corresponds to this level
@@ -196 +198 @@
 amplifiers on the device).  The chip contains metadata containers for
 the concepts and analysis, a link to the parent, and pointers to the
-various FITS data, if that corresponds to this level.  For astrometry,
-in addition to the rough positioning information, it contains a
-coordinate transform from the chip to the focal plane.  It is expected
-that this transform will consist of two second-order 2D polynomials;
-hence we think that it is prudent to include a reverse transformation
-which will be derived from numerically inverting the forward
-transformation.
+pointers to the various FITS data, if that corresponds to this level.
+For astrometry, in addition to the rough positioning information, it
+contains a coordinate transform from the chip to the focal plane.  It
+is expected that this transform will consist of two second-order 2D
+polynomials; hence we think that it is prudent to include a reverse
+transformation which will be derived from numerically inverting the
+forward transformation.  A boolean indicates whether the chip is of
+interest, allowing it to be excluded from analysis.
 
 \begin{verbatim}
@@ -217 +220 @@
     psArray *cells;                    // The cells (referred to by name)
     pmFPA *parent;                     // Parent FPA
+    bool valid;                        // Do we bother about reading and working with this chip?
     // FITS data
     const char *extname;               // Extension name, if it corresponds to this level
@@ -240 +244 @@
 of pieces of contiguous silicon).  It contains metadata containers for
 the concepts and analysis, a link to the parent, and pointers to the
-various FITS data, if that corresponds to this level.  For astrometry,
-it contains a transformation from the focal plane to the tangent plane
-and the fixed pattern residuals.  It is expected that the
-transformation will consist of two 4D polynomials (i.e.\ a function of
-two coordinates in position, the magnitude of the object, and the
-color of the object) in order to correct for optical distortions and
-the effects of the atmosphere; hence we think that it is prudent to
-include a reverse transformation which will be derived from
-numerically inverting the forward transformation.
+FITS header, if that corresponds to this level (the FPA may be the
+PHU, but will not ever contain pixels).  For astrometry, it contains a
+transformation from the focal plane to the tangent plane and the fixed
+pattern residuals.  It is expected that the transformation will
+consist of two 4D polynomials (i.e.\ a function of two coordinates in
+position, the magnitude of the object, and the color of the object) in
+order to correct for optical distortions and the effects of the
+atmosphere; hence we think that it is prudent to include a reverse
+transformation which will be derived from numerically inverting the
+forward transformation.
 
 \begin{verbatim}
@@ -263 +268 @@
     psArray *chips;                    // The chips
     // FITS data
-    const char *extname;               // Extension name, if it corresponds to this level
-    psArray *pixels;                   // The pixel data, if it corresponds to this level
     psMetadata *header;                // The FITS header, if it corresponds to this level
 } pmFPA;
 \end{verbatim}
+
+\tbd{Carrying the DB handle around in the pmFPA may not be what we
+really want to do in the end (we might want to stuff it into a
+separate structure with other sources of information), but for now this
+serves as an approximation and a useful convenience.}
 
 The constructor for \code{pmFPA} shall be:
@@ -367 +375 @@
 extant \code{fpa}.
 
-\tbd{Functions to remove things from an fpa so that only certain
-pieces of the FITS file are read in, and not the whole thing?}
+\tbd{Functions to set the valid booleans within an fpa so that only
+certain pieces of the FITS file are read in, and not the whole thing?}
 
 We specify an additional two functions to write out a focal plane