IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 26 and Version 27 of ppSub_testing_201201


Ignore:
Timestamp:
Feb 1, 2012, 11:27:05 AM (14 years ago)
Author:
Mark Huber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ppSub_testing_201201

    v26 v27  
    33[[PageOutline]]
    44
    5 The primary purpose has been expanded and redirected. While it appeared that the fixed convolution direction may have been the likely cause of an overabundance of false detections from residuals of bright sources in the field, issues in the convolved stack with a resulting larger than selected target PSF has illustrated there may also be issues with the PSF matching/convolution itself.
     5The primary purpose has been expanded and redirected. While it appeared that the fixed convolution direction may have been the likely cause of an overabundance of false detections from residuals of bright sources in the field, issues also in the convolved stack with a resulting larger than selected target PSF has illustrated there may also be issues with the PSF matching/convolution itself.
     6So the scope of testing has been broadened/focused to the PSF matching/convolution
    67
    7  * is the code doing what we want
    8  * is the code doing what we think
     8 * is ppSub doing what we want
     9 * is ppSub doing what we think
    910 * has something changed in the data or what the code is doing
    1011
    1112General tasks (no particular order):
    12  * wrap up and activate the convolution direction choice in ppSub for general use option
     13 * wrap up test and activate the convolution direction choice in ppSub for general use option
    1314 * test and verify the PSF matching/convolution, include the "no-conv" case as well for close matches
    1415 * investigate options for the false detections (may be flags2 use, may be solved with PSF matching or convolution direction)
    … …  
    3738
    3839Branch for originally testing the choice of convolution direction but now full development testing is also updated to r33098 (from 1/11/2012) -- http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/browser/branches/meh_branches/ppsub_test
    39 
    40 
     40 * for convolution direction choice
     41  * normalization updated each direction -- need to look if in path for ppStack fixed, seem to recall modifies even fixed
     42 * for both
     43  * kernel scaling based on
     44 
    4145
    4246= PSF Matching/Convolution =
    … …  
    5761MD04 sample:
    5862
     63Not all seem to be really due to convolving in the wrong direction and need to identify and separate the cases/causes if can. Running samples forced in both direction useful to see.
     64
     65CfA photpipe/HOTPANTs direction: using single template/reference stack so locally get keyword CONVOL00 from header except slight issue with amps. '''All are convolving the TEMPLATE only''' so also suggest issue seems not a convolution direction but convolution issue itself.
     66 * discovered the current photpipe setup is now set to for convolving the template only.. rather then testing both.. argh..
     67
     68
     69Sample diffims with direction forced and detections marked (note both stack-refstack and stack-stack cases). The stack-stack case is the really the only way to test the convolution direction choice now unless go back to the MD04.V2 sample.
     70(easiest to use event stamps from pages, but may want image photpipe diffim..)
     71
     72 * ref - ref
     73 * stk - ref vs ref - stk (both directions)
     74 * stk - stk (both directions)
     75
     76|| '''event (auto direction)''' || '''TARGET2 (convolved ref)''' / '''TARGET1 (convolved stk)''' || '''photpipe automatic (direction)''' || comment ||
     77|| X (TARGET2) || [[Image(test.png,300px)]] || [[Image(test.png,300px)]] (TEMPLATE) || conv refstk better,  ||
     78
     79
     80Photometry/detection comparisons:
     81
     82
    5983Simulated sample:
    6084
    … …  
    6387= Test Sets =
    6488
     89Need tests to verify changes will not break diffims for other surveys (MOPS etc) but do not need to worry about magic now. Not for testing if they will choose the right direction (only if using AUTO), but changes involved part of the normalization and will need to verify doesn't change flux/variance values:
     90 * MD
     91 * simulated image set WW,WS,SS, SSref -- since SSref for MD04 seem to prefer convolving the deeper refstack still, will need to generate
     92 * warp-warp diffim: MD and 3PI TTI
     93 * warp-stack diffim: MD and LAP stack
     94
     95
    6596== MD04 primary samples ==
    6697
    67 Initial test for if choosing the proper direction in stack-stack diffims now using MD04. Was initially done using MD10, but we want to continue to build up test samples over other IPP codes using MD04.
     98Initially selected for if choosing the proper direction in stack-stack diffims now using MD04. Was previously done using MD10, but we want to continue to build up a test set for testing other parts of the IPP and MD04 is a favorite with extensive overlap from other surveys.
    6899
    69100Start with just 2 skycells having example events from last year for photometry comparisons as well - 
    70101
    71 055 --> 077.V2 -- center -
     102skycell.055 (previous tessellations 077) -- near center -
    72103 * http://telescopes.rc.fas.harvard.edu/ps1/alerts2011/2010-C-020101/2010-C-020101.html - AGN@0.345 (xy?)
    73104 * http://telescopes.rc.fas.harvard.edu/ps1/alerts2011/2010-D-030288/2010-D-030288.html - poor sub/var?
    … …  
    79110  * http://telescopes.rc.fas.harvard.edu/ps1/alerts2012/2012-A-350211/2012-A-350211.html - alert
    80111
    81 058 --> 073.V2 -- edge -
     112skycell.058 (previous tessellations 073) -- edge -
    82113 * http://telescopes.rc.fas.harvard.edu/ps1/alerts2011/2010-A-000541/2010-A-000541.html - QSO@2.051
    83114 * http://telescopes.rc.fas.harvard.edu/ps1/alerts2011/2011-B-130093/2011-B-130093.html - A star
    … …  
    88119QUB cross-match page: http://star.pst.qub.ac.uk/ps1/psdb/crossmatchipptocfa/
    89120(add when time.. difficult to search the new crossmatch page..)
     121
     122Difficult to use past examples of wrong convolution direction since refstacks remade, so select sample to just test current choices. The monitoring part should take care of of this in more recent cases as MD04 actively being observed for next couple months.
     123
     124QUB examples of wrong convolution choice:
     125 * http://star.pst.qub.ac.uk/ps1/psdb/userlist/10/
     126 * http://star.pst.qub.ac.uk/ps1/psdb/userlist/5/?sort=-followup_flag_date
     127 * http://star.pst.qub.ac.uk/ps1/psdb/candidate/1095456431022404400/
     128
    90129
    91130Sample nightly stacks for both skycells with same obsdate to look at variation of PSF center and edge (0.25 "/pixel), limited to r-band for now and a sample size that can be manually rerun with some ease.
    … …  
    124163
    125164
    126 Difficult to use past examples of wrong convolution direction since refstacks remade, so select sample to just test current choices.
    127 
    128 QUB examples of wrong convolution choice:
    129  * http://star.pst.qub.ac.uk/ps1/psdb/userlist/10/
    130  * http://star.pst.qub.ac.uk/ps1/psdb/userlist/5/?sort=-followup_flag_date
    131 
    132  * http://star.pst.qub.ac.uk/ps1/psdb/candidate/1095456431022404400/
    133165
    134166
    135 Not all seem to be really due to convolving in the wrong direction and need to identify and separate the cases/causes if can. Running samples forced in both direction useful to see.
    136 
    137 CfA photpipe/HOTPANTs direction: using single template/reference stack so locally get keyword CONVOL00 from header except slight issue with amps. '''All are convolving the TEMPLATE only''' so also suggest issue seems not a convolution direction but convolution issue itself.
    138  * discovered the current photpipe setup is now set to for convolving the template only.. rather then testing both.. argh..
    139 
    140 
    141 Sample diffims with direction forced and detections marked (note both stack-refstack and stack-stack cases). The stack-stack case is the really the only way to test the convolution direction choice now unless go back to the MD04.V2 sample.
    142 (easiest to use event stamps from pages, but may want image photpipe diffim..)
    143 
    144 || '''event (auto direction)''' || '''TARGET2 (convolved ref)''' / '''TARGET1 (convolved stk)''' || '''photpipe automatic (direction)''' || comment ||
    145 || X (TARGET2) || [[Image(test.png,300px)]] || [[Image(test.png,300px)]] (TEMPLATE) || conv refstk better,  ||
    146 
    147 
    148 Photometry/detection comparisons:
    149 
    150 
    151 
    152 === Others Samples (in progress) ===
    153 
    154 Need tests to verify changes will not break diffims for other surveys (MOPS etc) but do not need to worry about magic now. Not for testing if they will choose the right direction (only if using AUTO), but changes involved part of the normalization and will need to verify doesn't change flux/variance values:
    155  * simulated image set WW,WS,SS, SSref -- since SSref for MD04 seem to prefer convolving the deeper refstack still, will need to generate
    156  * warp-warp diffim: MD and 3PI TTI
    157  * warp-stack diffim: MD and LAP stack
     167== Simulated Samples ==
    158168
    159169Simulated image sample: