IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/ippTools/src/chiptool.c

    r13891 r13937  
    173173    }
    174174
    175     psString recipe = psMetadataLookupStr(&status, config->args, "-set_recipe");
    176     if (!status) {
    177         psError(PS_ERR_UNKNOWN, false, "failed to lookup value for -set_recipe");
     175    psString reduction = psMetadataLookupStr(&status, config->args, "-set_reduction");
     176    if (!status) {
     177        psError(PS_ERR_UNKNOWN, false, "failed to lookup value for -set_reduction");
    178178        return false;
    179179    }
     
    243243
    244244        // queue the exp
    245         if (!chipQueueExpTag(config, exp_tag, workdir, label, recipe, expgroup, dvodb)) {
     245        if (!chipQueueExpTag(config, exp_tag, workdir, label, reduction, expgroup, dvodb)) {
    246246            if (!psDBRollback(config->dbh)) {
    247247                psError(PS_ERR_UNKNOWN, false, "database error");
     
    804804                    processedExp->workdir,
    805805                    processedExp->label,
    806                     processedExp->recipe,
     806                    processedExp->reduction,
    807807                    processedExp->expgroup,
    808808                    processedExp->dvodb
     
    999999        pendingExp->workdir,
    10001000        pendingExp->label,
    1001         pendingExp->recipe,
     1001        pendingExp->reduction,
    10021002        pendingExp->expgroup,
    10031003        pendingExp->dvodb
Note: See TracChangeset for help on using the changeset viewer.