Changes between Version 5 and Version 6 of DetectionsToMeasurements

Timestamp:

Sep 16, 2015, 3:33:37 PM (11 years ago)

Author:

bills

Comment:

--

DetectionsToMeasurements

@@ -5 +5 @@
 
 While triaging SAS 39 it became clear that connecting the data in the PSPS back to the source in the IPP and DVO was non-trivial. We need to do
-this to insure the completeness and integrity of the PSPS database. 
+this when debugging the completeness and integrity of the ippToPsps process. 
 
-The first thing Bill attacked was comparing the data in the Detection Table  (single frame detections) with the original psphot detections which
+The first thing I attacked was comparing the data in the Detection Table  (single frame detections) with the original psphot detections which
 are located in a camera stage '.smf' file.
 
@@ -19 +19 @@
 
 The program is a perl scrip that uses standard IPP programs and the [http://www.star.bristol.ac.uk/~mbt/stilts/ STILTS library]. Several of the
-examples here also use programs from [https://heasarc.gsfc.nasa.gov/ftools/ftools_menu.html FTOOLS] in particular ftlist.
+examples here also use programs from [https://heasarc.gsfc.nasa.gov/ftools/ftools_menu.html FTOOLS] in particular ftlist but the scripts do
+not use anything from FTOOLS.
 
 Consider the SAS2 exposure 356801. The smf file may be found with the following command.
@@ -26 +27 @@
 neb://any/SAS2/SAS.20141118/o5745g0427o.356801/o5745g0427o.356801.cm.1218577.smf
 }}}
-And then the concatsmf may be used to extract the detections
+The progarm concatsmf may be used to extract the detections into a file containing a single table.
 {{{
 % concatsmf neb://any/SAS2/SAS.20141118/o5745g0427o.356801/o5745g0427o.356801.cm.1218577.smf o5745g0427o.356801.cm.1218577.smf.tcat