Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-14935

Thoroughly assess of the effects of turning on "junk suppression" at the visit level


    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: pipe_tasks
    • Labels:
    • Templates:
    • Epic Link:
    • Team:
      Data Release Production


      In RFC-212, we adopted turning on the "junk suppression" temporary local background subtraction by default: SourceDetectionConfig.doTempLocalBackground=True. However, it was later realized that this broke the behavior of the safe clipping coadd assembly (introduced in DM-2915), so the defaults were set back to False in DM-8044.  Given the potential benefits of using "junk suppression" as well as the promise of superior artifact rejection algorithms for in coaddition – see DM-14697 for a detailed report (which, in fact, should not be affected by the setting of this config at the visit level), it is worth revisiting the effects of turning on the junk suppression at the visit level for a large/representative dataset (the HSC RC2 may be sufficient) and whether it should be turned on by default.

      Cautionary note:  regardless of the defaults, we must make it very clear for current and future users of the safe clipping algorithm that it was designed, tuned, and proven to only work properly with no extra background estimations.  Thus, any safe clipping coaddittion should only be performed on visits that were processed with doTempLocalBackground set to False .


      For more details, see the discussions (and demonstrations) in the above mentioned RFC and tickets.


          Issue Links



              • Assignee:
                lauren Lauren MacArthur
                John Swinbank, Lauren MacArthur, Yusra AlSayyad
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created:

                  Summary Panel