IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 152 and Version 153 of ppStack_testing_201111


Ignore:
Timestamp:
Jun 28, 2012, 3:50:19 PM (14 years ago)
Author:
Mark Huber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ppStack_testing_201111

    v152 v153  
    788788  * PSF model choices?
    789789=== Case 0: Improved Cuts/Limits ===
    790 
    791 
     790Possible preliminary improvement:
     791 
     792Sample summary of past LAP run stacks ~mhuber/lapstack20120510_inputtargetpsffwhm.log
     793
     794past/current ppStack.config for STACK_THREEPI:
     795 * PSF.INPUT.MAX  12.0 -- anything >12 pixels excluded (3")
     796* PSF.INPUT.CLIP.NSIGMA  NAN -- not used, but would redefine the INPUT.MAX to be clipped_mean + NSIGMA*clipped_stdev
     797
     798proposed:
     799* PSF.INPUT.MAX 8.0 (or 2", MD deep stack is set for 7.5)
     800* PSF.INPUT.CLIP.NSIGMA 2.0 (or 1.0?)
     801
     802Chris quickly looked at the FWHM of the exposures going into LAP stacks and order 90 percentile are <8 pixels. The NSIGMA is more difficult to quantify, so the general question is do we want to just help trim off more of the poorest inputs to keep the convolved target PSF more regular or be much more restrictive to improve the convolved target PSF at the cost of the number of inputs (maybe 10-30% at times for NSIGMA of 1). Any additional exclusion cuts include images that go into making the unconvolved stack as well.
     803
     804Adding pass cases for limits on the different minimum number of inputs would require some task modifications in LAP (and nightly science).
    792805=== Case 1: Initial Manually Set Target as Simple Model PSF (include FWHM) ===
    793806To explore the implications of (de)convolving to a simple PSF model with simtest and MD data