Changes between Version 57 and Version 58 of ippToPsps_Detections

Timestamp:

Aug 3, 2011, 9:01:45 AM (15 years ago)

Author:

rhenders

Comment:

--

ippToPsps_Detections

@@ -201 +201 @@
 || calibModNum||unknown||SMALLINT||0||calibration modification number|| NA || hardcoded to 1||
 || dataRelease||unknown||TINYINT||0||Data release when this color calibration was established|| NA || hardcoded to 0 ||
-= Running =
-
-To create and publish detection batches, do the following from the IPP trunk:
-
-
-{{{
-cd ippToPsps/perl
-./makeDetections.pl
-}}}
- 
-This will list all options. Essentials are the following:
-
-{{{
-* REQUIRED: need to provide an output path  -o <path>
-* REQUIRED: need to provide a DVO Db        -d <dvoDb>
-* REQUIRED: need to provide a DVO location  -l <dvoLocation>
-}}}
-
-Running with just these arguments will create batches for all unprocessed exposures available in the provided DVO database. It will store the batches in the provided output directory. To publish the batches to the datastore, the {{{-p}}} argument (datastore product) must be provided.
-
-The script connects with the ippToPsps database, so is aware of what has and has not already been processed and published. Only using the {{{-f}}} option can you force it to re-process a batch. '''Note''' that publishing the same exposure under two different batch names will cause havoc for the ODM, so be careful with the {{{-f}}} option.
-
-Example usage would be:
-
-{{{
-./makeDetections.pl -o . -d ThreePi.V1 -l /data/ipp004.0/gpc1/catdirs/ThreePi.V1 -p PSPS_test
-}}}
-
-This will work through all available exposures in the DVO database '!ThreePi.V1' at the location specified, and publishing to the 'PSPS_test' datastore product, updating the ippToPsps database as it proceeds. Querying this database allows you to see what has been processed, the failure rate, what has been published to the datastore etc.