Changeset 17911 for trunk/ippconfig/gpc1/format_mef.config

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:

• trunk/ippconfig/gpc1/format_mef.config (modified) (2 diffs)

trunk/ippconfig/gpc1/format_mef.config

@@ -13 +13 @@
         PHU             STR     FPA        # The FITS file represents a complete camera fpa
         EXTENSIONS      STR     CHIP       # The extensions represent chips
-        FPA.NAME        STR     CONTROLR   # A PHU keyword for unique identifier within the hierarchy level
+        FPA.OBS         STR     CONTROLR   # A PHU keyword for unique identifier within the hierarchy level
 END
 
@@ -196 +196 @@
         FPA.INSTRUMENT  STR     GPC1
         FPA.DETECTOR    STR     GPC1
-        FPA.NAME        S32     12345
+        FPA.OBS S32     12345
         FPA.TIMESYS     STR     UTC
         CHIP.XPARITY    S32     1