Index: trunk/doc/modules/ModulesSDRS.tex
===================================================================
--- trunk/doc/modules/ModulesSDRS.tex	(revision 2034)
+++ trunk/doc/modules/ModulesSDRS.tex	(revision 2072)
@@ -1,3 +1,3 @@
-%%% $Id: ModulesSDRS.tex,v 1.17 2004-10-09 00:35:09 price Exp $
+%%% $Id: ModulesSDRS.tex,v 1.18 2004-10-13 02:38:13 eugene Exp $
 \documentclass[panstarrs]{panstarrs}
 
@@ -10,5 +10,5 @@
 \project{Pan-STARRS Image Processing Pipeline}
 \organization{Institute for Astronomy}
-\version{02}
+\version{01}
 \docnumber{PSDC-430-008}
 % note the use of the docnumber & version number:
@@ -29,4 +29,6 @@
 % version  Date            Description
 DR & 2004 Jun 7 & Draft \\ \hline
+00 & 2004 Aug 16 & release for cycle 3 \\ \hline
+01 & 2004 Oct 12 & draft for cycle 4 \\ \hline
 \RevisionsEnd
 
@@ -460,5 +462,40 @@
 combination.
 
-
+\section{Camera Configutation Information}
+
+\tbd{these function are not yet ready for implementation.  The APIs
+  are fine but the algorithms need to be specified.}
+
+We require several utility functions to define the general layout of a
+camera and to relate the camera definition to the header in a given
+camera.  This information may be passed to the modules by using the
+configuration files as parse by \code{psMetadataParseConfig}.  These 
+
+\begin{verbatim}
+char *pmCameraFromHeader (psFitsHeader *header);
+\end{verbatim}
+This function examines a primary header unit (\code{header}) and
+determines the camera which provided the data.  \tbr{the rules for
+  performing this analysis probably depend on the keywords such as
+  INSTRUME and TELESCOP.  Should this function be a script so we can
+  easily add a new camera or should the rule set be defined by
+  configuration information?}.
+
+\begin{verbatim}
+bool  pmCameraValidateHeaders (psHash *headers, psMetadata *camera);
+\end{verbatim}
+This funtion examines the collection of \code{headers} and, based on
+the camera definitions in the metadata \code{camera}, determines if
+the header set is consistent with the specified camera.
+
+\begin{verbatim}
+psFPA *pmFPAfromHeader (psList *header, psMetadata *camera);
+\end{verbatim}
+This funtion uses the collection of \code{headers} and the camera
+definitions in the metadata \code{camera} to construct a complete
+\code{psFPA} structure which represents the data described by the
+collection of \code{headers}.  The resulting \code{FPA} has all
+possible structure elements defined but no space for pixel data should
+be allocated.  
 
 \section{Revision Change Log}
@@ -715,29 +752,2 @@
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\begin{verbatim}
-char *pmCameraFromHeader (psFitsHeader *header);
-\end{verbatim}
-This function examines a primary header unit (\code{header}) and
-determines the camera which provided the data.  \tbr{the rules for
-  performing this analysis probably depend on the keywords such as
-  INSTRUME and TELESCOP.  Should this function be a script so we can
-  easily add a new camera or should the rule set be defined by
-  configuration information?}.
-
-\begin{verbatim}
-bool  pmCameraValidateHeaders (psHash *headers, psMetadata *camera);
-\end{verbatim}
-This funtion examines the collection of \code{headers} and, based on
-the camera definitions in the metadata \code{camera}, determines if
-the header set is consistent with the specified camera.
-
-\begin{verbatim}
-psFPA *pmFPAfromHeader (psList *header, psMetadata *camera);
-\end{verbatim}
-This funtion uses the collection of \code{headers} and the camera
-definitions in the metadata \code{camera} to construct a complete
-\code{psFPA} structure which represents the data described by the
-collection of \code{headers}.  The resulting \code{FPA} has all
-possible structure elements defined but no space for pixel data should
-be allocated.