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/ippconfig/megacam/format_split.config

    r15095 r17911  
    1212        PHU             STR     CHIP    # The FITS file represents an entire FPA
    1313        EXTENSIONS      STR     NONE    # The extensions represent chips
    14         FPA.NAME        STR     EXPNUM  # A PHU keyword for unique identifier
     14        FPA.OBS         STR     EXPNUM  # A PHU keyword for unique identifier
    1515        CONTENT         STR     EXTNAME # Key to the CONTENTS menu
    1616        CONTENT.RULE    STR     {CHIP.NAME} # How to derive the CONTENT when writing
     
    9191# How to translate PS concepts into FITS headers
    9292TRANSLATION     METADATA
    93         FPA.NAME        STR     EXPNUM
     93        FPA.OBS        STR     EXPNUM
    9494        FPA.AIRMASS     STR     AIRMASS
    9595        FPA.FILTER      STR     FILTER
Note: See TracChangeset for help on using the changeset viewer.