Index: trunk/doc/modules/ModulesSDRS.tex
===================================================================
--- trunk/doc/modules/ModulesSDRS.tex	(revision 5022)
+++ trunk/doc/modules/ModulesSDRS.tex	(revision 5023)
@@ -1,3 +1,3 @@
-%%% $Id: ModulesSDRS.tex,v 1.56 2005-09-13 03:26:45 price Exp $
+%%% $Id: ModulesSDRS.tex,v 1.57 2005-09-13 03:36:09 price Exp $
 \documentclass[panstarrs]{panstarrs}
 
@@ -200,5 +200,5 @@
 it must not only specify how to translate the pixels from a FITS file
 into a focal plane hierarchy (\S\ref{sec:focalplane}), but it must
-also specify how to derive the values of the PS concepts
+also specify how to derive the various values the IPP needs
 (\S\ref{sec:concepts}).  Moreover, it must be able to do these for the
 great variety of cameras in use in the astronomical community.
@@ -290,7 +290,5 @@
 CELLS   METADATA
         left    METADATA        # Left amplifier
-                CELL.BIASSEC.SOURCE     STR     HEADER
                 CELL.BIASSEC            STR     BIASSEC
-                CELL.TRIMSEC.SOURCE     STR     HEADER
                 CELL.TRIMSEC            STR     DATASEC
                 CELL.PARITY             S32     1
@@ -298,7 +296,5 @@
         right   METADATA        # Right amplifier
                 # This cell is read out in the opposite direction
-                CELL.BIASSEC.SOURCE     STR     HEADER
                 CELL.BIASSEC            STR     BIASSEC
-                CELL.TRIMSEC.SOURCE     STR     VALUE
                 CELL.TRIMSEC            STR     [1025:2048,1:2048]
                 CELL.PARITY             S32     -1
@@ -310,8 +306,4 @@
 know from the \code{EXTENSIONS} is a cell, and that each extension is
 associated with a chip, and has a cell type.
-
-The \code{.SOURCE} keywords in the \code{CELLS}, explained in more
-detail in \S\ref{sec:concepts}, are necessary in order to distinguish
-a pointer to a header from an actual value.
 
 \paragraph{Deriving concept values}
@@ -480,10 +472,11 @@
 all readouts are of the same exposure and dark time.}
 
-These concepts are not always known by the same name, nor are they
-generally obtained in the same manner, in different camera systems,
-and so their source or value must be specified in the camera
-configuration file.  The value of a concept shall be found by
-searching in the following order:
+For different camera systems, these concepts are not always known by
+the same name, nor are they generally obtained in the same manner, and
+so their source or value must be specified in the camera configuration
+file.  The value of a concept shall be found by searching in the
+following order:
 \begin{itemize}
+\item The cell data from the \code{CELLS} metadata in the camera configuration.
 \item The FITS header via the \code{TRANSLATION} table.
 \item The \code{DATABASE} lookup.
@@ -491,7 +484,8 @@
 \end{itemize}
 
-After ingest, the user may safely assume that all of the above
-concepts exist (defined at the appropriate level), is of the specified
-type and in the specified format.
+After ingest (performed by \code{pmFPARead}, the user may safely
+assume that all of the above concepts exist (defined at the
+appropriate level), is of the specified type and in the specified
+format.
 
 \subsubsection{Dependencies for defaults}