Index: trunk/doc/modules/ModulesSDRS.tex
===================================================================
--- trunk/doc/modules/ModulesSDRS.tex	(revision 1805)
+++ trunk/doc/modules/ModulesSDRS.tex	(revision 1997)
@@ -1,3 +1,3 @@
-%%% $Id: ModulesSDRS.tex,v 1.15 2004-09-14 19:42:32 eugene Exp $
+%%% $Id: ModulesSDRS.tex,v 1.16 2004-10-07 18:15:06 eugene Exp $
 \documentclass[panstarrs]{panstarrs}
 
@@ -362,8 +362,4 @@
 \end{document}
 
-
-
-
-
 \subsection{Subtract sky}
 
@@ -611,2 +607,29 @@
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+
+\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.