Changes between Version 67 and Version 68 of ppStack_testing_201111

Timestamp:

Mar 19, 2012, 11:49:15 AM (14 years ago)

Author:

Mark Huber

Comment:

--

ppStack_testing_201111

@@ -24 +24 @@
 
 Other issues:
- * hard limit on number of inputs (solved: descrip to watch for)
- * heavy RAM use
- * change the target PSF FWHM selected 
+ * hard limit on number of inputs (solved: was shell limit )
+ * selection of target PSF FWHM 
+ * heavy RAM use (10-20GB typical for 100+ inputs)
+ * long run-time for 20+ inputs, 400 inputs order 12-14hr (use method similar to psphotStack?)
 
 Branch for testing (currently r32161 from last summer -- '''need to update..''')  -- http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/browser/branches/meh_branches/ppstack_test
@@ -33 +34 @@
  * ppSubMatchPSFs.c has TESTING but not ifdef at start, is a .DEBUG. used to trigger?
 
+All modification tests using updated branch from ipp-20120216 tag (r33407, 3/04/2012) -- ADD testing modifications 
 
 
@@ -261 +263 @@
 
 need to run larger FPA skycell sample, multiple filters of 100, 400 to test stability
+{{{
+mem400_stack_test.fixtest_s055g/mem400.log:      Target seeing FWHM: 10.172999                    
+mem400_stack_test.fixtest_s055i/mem400.log:      Target seeing FWHM: 7.128121                     
+mem400_stack_test.fixtest_s055r/mem400.log:      Target seeing FWHM: 8.744406                     
+mem400_stack_test.fixtest_s055y/mem400.log:      Target seeing FWHM: 8.210619                     
+mem400_stack_test.fixtest_s055z/mem400.log:      Target seeing FWHM: 8.907239                     
+
+mem400_stack_test.fixtest_s055g/mem400.log:        fwhm (psf): 10.278124,10.079561 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s055i/mem400.log:        fwhm (psf): 9.777281,9.695623 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s055r/mem400.log:        fwhm (psf): 11.805278,11.348278 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s055y/mem400.log:        fwhm (psf): 8.573956,8.533222 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s055z/mem400.log:        fwhm (psf): 9.877050,9.810744 (moments): 0.000000,0.000000
+
+
+mem400_stack_test.fixtest_s058g/mem400.log:      Target seeing FWHM: 8.574877                     
+mem400_stack_test.fixtest_s058i/mem400.log:      Target seeing FWHM: 8.097901                     
+mem400_stack_test.fixtest_s058r/mem400.log:      Target seeing FWHM: 7.353693                     
+mem400_stack_test.fixtest_s058y/mem400.log:      Target seeing FWHM: 8.535203                     
+mem400_stack_test.fixtest_s058z/mem400.log:      Target seeing FWHM: 8.813280                     
+
+mem400_stack_test.fixtest_s058g/mem400.log:        fwhm (psf): 8.743460,8.612661 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s058i/mem400.log:        fwhm (psf): 9.086349,9.011602 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s058r/mem400.log:        fwhm (psf): 7.497458,7.397744 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s058y/mem400.log:        fwhm (psf): 8.861631,8.803410 (moments): 0.000000,0.000000
+mem400_stack_test.fixtest_s058z/mem400.log:        fwhm (psf): 9.594481,9.520103 (moments): 0.000000,0.000000
+}}}
+
+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?  
+Split up 400 set into subgroups and ran, looks like is not using the rejected but is growing itself in converting to the PSF.MODEL PS_MODEL_PS1_V1?
+
 
 suspect this is also an issue (minor) with the single convolution diffims as well
-== Target as not worst input image ==
-
-want to look at not setting the convolved stack target PSF based on the worst input.
+
+leads into larger devel need of splitting/carrying the variances through and not dumping into a weight variable so early.
+
+
+----
+
+
+== Target PSF: manually set and as not worst input image ==
+
+want to look at NOT setting the convolved stack target PSF based on the worst input.
 
 have seen cases when the worse inputs are image rejected so in that case not a good idea to use anyways. 
@@ -275 +314 @@
  * will need to make a sample distribution of simulated PSFs, currently sample is flat. revise the making of the stack.mdc list of inputs
 
+=== manually set Target PSF ===
+
+PSF.AUTOSIZE    BOOL    TRUE            # Determine output PSF size from input PSFs?
+PSF.OUTPUT.FWHM F32     5.0             # Target size for output PSF (if not auto-sized)
+
+''NOTE: if wrongly called on command line with a bool -Db PSF.OUTPUT.FWHM 5.0 will silently fail and use the default configuration setting in ppStack.config''
+
+Sim set:
+
+MD04 set:
+ * set target 4.5, selects target seeing PSF to be 5.3. conv PSF grows to 
+ * set target 4.0, selects target seeing PSF to be 4.8. conv PSF grows to 
+
+
+
+----
 
 = Monitor Modifications =
@@ -297 +352 @@
 
 
-