Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Topics for discussion:
    • putting ap_* in lsst_distrib
      • would need l1dbproto?  we haven't asked DAX.  John Swinbank got the goahead from Fritz while we were nattering about, but we should ping Andy Salnikov to confirm.
      • if DAX weren't excited to that, Chris adopt his interface to match that of l1dbproto.  but in the meantime should just put ap_association in as is
      • Krzysztof Findeisen to shepherd the process since the ticket is assigned to him.
    • HiTS reprocessing (Meredith Rawls)
      • Meredith Rawls is no longer convinced astrometry is real–some weird 2014 HiTS behavior after just processCcd, even reprocessing using the new matcher.  Unclear if this is a ds9 issue
      • coadds and calexps agree, but have wrong RA/Dec.  no obvious failures in the log
      • working on using stack itself to visualize the visit
      • BestSeeingWcsSelector only selecting ~1 visit in some places; Eric Bellm needs to do the tests to rule this out as an issue...
      • Unknown User (cmorrison) suggests plotting the raws, or even plotting the boundingboxes in python
    • DES processing (Unknown User (emorganson))
    • CI (Krzysztof Findeisen )
    • DCR (Ian Sullivan)
      • having odd results replicating old simulated data.  Could be algorithm or measurement issue.
      • Got new refcats format in place, does not appear to have made a difference.
      • still has NaN PSF fluxes, which requires investigation.  John Swinbank says to look at the flags in output catalog (BASE_PSFFLUX***).  Potentially problem with the mask planes? suggests asking Nate Lust.
      • he's using the InstFlux, so needs to apply the calibration explicitly.  Also maybe sub-bands are being re-calibrated to the g-band refcat, removing some of the signature?  Investigate application of PhotoCalib object
      • uncovered a potential bug with ingestion & default values.
    • ap_* development
      • ap_pipe has few tests.  How can we write bite-sized tests?  Lots of mocks.  Test steps linked in ap_pipe rather than the called components, etc.  Meredith Rawls suggests it as a pair-programming exercise.
      • Unknown User (cmorrison) working on forced photometry
    • revise meeting time?
    • AOB/table round