Summary of MOPS_dualconv_test130530

MOPS has noted often in the past of poor convolution in diffims producing large numbers of false-detections. This has been traced back to always being the case when dual convolution (both input warps being convolved to a target PSF) when single convolution should have sufficed.

Larry suggested a couple chunks for comparison testing with the option for dual convolution being turn off and published to IPP-MOPS-TEST2

• night 6370
• 162.3PI.00.ANW2.J.g
• 162.3PI.00.ANW2.J.r

Reprocessing details -- started on 20130531

• gpc1db warp label, data_group -- meh_mopstest3pi130531_nodual, OSS.20130319 (unchanged)
• gpc1db diff label, data_group -- meh_mopstest3pi20130319_130531nodual, OSS.20130319
• gpc1db publishing label meh_mopstest3pi20130319_130531nodual
• gpc1db publish_id range: 817778--817813 (all inclusive)
• datastore time registered starting 2013-06-03T22:44:51Z

These were also from the OSS.20130319 night used for the comparison of MOPS diffim discoveries to IASC visual chip inspection for OSS.20130319 (MOPS_IASC20130319_tests130422)

More will be added to this page as time allows.

• summary for is dual convolution ever needed
• Larry also sent a know source list for the g-band, looking at the matched lists in more detail

Related summary pages:

• MOPS_IASC20130319_tests130422 -- has been key page for setting up examples and identifying problems
• MOPS_depthloss_test130715
• MD_WSdiffim_photcheck_test20121004
• ppSub_testing_201201
• MOPS_diff_false_positives