IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jun 4, 2008, 3:32:28 PM (18 years ago)
Author:
Paul Price
Message:

I've implemented the chip-dependent concepts. It uses a generalised version of the dependent DEFAULT concepts, which can, unfortunately, make the camera format configuration a bit longer, but it consolidates code and keeps things simple both for the code and the configuration.

In the process, I took care of a couple of other concept bugs that have been sitting in my inbox for nearly a year:

  • FPA.NAME has been replaced with FPA.OBS, which is intended to be an observation identifier (bug 885). You're welcome to change the name, so long as you also volunteer to fix all the camera formats.
  • FPA.CAMERA is automatically set (on construction of the FPA) to the camera name as used by the configuration files (bug 931). I've changed the ppStats REGISTER recipe to use FPA.CAMERA instead of FPA.INSTRUMENT (which is retained in the concepts as the instrument's name according to the instrument, whereas FPA.CAMERA is the instrument's name according to our configuration).
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/psModules/src/camera/pmFPAConstruct.h

    r16912 r17911  
    44 * @author Paul Price, IfA
    55 *
    6  * @version $Revision: 1.10 $ $Name: not supported by cvs2svn $
    7  * @date $Date: 2008-03-11 01:27:05 $
     6 * @version $Revision: 1.11 $ $Name: not supported by cvs2svn $
     7 * @date $Date: 2008-06-05 01:31:33 $
    88 * Copyright 2005-2006 Institute for Astronomy, University of Hawaii
    99 */
     
    2121/// as the corresponding values (whitespace separated).  The FPA hierarchy is created devoid of any
    2222/// input/output sources (i.e., HDUs).
    23 pmFPA *pmFPAConstruct(const psMetadata *camera ///< The camera configuration
     23pmFPA *pmFPAConstruct(const psMetadata *camera, ///< The camera configuration
     24                      const char *cameraName ///< Name of the camera (for FPA.CAMERA concept)
    2425                     );
    2526
     
    2829/// This is suitable for generating an output FPA given the desired format.
    2930bool pmFPAAddSourceFromFormat(pmFPA *fpa, ///< The FPA
    30                               const char *fpaname, ///< FPA.NAME for the source
     31                              const char *fpaObs, ///< FPA.NAME for the source
    3132                              const psMetadata *format ///< Format of file
    3233    );
     
    3738/// configuration is required in order to describe how the FPA is laid out in terms of disk files.
    3839bool pmFPAAddSourceFromView(pmFPA *fpa,   ///< The FPA
    39                             const char *fpaname, ///< FPA.NAME for the source
     40                            const char *fpaObs, ///< FPA.NAME for the source
    4041                            const pmFPAview *phuView, ///< The view, corresponding to the PHU
    4142                            const psMetadata *format ///< Format of file
Note: See TracChangeset for help on using the changeset viewer.