Changes between Version 245 and Version 246 of ippToPsps

Timestamp:

Apr 3, 2012, 1:57:00 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -73 +73 @@
 
 Another configuration is used to describe a particular 'loading campaign', complete with the names of databases, location of output files, datastore settings etc. This configuration is stored in the {{{ippToPsps}}} database. Details can be found [wiki:ippToPsps_Database#Theconfigtable here]. All {{{ippToPsps}}} programs require the name of a config at startup as the first argument. Changes to the config can be made at any time, and programs will update accordingly. Most fields are self-explanatory, others that are less obvious will be explained below in the ''Using the software'' section.
-== The {{{ippToPsps}}} database ==
-
-A full description of the {{{ippToPsps}}} database is detailed [wiki:ippToPsps_Database here]
-
+== Databases ==
+
+{{{ippToPsps}}} programs use up to four databases. All access the {{{ippToPsps}}} database, which tracks all processing of batches through {{{ippToPsps}}}. A full description of the {{{ippToPsps}}} database is detailed [wiki:ippToPsps_Database here]. {{{loader.py}}} and {{{queue.py}}} both also make use of a 'scratch' database, a database on the local machine used during processing with data discarded upon completion. Details of the scratch database can be found [wiki:ippToPsps_ScratchDatabase here].
 == DVO ==