Changes between Version 91 and Version 92 of ppStack_testing_201111

Timestamp:

Mar 27, 2012, 8:56:44 AM (14 years ago)

Author:

Mark Huber

Comment:

--

ppStack_testing_201111

@@ -381 +381 @@
 }}}
 
-How is the Target seeing FWHM selected to be >7.5 when limited to that on the input images. Are input images not being rejected?  Somewhat part of next section on Target PSF, but need to trace out here. Could split up 400 set into subgroups and run, looks like is not using the rejected but is growing itself in converting to the PSF.MODEL PS_MODEL_PS1_V1?
- * would be helpful to have other stats, at least min/max inputs
+Seems to be a few issues in this larger sample - 
+ * if FWHM cut >7.5 pixels, why is target selected >7.5? Are input images not being rejected?  Somewhat part of next section on Target PSF, but need to trace out here. Could split up 400 set into subgroups and run, looks like rejected are not being used but is growing itself in converting to the PSF.MODEL PS_MODEL_PS1_V1.
  * s055g - rerun in smaller sub-sets ~100, target is ~9.45 and has similar output. Limiting input FWHM <7.1 selects a  target ~8.4. rejection for >7.5 is active.
  * s055r - appears to have a problem, there convolved images are poor and many are rejected. Target PSF is in some way not representative? 100 input subsets seem to not show this problem.
+ * generally would be helpful to have other stats, at least min/max inputs
+
 
 Related to the s055r problem, there may be a problem with excess image rejection: generally ~20-40% are from the >7.5 pixel cut initially
- * will also be cut for input into the unconvolved stacks
+ * Note -- rejected will be cut for input into the unconvolved stacks as well. Even for 058g,i seems a bit higher than would want.
 {{{
 mem400_stack_test.fixtest_s055g/mem400.stats:REJECT_IMAGES    S32       115              # Number of images rejected completely