Changes between Version 14 and Version 15 of BillsPSPSToIPP

Timestamp:

Sep 23, 2015, 9:33:42 AM (11 years ago)

Author:

bills

Comment:

--

BillsPSPSToIPP

@@ -49 +49 @@
 }}}
 
-Detection to corresponding row in DVO
--------------------------------------
+== Detection to corresponding row in DVO ==
 
 mostly dvo queries to particular detections are by obsTime.
@@ -154 +153 @@
 Then given the exp_id, and skyCellID one can go to the IPP's gpc1
 database and find the fullForceResult. (Well, one would need to know
-the label or the skycal_id). 
+the label or the skycal_id). Th
 
 
 {{{
     fftool -result -label SAS.20141118.ff8 -exp_id $frameID -tess_id $tessID -skycell_id $skyCellID
-
-}}}
-
+}}}
+
+This result will also give the ff_id of the corresponding run.
+
+== ForcedWarpMeasurement to DVO
+The entry in the dvo images table is the one where EXTERN_ID == the warp_skyfile_id of the corresponding warp. This can be found from
+
+{{{
+warptool -warped -exp_id 356845 -skycell_id skycell.1315.036 -label SAS.20141118
+}}}
+
+'''SUGGESTION''':  I have added warp_skyfile_id to the output of fftool -result so this step can be avoided.
+
+The steps to find data in the dvo files is similar to that for regular detections.
+ 1. Look for IMAGE_ID of entry in Images.dat with EXTERN_ID == warp_skyfile_id
+ 2. Use dvoRegionID to find the NAME of the corresponding DVO files in SkyTable.fits
+ 3. Find measurements with IMAGE_ID and DET_ID == ippDetectID
 
 == Stack Tables ==