IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 193 and Version 194 of ippToPsps


Ignore:
Timestamp:
Mar 9, 2012, 2:30:58 PM (14 years ago)
Author:
rhenders
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ippToPsps

    v193 v194  
    9898== queue.py ==
    9999
    100 This program populates tables in the ippToPsps database so that any {{{loader.py}}} programs know what to processes. Data to be processed is divided up in a grid on the sky, using the RA/Dec and box-size settings in the config. The {{{plotter.py}}} program can generate a density plot of data still to be processed through {{{ippToPsps}}}, an example of which is shown below.
     100Before any {{{loader.py}}} clients can do anything, you must queue something up. To do this run:
     101
     102{{{
     103./run.sh queue.py someConfig
     104}}}
     105
     106Data to be processed is divided up in a grid on the sky, using the RA/Dec and box-size settings in the config. The {{{plotter.py}}} program can generate a density plot of data still to be processed through {{{ippToPsps}}}, an example of which is shown below.
    101107
    102108[[Image(new3pi_P2_2012_0308_135938.png)]]
     109
     110
     111The master list of items to be processed comes from the gpc1 {{{addRun}}} table, which lists all items currently merged into the DVO database we are using. From this list, {{{queue.py}}} subtracts items that have already been successfully loaded to the datastore already, as well as items that have routinely failed to process, and queues up the remainder.
    103112== loader.py ==
    104113