Changes between Version 239 and Version 240 of ippToPsps

Timestamp:

Apr 2, 2012, 5:57:42 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -64 +64 @@
 Each batch type produced by {{{ippToPsps}}} (detection, stack, init etc) has its own class, all of which inherit from the Batch base-class, which handles features common to all batches, such as creating and opening output FITS files, connecting to the GPC1 database, connecting with the DVO database etc. This keeps duplicated code at a minimum. The Batch class is an abstract class, i.e. it should not, and cannot, be instantiated.
 
-{{{ippToPsps}}} works like this:
-
- * reads all relevant FITS tables from a given {{{smf}}} or {{{cmf}}} into temporary tables in a 'scratch' MySQL database
- * creates empty MySQL tables for PSPS output (also in the 'scratch' database). These tables match the shape of the final PSPS database tables exactly.
- * copies all relevant columns from the temporary IPP tables into the PSPS tables, discarding duplicates where necessary
- * accesses the DVO database and creates temporary MySQL tables containing all the detections for this {{{smf}}} or {{{cmf}}}
- * updates the PSPS tables with the IDs from the DVO MySQL tables
- * replaces any NULL values with -999, as required by the PSPS loader
- * exports the PSPS tables to a FITS file
- * publishes FITS file, complete with a batch 'manifest' file, to the datastore
-
-The reading and export of FITS tables is done using STILTS. For import, we can specify which columns we wish to import from the IPP smf and cmf files (we don't need everything).
+
 
 == Configuration ==