| | 26 | |
| | 27 | = Running = |
| | 28 | |
| | 29 | To create and publish detection batches, do the following from the IPP trunk: |
| | 30 | |
| | 31 | |
| | 32 | {{{ |
| | 33 | cd ippToPsps/perl |
| | 34 | ./makeDetections.pl |
| | 35 | }}} |
| | 36 | |
| | 37 | This will list all options. Essentials are the following: |
| | 38 | |
| | 39 | {{{ |
| | 40 | * REQUIRED: need to provide an output path -o <path> |
| | 41 | * REQUIRED: need to provide a DVO Db -d <dvoDb> |
| | 42 | * REQUIRED: need to provide a DVO location -l <dvoLocation> |
| | 43 | }}} |
| | 44 | |
| | 45 | Running with just these arguments will create batches for all unprocessed exposures and store them in the provided output directory. To publish the batches to the datastore, the {{{-p}}} argument 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}}} force option can you force it to re-process a batch. |
| | 46 | |
| | 47 | |