Changes between Version 285 and Version 286 of ippToPsps

Timestamp:

Apr 5, 2012, 4:13:23 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -109 +109 @@
 == Configuration ==
 
+Three types of configuration exist for {{{ippToPsps}}}, but only loading configs will be of much interest to the user.
+
+=== PSPS table descriptions ===
+
 Due to the potential for changes in both input and output for {{{ippToPsps}}}, rather than hard-coding table descriptions, the code is heavily configurable. As such, the tables descriptions are stored as [http://www.ivoa.net/Documents/VOTable/20040811/REC-VOTable-1.1-20040811.html VOTable] files (for [http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/browser/trunk/ippToPsps/config/P2/tables.vot example]), which are a standard of the [http://www.ivoa.net/ IVOA]. Because VOTables are an XML format, they are both human and machine readable, expandable and self-describing. These VOTables are generated directly from the PSPS schema using a [http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/browser/trunk/ippToPsps/perl/pspsSchema2xml.pl script], so that any changes to the schema can be easily passed-along to {{{ippToPsps}}}.
+
+=== Settings file ===
+
+This XML file contains configuration information that does not need to change per loading campaign, eg things like database locations and where to store logs. It can be found under svn [browser:trunk/ippToPsps/config/settings.xml settings here].
+
+=== 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.
@@ -120 +130 @@
 
 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.
-
 == Databases ==