Changes between Version 39 and Version 40 of ippToPsps

Timestamp:

Mar 18, 2010, 12:51:32 PM (16 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -6 +6 @@
 = Introduction =
 
-{{{ippToPsps}}} is the interface between IPP and PSPS. In short, {{{ippToPsps}}} creates FITS files from IPP {{{smf}}} and {{{cmf}}} files (as well as relevant DVO databases), then publishes them to a datastore in the form of ''jobs''. On the PSPS side, the DXLayer polls the datastore, collects jobs when they become available, then converts the contents to {{{csv}}} files before sending them on to special MSSQL loader software, which ''merges'' them into the PSPS database. Ultimately there will be feedback from PSPS regarding errors in the received data, to which {{{ippToPsps}}} will need to respond.
+{{{ippToPsps}}} is the interface between IPP and PSPS. In short, {{{ippToPsps}}} creates FITS files from IPP data, then publishes them to a datastore in the form of ''jobs''. On the PSPS side, the DXLayer polls the datastore, collects jobs when they become available, then converts the contents to {{{csv}}} files before sending them on to special MSSQL loader software, which ''merges'' them into the PSPS database. Ultimately there will be feedback from PSPS regarding errors in the received data, to which {{{ippToPsps}}} will need to respond.
 
 It is intended that the binary tables in the FITS files generated by {{{ippToPsps}}} match the PSPS database schemas perfectly, the consequence being that any alterations to the PSPS database schema will only affect {{{ippToPsps}}} code, and not the DXLayer. A certain amount of data validation will be performed by {{{ippToPsps}}} before publication, more validation occurring at the loading and merge stages on the PSPS side.
@@ -22 +22 @@
 = Configuration =
 
-Due to the potential for changes in both input and output for {{{ippToPsps}}}, the code is heavily configurable. Config files are in an XML format as this affords the most flexibility (XML is both human and machine readable, expandable, self-description etc). {{{ippToPsps}}} is pointed to a config directory, under which subdirectories for each batch type hold the various XML config files.
+Due to the potential for changes in both input and output for {{{ippToPsps}}}, 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.
 
 == Table shapes ==