Changes between Version 7 and Version 8 of DetectionsToMeasurements
- Timestamp:
- Sep 16, 2015, 3:37:10 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DetectionsToMeasurements
v7 v8 82 82 }}} 83 83 84 85 86 The next step is to trace the detections in PSPS back to the DVO catalog. 84 45 missing detections. The next step is to trace the detections in PSPS back to the DVO catalog. 87 85 88 86 == Finding particular detections in the DVO catalog files == … … 96 94 97 95 If we just want to find which catalog and dvo "image" contains this detection we can use 98 { 96 {{{ 99 97 (ipp079:~/work/psps) bills% detectToMeasure --ra 333.719989076316 --dec -4.47253338047446 --exp_id 356801 --class_id XY24 100 98 RA DEC NAME CAT_ID EXTERN_ID IMAGE_ID catalogPrefix 101 99 333.719989076316 -4.47253338047446 s0000/5228.01 NULL 75160686 4638 /data/ipp079.0/gpc1/catdirs/SAS/SAS39.V1/s0000/5228.01 102 } 100 }}} 103 101 To find the missing detection add --det_id 140 104 { 102 {{{ 105 103 detectToMeasure --ra 333.719989076316 --dec -4.47253338047446 --exp_id 356801 --class_id XY24 --det_id 140 --output det140.fit 106 104 … … 112 110 HDU 1 Primary Array Image Int1(3659) 113 111 HDU 2 DVO_MEASURE_PS1_V5 BinTable 63 cols x 1 rows 114 } 112 } }} 115 113 116 114 If the --list-others option is used it will extract all detections for the dvo object for the detection in question. if --list-others --this-image is used it … … 131 129 }}} 132 130 133 Looks like ippToPsps doesn't handle objects with multiple detections in the same image correctly.131 We have two detections from the same DVO object and image. Looks like ippToPsps doesn't handle objects with multiple detections in the same image correctly.
