Changeset 13937 for trunk/ippTools/src/camtool.c

Timestamp:

Jun 21, 2007, 2:10:11 PM (19 years ago)

Author:

Paul Price

Message:

Changes to multiple packages in order to use "reduction classes" to
specify recipe names. The idea is to give a group of recipes a
symbolic name, which distinguish how the reduction is to be performed,
without going to all the trouble of changing the recipes themselves.

For example, we might want to turn off the usual
overscan/bias/dark/shutter/flat processing and only do photometry if
we have pre-processed data. Gene also wants a similar ability for
building the flat-field correction.

Added a REDUCTION metadata to the camera configuration that contains
multiple METADATA entries that have recipes for different processing
steps. PS::IPP::Config has a 'reduction' function to return the
appropriate recipe, and this is now used in the scripts. Updated
ippTasks to use these where appropriate.

This necessitated changing the database, so that the desired reduction
class can be specified in the right places. Instructions on converting
an extant database are in dbconfig/changes.txt.

Tested with the SIMTEST, and it works.

There is currently no way of specifying the reduction class when an
exposure proceeds from 'register' to 'chip' (it has to be hacked in
the database directly: "update chipPendingExp set reduction =
'SOME_CLASS' where ..."), but it can be specified when adding a
detrend run or queuing chips with 'chiptool -queue' (the '-reduction'
option). Also, the 'recipe' columns remain throughout the detrend
tables, and they continue to be populated with the actual recipe used
(rather than the reduction class; but that is contained in the
detRun).

File:

• trunk/ippTools/src/camtool.c (modified) (5 diffs)

trunk/ippTools/src/camtool.c

@@ -184 +184 @@
     }
 
-    psString recipe = psMetadataLookupStr(&status, config->args, "-set_recipe");
-    if (!status) {
-        psError(PS_ERR_UNKNOWN, false, "failed to lookup value for -set_recipe");
+    psString reduction = psMetadataLookupStr(&status, config->args, "-set_reduction");
+    if (!status) {
+        psError(PS_ERR_UNKNOWN, false, "failed to lookup value for -set_reduction");
         return false;
     }
@@ -237 +237 @@
 
     // would could do this "all in the database" if we didn't want the option
-    // of changing the label/recipe/expgroup/dvodb/etc.  So we're pulling the
+    // of changing the label/reduction/expgroup/dvodb/etc.  So we're pulling the
     // data out so we have the option of changing these values or leaving the
     // old values in place (i.e., passing the values through).
@@ -257 +257 @@
                     workdir     ? workdir   : row->workdir,
                     label       ? label     : row->label,
-                    recipe      ? recipe    : row->recipe,
+                    reduction      ? reduction    : row->reduction,
                     expgroup    ? expgroup  : row->expgroup,
                     dvodb       ? dvodb     : row->dvodb
@@ -617 +617 @@
         pendingRow->workdir,
         pendingRow->label,
-        pendingRow->recipe,
+        pendingRow->reduction,
         pendingRow->expgroup,
         pendingRow->dvodb,
@@ -628 +628 @@
         zp_mean,
         zp_stdev,
-        fwhm,
-        fwhm_range,
-        n_stars,
-        n_extended,
-        n_cr,
-        n_astrom,
+        fwhm,
+        fwhm_range,
+        n_stars,
+        n_extended,
+        n_cr,
+        n_astrom,
         path_base,
         code