Changes between Version 286 and Version 287 of ippToPsps

Timestamp:

Apr 5, 2012, 4:16:01 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -121 +121 @@
 === Loading configs ===
 
-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.
-
-All {{{ippToPsps}}} programs take a config argument. This can be one of three things:
+Loading configs are the where the user actually defines what {{{ippToPsps}}} should do for a particular 'loading campaign'. This configuration data is stored in the {{{ippToPsps}}} database, details of which can be found [wiki:ippToPsps_Database#Theconfigtable here]. All {{{ippToPsps}}} programs require a config argument at start-up. This can be one of three things:
 
  * the name of a particular config currently in the [wiki:ippToPsps_Database#Theconfigtable config table of the database], meaning that program will run using only that config
@@ -130 +128 @@
 
 The 'all' option is handy for programs like {{{metrics.py}}} or {{{cleanup.py}}}; instead of having an intance of these programs per config, one instance can cycle through them all. The {{{edit}}} option can be used when creating a config for the first time, or to edit an existing one.
+
+In addition, changes to configs can be made at any time and programs will update accordingly.
 == Databases ==