IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 2072


Ignore:
Timestamp:
Oct 12, 2004, 4:38:13 PM (22 years ago)
Author:
eugene
Message:

mods for revision 01

Location:
trunk/doc/modules
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/modules/ChangeLogSDRS.tex

    r2034 r2072  
    1 %%% $Id: ChangeLogSDRS.tex,v 1.3 2004-10-09 00:35:02 price Exp $
     1%%% $Id: ChangeLogSDRS.tex,v 1.4 2004-10-13 02:38:13 eugene Exp $
    22
    33\subsection{Changes from version 00 to version 01}
     
    99\item added \code{pmCameraValidateHeaders}
    1010\item added \code{pmFPAfromHeader}
    11 \end{itemize}
    12 
    13 \subsection{Changes from version 01 to version 02}
    14 
    15 \begin{itemize}
    1611\item Added \code{pmReadoutCombine}
    1712\end{itemize}
  • trunk/doc/modules/ModulesSDRS.tex

    r2034 r2072  
    1 %%% $Id: ModulesSDRS.tex,v 1.17 2004-10-09 00:35:09 price Exp $
     1%%% $Id: ModulesSDRS.tex,v 1.18 2004-10-13 02:38:13 eugene Exp $
    22\documentclass[panstarrs]{panstarrs}
    33
     
    1010\project{Pan-STARRS Image Processing Pipeline}
    1111\organization{Institute for Astronomy}
    12 \version{02}
     12\version{01}
    1313\docnumber{PSDC-430-008}
    1414% note the use of the docnumber & version number:
     
    2929% version  Date            Description
    3030DR & 2004 Jun 7 & Draft \\ \hline
     3100 & 2004 Aug 16 & release for cycle 3 \\ \hline
     3201 & 2004 Oct 12 & draft for cycle 4 \\ \hline
    3133\RevisionsEnd
    3234
     
    460462combination.
    461463
    462 
     464\section{Camera Configutation Information}
     465
     466\tbd{these function are not yet ready for implementation.  The APIs
     467  are fine but the algorithms need to be specified.}
     468
     469We require several utility functions to define the general layout of a
     470camera and to relate the camera definition to the header in a given
     471camera.  This information may be passed to the modules by using the
     472configuration files as parse by \code{psMetadataParseConfig}.  These
     473
     474\begin{verbatim}
     475char *pmCameraFromHeader (psFitsHeader *header);
     476\end{verbatim}
     477This function examines a primary header unit (\code{header}) and
     478determines the camera which provided the data.  \tbr{the rules for
     479  performing this analysis probably depend on the keywords such as
     480  INSTRUME and TELESCOP.  Should this function be a script so we can
     481  easily add a new camera or should the rule set be defined by
     482  configuration information?}.
     483
     484\begin{verbatim}
     485bool  pmCameraValidateHeaders (psHash *headers, psMetadata *camera);
     486\end{verbatim}
     487This funtion examines the collection of \code{headers} and, based on
     488the camera definitions in the metadata \code{camera}, determines if
     489the header set is consistent with the specified camera.
     490
     491\begin{verbatim}
     492psFPA *pmFPAfromHeader (psList *header, psMetadata *camera);
     493\end{verbatim}
     494This funtion uses the collection of \code{headers} and the camera
     495definitions in the metadata \code{camera} to construct a complete
     496\code{psFPA} structure which represents the data described by the
     497collection of \code{headers}.  The resulting \code{FPA} has all
     498possible structure elements defined but no space for pixel data should
     499be allocated. 
    463500
    464501\section{Revision Change Log}
     
    715752
    716753%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    717 
    718 \begin{verbatim}
    719 char *pmCameraFromHeader (psFitsHeader *header);
    720 \end{verbatim}
    721 This function examines a primary header unit (\code{header}) and
    722 determines the camera which provided the data.  \tbr{the rules for
    723   performing this analysis probably depend on the keywords such as
    724   INSTRUME and TELESCOP.  Should this function be a script so we can
    725   easily add a new camera or should the rule set be defined by
    726   configuration information?}.
    727 
    728 \begin{verbatim}
    729 bool  pmCameraValidateHeaders (psHash *headers, psMetadata *camera);
    730 \end{verbatim}
    731 This funtion examines the collection of \code{headers} and, based on
    732 the camera definitions in the metadata \code{camera}, determines if
    733 the header set is consistent with the specified camera.
    734 
    735 \begin{verbatim}
    736 psFPA *pmFPAfromHeader (psList *header, psMetadata *camera);
    737 \end{verbatim}
    738 This funtion uses the collection of \code{headers} and the camera
    739 definitions in the metadata \code{camera} to construct a complete
    740 \code{psFPA} structure which represents the data described by the
    741 collection of \code{headers}.  The resulting \code{FPA} has all
    742 possible structure elements defined but no space for pixel data should
    743 be allocated. 
Note: See TracChangeset for help on using the changeset viewer.