Changes between Version 166 and Version 167 of ippToPsps

Timestamp:

Oct 5, 2011, 2:45:57 PM (15 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -8 +8 @@
 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 batch 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 various temporary copies of the batches are deleted once the ODM reports that they have been successfully loaded or merged.
 
 = Batch types =
@@ -18 +18 @@
 || [wiki:ippToPsps_Detections Detections] || P2 || single exposure detections || generated from one {{{smf}}} file per exposure plus associated DVO database ||
 || [wiki:ippToPsps_Stack Stack] || ST || stack image detections || one FITS file generated per IPP {{{cmf}}}, which contains data for one filter on one skycell ||
-|| [wiki:ippToPsps_Difference Difference] || ? || difference image detections|| generated from one {{{cmf}}} file per skycell per exposure ||
 
 [[BR]]