Changes between Version 12 and Version 13 of ippToPsps

Timestamp:

Feb 16, 2010, 2:01:22 PM (16 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -8 +8 @@
 = Introduction =
 
-{{{ippToPsps}}} is the interface between IPP and PSPS. In short, {{{ippToPsps}}} creates FITS files from data found in 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, converts the contents to {{csv}} files then sends them on to a special MSSQL loader software, which inserts 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 data found in 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 inserts 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}}} will match the PSPS database schemas perfectly, the consequence being that any alterations to the PSPS database schema will only require changes to {{{ippToPsps}}} code, and not the DXLayer. A certain amount of data validation will be performed by {{ippToPsps}} before publication
+It is intended that the binary tables in the FITS files generated by {{{ippToPsps}}} will 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.
 
-= {{{ippToPsps}}} products =
+= Architecture =
+
+{{ippToPsps}} is a C program within the IPP build. When given the correct arguments it will generate a single FITS for the specified product (above). The program is run from a perl script, which itself generates a list of exposure IDs based on arguments provided by the user (label etc). An instance of {{{ippToPsps}}} is run per exposure ID.
+
+= Products =
 
 {{{ippToPsps}}} creates three ''products''.
@@ -20 +24 @@
  * '''Stacks'''
 
-= Architecture =
-
-{{ippToPsps}} is a C program within the IPP build. When given the correct arguments it will generate a single FITS for the specified product (above). The program is run from a perl script, which itself is provided ... in order to generate the arguments necessary to run {{ippToPsps}}.
-
-= Input and output =
-
 == Detections ==
 
 '''Input'''
 
-Input is one {{smf}} file for a given exposure and an associated DVO database from which to retrieve object IDs.
+Input is one {{smf}} file for a given exposure and an associated DVO database from which to retrieve object, and other, IDs.
 
 '''Output'''