Changeset 2072
- Timestamp:
- Oct 12, 2004, 4:38:13 PM (22 years ago)
- Location:
- trunk/doc/modules
- Files:
-
- 2 edited
-
ChangeLogSDRS.tex (modified) (2 diffs)
-
ModulesSDRS.tex (modified) (5 diffs)
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 $ 2 2 3 3 \subsection{Changes from version 00 to version 01} … … 9 9 \item added \code{pmCameraValidateHeaders} 10 10 \item added \code{pmFPAfromHeader} 11 \end{itemize}12 13 \subsection{Changes from version 01 to version 02}14 15 \begin{itemize}16 11 \item Added \code{pmReadoutCombine} 17 12 \end{itemize} -
trunk/doc/modules/ModulesSDRS.tex
r2034 r2072 1 %%% $Id: ModulesSDRS.tex,v 1.1 7 2004-10-09 00:35:09 price Exp $1 %%% $Id: ModulesSDRS.tex,v 1.18 2004-10-13 02:38:13 eugene Exp $ 2 2 \documentclass[panstarrs]{panstarrs} 3 3 … … 10 10 \project{Pan-STARRS Image Processing Pipeline} 11 11 \organization{Institute for Astronomy} 12 \version{0 2}12 \version{01} 13 13 \docnumber{PSDC-430-008} 14 14 % note the use of the docnumber & version number: … … 29 29 % version Date Description 30 30 DR & 2004 Jun 7 & Draft \\ \hline 31 00 & 2004 Aug 16 & release for cycle 3 \\ \hline 32 01 & 2004 Oct 12 & draft for cycle 4 \\ \hline 31 33 \RevisionsEnd 32 34 … … 460 462 combination. 461 463 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 469 We require several utility functions to define the general layout of a 470 camera and to relate the camera definition to the header in a given 471 camera. This information may be passed to the modules by using the 472 configuration files as parse by \code{psMetadataParseConfig}. These 473 474 \begin{verbatim} 475 char *pmCameraFromHeader (psFitsHeader *header); 476 \end{verbatim} 477 This function examines a primary header unit (\code{header}) and 478 determines 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} 485 bool pmCameraValidateHeaders (psHash *headers, psMetadata *camera); 486 \end{verbatim} 487 This funtion examines the collection of \code{headers} and, based on 488 the camera definitions in the metadata \code{camera}, determines if 489 the header set is consistent with the specified camera. 490 491 \begin{verbatim} 492 psFPA *pmFPAfromHeader (psList *header, psMetadata *camera); 493 \end{verbatim} 494 This funtion uses the collection of \code{headers} and the camera 495 definitions in the metadata \code{camera} to construct a complete 496 \code{psFPA} structure which represents the data described by the 497 collection of \code{headers}. The resulting \code{FPA} has all 498 possible structure elements defined but no space for pixel data should 499 be allocated. 463 500 464 501 \section{Revision Change Log} … … 715 752 716 753 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 717 718 \begin{verbatim}719 char *pmCameraFromHeader (psFitsHeader *header);720 \end{verbatim}721 This function examines a primary header unit (\code{header}) and722 determines the camera which provided the data. \tbr{the rules for723 performing this analysis probably depend on the keywords such as724 INSTRUME and TELESCOP. Should this function be a script so we can725 easily add a new camera or should the rule set be defined by726 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 on732 the camera definitions in the metadata \code{camera}, determines if733 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 camera739 definitions in the metadata \code{camera} to construct a complete740 \code{psFPA} structure which represents the data described by the741 collection of \code{headers}. The resulting \code{FPA} has all742 possible structure elements defined but no space for pixel data should743 be allocated.
Note:
See TracChangeset
for help on using the changeset viewer.
