Changes between Version 119 and Version 120 of ippToPsps
- Timestamp:
- Dec 27, 2010, 3:56:25 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ippToPsps
v119 v120 37 37 = Architecture = 38 38 39 == ippToPsps == 40 41 {{{ippToPsps}}} is written in C under the IPP source repository. When compiled, there is an executable-per-batch type: 39 {{{ippToPsps}}} is written in C under the IPP source repository. When compiled, there is one executable-per-batch type: 42 40 43 41 {{{ … … 52 50 When run, the above programs generate a single FITS file, which are then packaged up and published to the datastore by the Perl code, ready for collection by the {{{DXLayer}}} (below). 53 51 54 == = Design ===52 == Design == 55 53 56 54 Each batch type (detection, stack, init etc) is it's 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 is an abstract class, i.e. it should not, and cannot, be instantiated. … … 58 56 Each class has a single header file and a single source file. Public fields and methods are visible in the class (struct) definition in the header. Private members and functions are declared as static in the associated source files, thus keeping them encapsulated. All class code is contained in a single C file. Methods are accessed via function pointers in the structure. 59 57 60 = = DXLayer ==58 = Running = 61 59 62 The {{{DXLayer}}} polls the datastore waiting for new batches. Upon receipt of a new batch, the FITS files are converted to a csv format, suitable for ingest by the ODM. 63 64 == ODM Loader == 65 66 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. 67 68 = Deletion policy = 60 == Deletion policy == 69 61 70 62 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:
