Changes between Version 38 and Version 39 of ppSub_testing_201201

Timestamp:

Feb 13, 2012, 1:51:19 PM (14 years ago)

Author:

Mark Huber

Comment:

--

ppSub_testing_201201

@@ -8 +8 @@
  * has something changed in the data or what the code is doing
 
-General tasks (no particular order and by no means complete):
+General tasks (no particular order and by no means complete, concise or clear):
  * need to establish a baseline to verify against any past/future changes in code and with reprocessing including a test set of real+simulated images that is '''readily''' inter-comparable (avoid having to pull values from logfiles etc)
   * IPP/ppSub: current ops tag ipp-20111222, branches/meh_branches/ppsub_test [available]
@@ -16 +16 @@
    * sim: for all cases W-W, W-S, S-S, S-refstk [in progress, mostly created from past testing with ppStack but again "bundle"]
    * 3PI/other:  for W-W and W-S cases [still need to select images to use, then "bundle"]
+
  * 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(?)]
-  * if it chooses to convolved the input, is it poorer (see recent monitoring)
+  * 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
+
  * verify the PSF matching, convolution and diffims - test as expected, self-comparison, cross-comparison (will need translation map for different outputs)
   * PSF shape - is it equivalent to the target before convolution and subtraction (is there a scaling/normalization issue?)
@@ -24 +27 @@
   * 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
- * sources of "extra" false diffim detections 
-  * start using of flags2 and DIFF_* diffim stats - need to map conditions in more detail (see tuning)
+
+ * tracking sources of "extra" false diffim detections 
+  * more use of flags2 and DIFF_* diffim stats - need to map conditions in more detail (see tuning)
+  * 
+
  * monitor new data/reprocessing/tag changes
   * 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 
   * kernels (current ppSub using equivalent HOTPANTS, pandromeda pipeline values) and proper scaling -- currently ppSub actually seems mostly insensitive to the kernel params