Changes between Version 35 and Version 36 of ippToPsps

Timestamp:

Mar 18, 2010, 12:13:27 PM (16 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -14 +14 @@
 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.
 
-The 'products', or 'batch types' generated by {{{ippToPsps}}} are as follows:
-
- * ''''Initialisation' batch (IN)'''[[BR]]
- * ''''Detection' batch (P2)'''[[BR]]
- * ''''Difference' batch (OB)'''[[BR]]
- * ''''Stack' batch (ST)'''[[BR]]
-
-The initialisation batch contains numerous metadata tables that describe the data in the other batches, for example, filter IDs, survey IDs etc.
+The outputs of {{{ippToPsps}}} are referred to as 'batches', and
+
+||'''Batch name''' || '''PSPS name''' || '''Description''' || '''IPP Source''' ||
+|| Initialisation || IN || Metadata for the other batches eg filter ID, survey ID etc || generated from XML config ||
+|| Detection || P2 || Single exposure detections || generated from one {{{smf}}} file per exposure ||
+|| Difference || OB || difference image detections|| generated from one {{{cmf}}} file per skycell per exposure ||
+|| Stack || ST || stack image detections || generated from... ||
 
 = Architecture =