IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 39 and Version 40 of PSNSC_MOPS


Ignore:
Timestamp:
Feb 6, 2019, 11:20:22 AM (7 years ago)
Author:
Mark Huber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PSNSC_MOPS

    v39 v40  
    6666 *
    6767
    68 masking -- has been shown useful for precovery having the masked pixels not removed from the images by reprocessing with masking turned off (label mehtest.nomask, MASK FALSE in hacked CHIP_MASKTEST)
    69  * overall, masking needs to be re-evaluated as appears to be possibly more aggressive than needed and not use properly in others... -- gpc1 and gpc2 both need thorough static (chip) and dynamic (warp) checking -- recent example o8487g0686o(ota75,05),
    70  * masked pixels should be left in the images or in a separate extension and higher level code use use pixels based on mask values -- removal of pixels at start of process prevents any adjusted use of them later in the processing
    71  * example reprocessing for no mask testing until code changed to leave in all pixels --
     68masking -- has been shown useful for pre/recovery having the masked pixels not removed from the images by reprocessing with masking turned off
     69 * previously was label mehtest.nomask, MASK FALSE in hacked CHIP_MASKTEST --
    7270{{{
    7371chiptool -definebyquery -set_label mehtest.nomask  -set_workdir neb://@HOST@.0/meh/mehtest.nomask -set_data_group mehtest.nomask -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction NOMASKTEST -dbname gpc1 -exp_name XXXXXX
    7472}}}
     73 * new command and config to work on this -- also change to make processing more retained since these are images MOPS makes measurements on to submit to MPC
     74{{{
     75chiptool -definebyquery -set_label mops.nomasktest  -set_workdir neb://@HOST@.0/gpc1/mops.nomasktest -set_data_group mops.nomasktest -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction NOMASKTEST -dbname gpc1 -exp_name XXXXX
     76}}}
     77 * overall, masking needs to be re-evaluated as appears to be possibly more aggressive than needed and not use properly in others... -- gpc1 and gpc2 both need thorough static (chip) and dynamic (warp) checking -- recent example o8487g0686o(ota75,05),
     78 * masked pixels should be left in the images or in a separate extension and higher level code use use pixels based on mask values -- removal of pixels at start of process prevents any adjusted use of them later in the processing
     79
    7580
    7681WS diffims for MOPS --