Changes between Version 29 and Version 30 of ippToPsps_Detections
- Timestamp:
- Jun 23, 2011, 9:15:55 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ippToPsps_Detections
v29 v30 7 7 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. 8 8 9 The current loading summary can be seen [browser:trunk/ippToPsps/docs/loadingSummary.txt here]10 9 = PSPS tables = 11 10 … … 17 16 1 '''{{{ObjectCalColor}}}''' extension per chip[[BR]] 18 17 19 The full table definitions can be seen [browser:trunk/ippToPsps/config/detection/tables. xmlhere]18 The full table definitions can be seen [browser:trunk/ippToPsps/config/detection/tables.vot here] 20 19 21 20 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.
