Changes between Version 106 and Version 107 of ippToPsps

Timestamp:

Sep 27, 2010, 12:22:10 PM (16 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -27 +27 @@
 All FITS tables mirror PSPS database tables. Since the PSPS schema will probably remain in a state of flux for some time, rather than hard-coding table descriptions, instead {{{ippToPsps}}} reads table shapes from an XML config. This config can be regenerated from the master PSPS schema using a Perl script ({{{pspsSchema2xml.pl}}}) in the scripts directory. The same script also generates C header files for each batch-type. These headers contains enums for each PSPS table and are used by the code at runtime. This helps minimise code changes.
 
-== Initialisation data ==
+== Initialization data ==
 
 The table shapes of the initialisation batch are handled as above. The actual initialisation data (lists of filters etc), which is liable to change, is held in a config and used by {{{ippToPsps}}} to populate the tables in the FITS file. This data is also used when generating other batch types, detections for example, as look-up tables for setting survey ID etc.
@@ -48 +48 @@
 
 Performs validation on incoming data based on metadata previously loaded as an initialisation batch (see above). If validation is successful, new batches are merged into the PSPS database. One basic requirement of the ODM is that all detections in a detection batch have unique object IDS. Object IDs are assigned by the IPP DVO to each detection on a chip. The number is formulated from the Ra and Dec of the detection.
+
+= Deletion policy = 
+
+When loading, two copies of the data exist: the batches on the datastore and the original files on disk. The deletion policy at present is:
+
+ * when a batch has been loaded to the ODM and has a status of 'merge worthy', then the copy on the datastore is removed
+ * when a batch has been successfully merged into the PSPS database, the copy on local disk is deleted
+
+The logic for this is that errors may occur during the merge phase, and it is useful to have a copy of any offending batches locally for debugging purposes.
 
 = Recovery system design =