Changeset 24973

Timestamp:

Aug 2, 2009, 4:27:26 PM (17 years ago)

Author:

eugene

Message:

allow dvo to accept supplied zero point information

Location:

trunk/Ohana/src/addstar

Files:

• Makefile (modified) (1 diff)
• doc/notes.txt (modified) (1 diff)
• include/addstar.h (modified) (2 diffs)
• src/ConfigInit.c (modified) (1 diff)
• src/GetZeroPointExposure.c (added)
• src/LoadData.c (modified) (1 diff)
• src/ReadImageHeader.c (modified) (4 diffs)

trunk/Ohana/src/addstar/Makefile

@@ -58 +58 @@
 $(SRC)/greference.$(ARCH).o \
 $(SRC)/grefstars.$(ARCH).o \
+$(SRC)/GetZeroPointExposure.$(ARCH).o \
 $(SRC)/LoadStars.$(ARCH).o \
 $(SRC)/LoadHeaders.$(ARCH).o \

trunk/Ohana/src/addstar/doc/notes.txt

@@ +1 @@
+
+2009.08.02
+
+  ZERO POINTS: addstar currently has a couple of inconsistent ways that it 
+  measures or uses image zero points:
+
+  * the standard zero point: data in the database is saved as M_inst +
+    25.0.  This value is written to the image header and checked when
+    the image is loaded.  This is completely archaic, but removing
+    this concept from the DVO system will require some work and some
+    care.  This value is NOT reflected in the image->Mcal values
+
+  * on-the-fly calibration: addstar was used by CFHT skyprobe to
+    measure the sky transparency.  This calculation was done by
+    measuring the zero point between the Tycho stars in the database
+    and the stars in the image.  Star data is saved in
+    AddToCalibration as they are found (in find_matches, or
+    equivalent).  At the end of the match processing, the zero point
+    for the image was calculated with FindCalibration and saved to the
+    image table but NOT the measure table.  For skyprobe, the stars
+    are normally not saved to the database -- the Tycho stars are kept
+    in the measure & average tables, and used as the reference for the
+    zero point calculation above.
+
+  For Pan-STARRS, the zero point analysis is performed by psastro
+  before we run addstar.  However, there are a few ways we could
+  choose to apply the zero point calculation:
+
+  * use the per-chip zero point reported in the individual chip
+    headers (easy, but fairly wrong)
+
+  * calculate the per-exposure zero point from the chip headers and
+    supply.
+
+  * calculate the per-exposure zero point from the MATCHED_REFS table
+
+  We also need to consider the zero point error.  We currently have
+  only dM (poisson error) + dMcal (calibration error).  We need to
+  divide dMsys into dMcal (photometry calibration error) and dMap
+  (aperture correction error).
+
+  * zero point options:
+    * NOMINAL : set Mcal = 0.0
+    * CHIP_HEADER : each chip has zero point in header
+    * PHU_HEADER : a single exposure-wide value in the header
+    * CHIP_AVERAGE : determine zero point for exposure from chip zero points
+    * MATCHED_REFS : recalculate from table
 
 2009.02.11

trunk/Ohana/src/addstar/include/addstar.h

@@ -118 +118 @@
 double  FAKE_THETA;     // boresite angle for fake images
 
+char    ZERO_POINT_OPTION[64];
+float   ZERO_POINT_OFFSET;
+
 // carries the mosaic into gstars
 
@@ -187 +190 @@
 HeaderSet *MatchHeaders           PROTO((int **extsize, int *nimage, int mode, Header **headers, int Nheaders));
 int        LoadData               PROTO((FILE *f, char *file, Image **images, int *nvalid, Stars **stars, int *Nstars, Header **headers, int *extsize, HeaderSet *headerSets, int NheaderSets));
+int        GetZeroPointExposure   PROTO((Header **headers, HeaderSet *headerSets, int Nimages));
 
 int        in_image               PROTO((double r, double d, Image *image));

trunk/Ohana/src/addstar/src/ConfigInit.c

@@ -77 +77 @@
   if (!ScanConfig (config, "EXTNAME-KEYWORD",        "%s",  0, ExtnameKeyword)) {
       strcpy (ExtnameKeyword, "EXTNAME"); 
+  }
+
+  // if this config variable is not set, do not set any zero point offset
+  if (!ScanConfig (config, "ZERO_POINT_OPTION", "%s",  0, ZERO_POINT_OPTION)) {
+      strcpy (ZERO_POINT_OPTION, "NOMINAL"); 
   }
 

trunk/Ohana/src/addstar/src/LoadData.c

@@ -24 +24 @@
   // find image rootname
   name = filebasename (file);
+
+  // if zero points are calculated for the full exposure using more than just the matched chip header,
+  // we need to perform that analysis here
+  GetZeroPointExposure (headers, headerSets, Nimages);
 
   // now run through the images, interpret the headers and read the stars

trunk/Ohana/src/addstar/src/ReadImageHeader.c

@@ -8 +8 @@
   double tmp, sec, Cerror, ZeroPt, FWHM_X, FWHM_Y;
   char *c, photname[64], line[80];
+  PhotCode *photcodeData;
 
   // zero out the entire image structure
@@ -104 +105 @@
       return (FALSE);
     }
-    photcode = GetPhotcodeCodebyName (photname);
-    if (photcode == 0) {
+    photcodeData = GetPhotcodebyName (photname);
+    if (photcodeData == NULL) {
       fprintf (stderr, "photcode %s not found in photcode table\n", photname);
       return (FALSE);
     }
+    photcode = photcodeData[0].code;
   }
   if (photcode == 0) { 
@@ -191 +193 @@
   }
 
+  // XXX this is archaic: we used to set a fixed zero point of 25 to shift data into the range
+  // 0 - 32 so it would fit in an unsigned int.  This is also needed because some programs like
+  // sextractor will put in an arbitrary zero point that we need to understand to get back to
+  // instrumental mags.  
   gfits_scan (header, "ZERO_PT", "%lf", 1, &ZeroPt);
   if (ZeroPt != GetZeroPoint()) {
@@ -197 +203 @@
   }
 
+  // if it exists, find the 
+  if (!strcasecmp(ZERO_POINT_OPTION, "CHIP_HEADER")) {
+      float ZPT_OBS;
+      if (!gfits_scan (header, "ZPT_OBS", "%f", 1, &ZPT_OBS)) {
+          fprintf (stderr, "zero point not supplied in header\n");
+          ZERO_POINT_OFFSET = 0.0;
+      } else {
+          ZERO_POINT_OFFSET = 0.001*photcodeData[0].C - ZPT_OBS;
+      }   
+  }
+
   /* secz is in units milli-airmass */
-  image[0].Mcal = 0.0;
+  image[0].Mcal = ZERO_POINT_OFFSET;
   image[0].Xm   = NAN_S_SHORT;
   image[0].flags = 0;