Changes between Version 139 and Version 140 of ippToPsps

Timestamp:

Aug 3, 2011, 9:00:34 AM (15 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -70 +70 @@
 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/detection/tables.vot example]), which are a standard of the [http://www.ivoa.net/ IVOA]. Because VOTables are an XML format, they 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}}}.
 
-Additionally, a more general configuration file is used to detail the names of databases, location of output files, datastore settings etc. This can be seen [http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/browser/trunk/ippToPsps/jython/config.xml here]
+Additionally, a more general configuration file is used to detail the names of databases, location of output files, datastore settings etc. The path to one of these configuration files is the sole argument to running the code (see below). An example can be seen [http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/browser/trunk/ippToPsps/jython/configs/lap.xml here]
 
 = Using the software =