IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 1145


Ignore:
Timestamp:
Jun 30, 2004, 12:08:52 AM (22 years ago)
Author:
Paul Price
Message:

Added section on reading in an FPA.

File:
1 edited

Legend:

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

    r1119 r1145  
    1 %%% $Id: ModulesSDRS.tex,v 1.8 2004-06-29 02:26:55 price Exp $
     1%%% $Id: ModulesSDRS.tex,v 1.9 2004-06-30 10:08:52 price Exp $
    22\documentclass[panstarrs]{panstarrs}
    33
     
    6868The Phase 2 processing modules are:
    6969\begin{itemize}
     70\item Read in an FPA;
    7071\item Calculate the convolution kernel;
    7172\item Convolve an image with the kernel;
     
    9596%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    9697
     98\section{Read in an image}
     99
     100Of course, before any image manipulation may occur, the image must be
     101read in.  This involves populating the FPA with structures to
     102represent the true focal plane.  However, different instruments have
     103different focal planes, and the images are written to disk in
     104different ways.  We have proposed a configuration file format which
     105appears to be able to document the structure of a focal plane and
     106specify how the IPP can read the required information from the FITS
     107files \tbd{A REFERENCE GOES HERE}.
     108
     109Given an open \code{FILE} pointer to a configuration file,
     110\code{config}, and the name of an FPA image, \code{fpaName},
     111\code{psFPAGenerate} shall return a \code{psFPA} of the correct
     112structure, with all the metadata entries read from the nominated FPA
     113image.  Astrometric information shall be initialised to values
     114specified by the configuration file.  The API shall be:
     115
     116\begin{verbatim}
     117psFPA *psFPAGenerate(FILE *config, const char *fpaName);
     118\end{verbatim}
     119
     120Once an FPA has been generated, the pixels may all be read in at once,
     121or the pixels may be read in a chip, cell or readout at a time.  The
     122corresponding APIs are:
     123
     124\begin{verbatim}
     125psFPA *psFPAReadAll(psFPA *in);
     126psFPA *psFPAReadChip(psFPA *in, const char *chipName);
     127psChip *psChipReadCell(psChip *in, const char *cellName);
     128psCell *psCellReadReadout(psCell *in, const char *readoutName);
     129\end{verbatim}
     130
     131Note that reads of a cell or readout do not act upon an FPA, but
     132rather a chip and a cell, respectively.  This saves the user from
     133specifying the name of the FPA, chip, and cell just to get a readout,
     134since this information is already stored in the generated \code{psFPA}
     135struct.
     136
     137\tbd{How to write the output???}
     138
     139%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
     140
    97141\section{Convolution}
    98142
     
    568612shall be the following:
    569613\begin{verbatim}
    570 /** Returns an image that has the bad pixels masked.  Also masks saturated pixels */
    571614psReadout *psPhase2MaskBadPixels(psReadout *in, const psImage *mask, int maskVal, float sat, int grow);
    572615\end{verbatim}
Note: See TracChangeset for help on using the changeset viewer.