Changes between Version 192 and Version 193 of ippToPsps

Timestamp:

Mar 9, 2012, 2:28:07 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -238 +238 @@
 This will produce an IN batch, publish it, then stop (the IN-batch MySQL tables will also be updateded in the local scratch database).
 
-=== Queuing ===
-
-Before any loading clients can do anything, you must queue something up. To do this run:
-
-{{{
-./run.sh queue.py someConfig
-}}}
-
-When run, {{{load.py}}} first queues up all the exposures or stacks that it needs to process, then works through them sequentially, doing detections first then stacks. The master list comes from the gpc1 {{{addRun}}} table, which lists all items currently merged into the DVO database we are using. From this list, {{{ippToPsps}}} subtracts items that have already been successfully loaded to the datastore already, and queues up the remainder.
-
-Because it is possible, and usual, to run multiple versions of {{{load.py}}} in order to speed up loading time, the methods to queue and begin processing a new batch form a critical section. This simply means that the 'batch' table in the {{{ippToPsps}}} database is locked by a client looking for a new item to process, then released afterwards. 
-
-An important factor in the queuing of items is the current ''epoch'', which is set in the config.
+
 
 === Epochs ===