Changes between Version 3 and Version 4 of BillsSas39BatchesNotes

Timestamp:

Aug 25, 2015, 10:33:57 AM (11 years ago)

Author:

heather

Comment:

--

BillsSas39BatchesNotes

@@ -18 +18 @@
 Seems like this column is a detection level thing. Maybe an average would be useful?
 
+HAF/EAM: we want the biggest value : need to check if xQFperfect is set in dvo
 
 PSPS_SAS39_P2 "P2 Batch"
@@ -28 +29 @@
 FrameMeta: 1 row
 -999 columns:
-p1Recip, p2Recip, p3Recip
+~~~p1Recip, p2Recip, p3Recip~~~ -- replace those three with "md5sum" from smf
+varchar not 8000 characters long
 
 ImageMeta: 1 row 
@@ -38 +40 @@
     Is the intent that it should be PS_MODEL_PSF (1) but.  That doesn't allow for the possibility 
     for using a different PSF model type in future releases. 
+
+HAF/EAM/KCC: need a table of the models we have used ( fill in FitModel in Metadata Tables) -- fill in fit model, make the cmf have the correct value. SMF header has PSFMODEL keyword
+
+
   detrend4-8
     I think that there are a couple of other detrend types that are used in the processing could be saved 
     here if those would be interesting. 
 
+HAF/EAM/KCC: add a few more detrends: NOISEMAP NONLIN VIDEODARK 7/8 would be ignored
+
 0 valued columns
   should DataRelease be 0? Definitely not in PV3 I think.
   calibModNum. Maybe we should start with 1 instead of 0 for first calibration?
 
+HAF: that's my fault (should be 39 for most sas39 batches) - we should call it 3 for PV3
+EAM/KCC dataRelease -> processingVersion (all tables)
+
 Detection: many rows of course
 -999 columns: None
@@ -66 +77 @@
 What are posImageID and negImageID ?
 
+HAF/EAM/KCC needs more documentation on posImageID/negImageID 
+warp_id  (add postage stamp in there) -  need WarpToImage table 
+
+
 NEEDS REVIEW:
 Ok it looks like posImageID is the warp_id for the diffRun and negImageID looks like it's trying to be
@@ -73 +88 @@
 Or maybe I'm lost.
 
+HAF/EAM/KCC not lost, that was done on purpose for broader time ranges on SAS39. (sas39 warp - 3pipv2 stack)
+
 DiffToImage
 Perhaps this table resolves the issue. It looks like all of these DiffToImage tables are the same. It gives a list
 of the input ImageMetas. 
 
-Detection
+DiffDetection
 -999 columns. There are several. Perhaps they are things that aren't measured for diffs. Needs more study.
 
+HAF/EAM/KCC need a list
 
 PSPS_SAS39_DO "Diff Object Batch"
@@ -89 +107 @@
 No attempted match to PSPS objects? Sounds compute intensive I guess.
 
--999 columns:
-htmID zoneID cx,cy,cz lamda, beta, l, b, xQfPerfect
-
+EAM/HAF/KCC: the association between diff detection and the big object table is of subjective use (depends on the science case)
+
+-999 columns:
+htmID zoneID cx,cy,cz lamda, beta, l, b,  HAF/EAM/KCC : computed by PSPS
+
+-999 column: xQfPerfect
+HAF/EAM/KCC: should be max qfperfect, look at dvo
 
 PSPS_SAS39_ST "Stack Batch" one per skycell
@@ -105 +127 @@
 StackMeta
 Description of each stack (stackMetaID == stackRun.stack_id)
--999 columns: magSat, competMag, astroScat, photoScat, nAstro, nPhoRef, calibModNum
+-999 columns: magSat, competMag, astroScat, photoScat, nAstro, nPhoRef, 
+
+HAF/KCC/EAM
+ * magsat - we don't calculate it, drop it (stack / detection/ diff)
+ * completMag - detectionThreshold  -->  DETEFF.MAGREF (instrumental mag, needs zp / exp correction  for stack and detection and diff)
+ * astroScat - AST_CDX,  AST_CDY  calc=  sqrt(a^2+b^2) - this is not the astrometric error - a measurement of the calibration but not definitive
+ * photoScat - ZPT_ERR - describe it better: the scatter of the calibration stars
+ * nAstro - NASTRO : change to nRefStars  
+ * nPhoRef - 
+ * calibModNum - HAF to remove from schema
 
 StackObjectThin Magnitudes only. No fluxes