Changes between Version 133 and Version 134 of ippToPsps

Timestamp:

Aug 2, 2011, 2:58:39 PM (15 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -4 +4 @@
 [[PageOutline]]
 
-{{{ippToPsps}}} is the interface between IPP and PSPS. It creates FITS files generated from a multitude of IPP data-sources, then publishes them to a datastore in the form of ''batches''. On the PSPS side, the {{{DXLayer}}} polls the datastore, collects batches when they become available, then converts the contents to {{{csv}}} files before sending them on to SQL Server loader software, which ''merges'' them into the PSPS database. 
+{{{ippToPsps}}} is the interface between IPP and PSPS, tasked with publishing science products from the former to the latter. At the highest level, its job is to create FITS files, generated from a multitude of IPP data-sources, and then publishe them to a datastore in the form of ''batches''. On the PSPS side, the {{{DXLayer}}} polls the datastore, collects batches when they become available, then converts the contents to {{{csv}}} files before sending them on to SQL Server loader software, which ''merges'' them into the relevant PSPS database. 
 
-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 is performed by {{{ippToPsps}}} before publication, with more validation occurring at the loading and merge stages on the PSPS side.
+The binary tables in the FITS files generated by {{{ippToPsps}}} match the PSPS database schema 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 is performed by {{{ippToPsps}}} before publication, with more validation occurring at the loading and merge stages on the PSPS side.
 
-Simultaneously to loading data, {{{ippToPsps}}} polls PSPS to inquire after the status of the batches it has loaded. Batches that failed can then be reloaded. The status of every batche is maintained in a MySQL database local to {{{ippToPsps}}}.
+Simultaneously to loading data, {{{ippToPsps}}} polls PSPS to inquire after the status of the batches it has loaded. Batches that failed can then be reloaded. The status of every batch is maintained in a MySQL database local to {{{ippToPsps}}}.
 
 The outputs of {{{ippToPsps}}} are referred to as 'batches', and are detailed below.