Changes between Version 4 and Version 5 of BillsSas39BatchesNotes

Timestamp:

Aug 25, 2015, 11:12:40 AM (11 years ago)

Author:

heather

Comment:

--

BillsSas39BatchesNotes

@@ -135 +135 @@
  * photoScat - ZPT_ERR - describe it better: the scatter of the calibration stars
  * nAstro - NASTRO : change to nRefStars  
- * nPhoRef - 
+ * nPhoRef - (delete)
+ * add set of similar names  (same information, from relexp/relstack) recalAstroScat, recalPhotoScat, recalNAstroStars, recalNPhotoStars
  * calibModNum - HAF to remove from schema
 
@@ -146 +147 @@
     primary
     bestDetection
-    xInfoFlag2 !!!!!!!!!!! Stack detections very hard to use without this flag!
+    xInfoFlag2 !!!!!!!!!!! Stack detections very hard to use without this flag!  (HAF to investigate, should be value from cmf)
 
 StackObjectAttributes  Fluxes only (in janskys) no magnitudes.
     Has the detection attributes, but not the flags.
+EAM/HAF/KCC counts per seconds, we have zp as well.
+schema description change - forced mean objct is in janskys (can't be in adus)
+everything that is a flux - > reported in a jansky instead of adu - 
+need conversion from adu to jansky from EAM
 
 StackModelFitExtra
@@ -171 +176 @@
 ForcedMeanObject
 -999 columns:
-xGamma
+xGamma  - to be dropped (EAM)
 
 Forced MeanLensing
-xpsfE1 xpsfE2   are -999 
-There is no columns gpsfE1 or gpsfE2 Is this intentional?
+xpsfE1 xpsfE2   are -999  EAM thinks it's being set.
+There is no columns gpsfE1 or gpsfE2 Is this intentional? Not intentional HAF to investigate EAM to investigate
 
 --------------------------------------------------------------------------------------------------
@@ -186 +191 @@
 skycellID has format 1405.07. For consistency with the rest of the schema it should probably be 2 columns
 projectionCell and skycellID
-
+HAF: OK i'll fix it
 
 -999 columns
 photoCalID analVer astroScat photoScat nAstro nPoRef
 
+photoCalID ???
+analVer should be svn number
+astroScat -- drop
+photoScat -- same as in stack
+nAstro -- drop
+nPhoRef -- same as in stack
+
 0 valued columns
-magSat
-completMag
-
+magSat -- drop
+completMag -- as done for stack/p2
+(and grab from relexp (fullforce) info for photoscat/ nphoref)
 
 ForcedWarpMeasurement
@@ -200 +212 @@
 
 -999 columns
-psfLikelihood
+psfLikelihood ( repeat as done for Detections)
 
 ForcedWarpExtended
@@ -211 +223 @@
 ForcedWarpToImage
 -----------------
-what is forcedWarpID ? It doesn't seem to be an ff_id
+what is forcedWarpID ? It doesn't seem to be an ff_id  (HAF: yes, need to add more information)
 imageID is a pointer to the input's ImageMetas (IPP's chipProcessedImfile)
 My comments above on the diff's tables may apply although here I did not see anything that specifies the warp.
 
-Here psModelID is a string PS_MODEL_PS1_V1
-
-
-
-
-
-
+Here psModelID is a string PS_MODEL_PS1_V1 ( HAF: same as other stuff)
+
+
+
+
+