IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 101 and Version 102 of ippToPsps


Ignore:
Timestamp:
Jun 29, 2010, 8:48:07 AM (16 years ago)
Author:
rhenders
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ippToPsps

    v101 v102  
    1313|| Initialisation || IN || Metadata for the other batches eg filter ID, survey ID etc || generated from XML config ||
    1414|| [wiki:ippToPsps_Detections Detections] || P2 || Single exposure detections || generated from one {{{smf}}} file per exposure plus associated DVO database ||
    15 || Difference || ? || difference image detections|| generated from one {{{cmf}}} file per skycell per exposure ||
    16 || Stack || ST || stack image detections || generated from... ||
     15|| [wiki:ippToPsps_Difference Difference] || ? || difference image detections|| generated from one {{{cmf}}} file per skycell per exposure ||
     16|| [wiki:ippToPsps_Stack Stack] || ST || stack image detections || generated from... ||
    1717
    1818[[BR]]
     
    4848Performs 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.
    4949
    50 = Notes about the different batch types =
    5150
    52 == Detections ==
    5351
    54 The input for the detection batch is one IPP camera-stage {{{smf}}} file for a given exposure, as well as an associated DVO database from which to retrieve object, and other, IDs. One FITS file is generated for each exposure. The extensions are:
    5552
    56 1 '''{{{Primary}}}''' extension[[BR]]
    57 1 '''{{{FrameMeta}}}''' extension[[BR]]
    58 1 '''{{{ImageMeta}}}''' extension per chip[[BR]]
    59 1 '''{{{Detection}}}''' extension per chip[[BR]]
    60 1 '''{{{SkinnyObject}}}''' extension per chip[[BR]]
    61 1 '''{{{ObjectCalColor}}}''' extension per chip[[BR]]
    62 
    63 So, 242 extensions in all, including the obligatory primary header. The 'object ID' is featured in the last three tables, and must remain unique across the exposure (it is generated within DVO). In the merged PSPS database, the primary key on the detections table is both the object ID and detection ID, meaning the the same object can appear in multiple, overlapping exposures as they will have different detection IDs.
    6453
    6554== Diffs ==