Changes between Version 1 and Version 2 of DetectionsToMeasurements

Timestamp:

Sep 16, 2015, 2:51:03 PM (11 years ago)

Author:

bills

Comment:

--

DetectionsToMeasurements

@@ -11 +11 @@
 
 The smf file contains 2 extensions for each OTA in the exposure. The extension that we are interested in is the '.psf' extension. The other
-contains the results of the detection efficience measurements.
+contains the results of the detection efficiency measurements.
 
 == Creating a concatenated file containing all detections in one table ==
@@ -23 +23 @@
 neb://any/SAS2/SAS.20141118/o5745g0427o.356801/o5745g0427o.356801.cm.1218577.smf
 }}}
-And then the concatsmf may be used to extractx the detections
+And then the concatsmf may be used to extract the detections
 {{{
 % concatsmf neb://any/SAS2/SAS.20141118/o5745g0427o.356801/o5745g0427o.356801.cm.1218577.smf o5745g0427o.356801.cm.1218577.smf.tcat
@@ -34 +34 @@
 HDU 1   Primary Array      Image      Int1(3627)                    
 HDU 2   o5745g0427o.356801.cm.1218577.smf BinTable    58 cols x 58059 rows    
+
+NOTE: concatsmf assumes that the basename of the smf file has begins format $exp_name.$exp_id.cm.$cam_id (but only exp_id is currently used)
 }}}
 
@@ -39 +41 @@
 
 Next we go to PSPS and find Detections from this exposure with the query
+
+{{{
+select imageID/100 frameID, Detection.*  INTO mydb.[o5745g0427o_356801] FROM Detection where imageID/100=356801
+
+The frameID is not necessary, I added it because I thought that it might be useful.
+}}}
+
+After downloading the results of this query we find that there are only 58014 detections. 45 apparently did not make their way into PSPS.
+
+Did they get lost loading into DVO or in the ippToPsps process?
+
+Let's figure out what's missing.
+
+The next step is to trace the detections in PSPS back to the DVO catalog.