Changes between Version 39 and Version 40 of ppSub_testing_201201

Timestamp:

Feb 13, 2012, 2:01:00 PM (14 years ago)

Author:

Mark Huber

Comment:

--

ppSub_testing_201201

@@ -7 +7 @@
  * is ppSub doing what we think
  * has something changed in the data or what the code is doing
+
 
 General tasks (no particular order and by no means complete, concise or clear):
@@ -18 +19 @@
 
  * wrap up and re-test the convolution direction choice in ppSub (see monitor)
-  * does it still work as it did when tested a few months ago with MD10.V2? [to test for the baseline sample MD04.V3 S-refstk and S-S, sim, 3PI/other(?)]
-  * does it affect the dual convolution [need 3PI sample]
-  * if it chooses to convolved the input, is it poorer (see recent monitoring) -- greater false detections, larger/messy residuals
+  * does it still work as it did when tested a few months ago with MD10.V2? [to test for the baseline sample MD04.V3 S-refstk and S-S, sim]
+  * does it affect the dual convolution [need 3PI/other sample still]
+  * if it chooses to convolve the input, is it poorer (see recent monitoring) with greater false detections, larger/messy residuals
 
  * verify the PSF matching, convolution and diffims - test as expected, self-comparison, cross-comparison (will need translation map for different outputs)
@@ -26 +27 @@
   * forced photometry measurements on sky and selected sources (stats and residuals)
   * return to stamp choices - need a check for "poor" not being rejected
-  * the "no-conv" case - what is limiting ppSub - have many cases of "close" inputs, what are the resulting kernels and output convolution params
+  * the "no-conv" case - what is limiting ppSub -- have many cases of "close" inputs in test sets, what are the resulting kernels and output convolution params
 
  * tracking sources of "extra" false diffim detections 
-  * more use of flags2 and DIFF_* diffim stats - need to map conditions in more detail (see tuning)
-  * 
+  * obviously more use of flags2 and DIFF_* diffim stats -- need to map conditions in more detail (see tuning) as seem to miss flagging the lower level peak/blister residuals (below)
+  * lower level peak/blister residuals -- seem to come and go not always aligned with FWHM (see monitoring and MD04 test sample) and not found often in photpipe (to be tested with test set however)
 
  * monitor new data/reprocessing/tag changes
-  * initially new data as MD04 is ongoing and IQ is improved - convolution direction tests, false detection tests
+  * initially new data as MD04 is ongoing and IQ is improved -- convolution direction tests, false detection tests
   * obviously test changes with ppsub_test
 
- * parameter space/tuning 
+ * parameter space, tuning, adding 
   * kernels (current ppSub using equivalent HOTPANTS, pandromeda pipeline values) and proper scaling -- currently ppSub actually seems mostly insensitive to the kernel params
   * DIFF_xRATIO diffim stats (photpipe vs MT)
+  * values to be added to gpc1 DB and/or the FITS headers (for checking, monitoring)