| 24 | | Due to the potential for changes in both input and output for {{{ippToPsps}}}, rather than hard-coding table descriptions, the code is heavily configurable. Configuration files are in an XML format, as this affords the most flexibility (human and machine readable, expandable, self-describing etc). {{{ippToPsps}}} is pointed to a config directory, under which subdirectories for each batch type hold the various XML config files. The skeleton for the files below are all created from the PSPS schema using the {{{pspsSchema2xml.pl}}} Perl script (found in the {{{ippToPsps/perl}}} directory). The same script also generates C header files for each batch-type. These headers contains enums for each PSPS table and are used by the code at runtime. This helps minimize code changes. |
| | 24 | 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}}}. |
| 26 | | '''{{{table.xml}}}''' |
| 27 | | |
| 28 | | This file contains full table definitions for this batch type. It is a direct mapping of the PSPS schema. |
| 29 | | |
| 30 | | '''{{{map.xml}}}''' |
| 31 | | |
| 32 | | Most data to be loaded into the FITS tables comes from IPP {{{smf}}} or {{{cmf}}} files. For many columns, there is a direct mapping between these files and the PSPS database columns. These mappings are detailed in this file. |
| 33 | | |
| 34 | | '''{{{data.xml}}}''' |
| 35 | | |
| 36 | | A place to store hard-coded values to go directly into PSPS tables. Currently only the {{{init}}} batch type uses this to populate the init tables with, for example, filter types, survey names etc. This same file is also used by other batch types as look-up tables for setting survey IDs, filters etc. |
| | 26 | 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] |
