Attendees: Colin, Mario, Simon, Dominique F., Hsin-Fang, Gruendl, Juan, MWV, Angelo, David
- Measurement on difference images. Fixed bugs preventing to get measurements, now able to quantify detections as function of magnitude, etc
- Action Item: Include link to results in verification wiki
- Tired to loop over src FITS catalogs, used daf_ingest to set up a mysql database and running queries again lsst10 improved analysis a lot. ingestProcessed.py should be used for metadata, where is it?
- Action item: Talk with Jacek or Serge about database access. See discussion on community about the need of having the visit and ccd metadata in addition to the src table.
- Results: many detections of probable “noise”. Noise model is wrong, off by ~15%, CP noise model issue. Distribution of im1-im2/variance is too wide.
- Plan to proceed? Try our own ISR from raw images and see how good our noise model is. MWV suggested a generic test of noise model.
- Gave talk at AAS, good summary of what we have done so far (http://zenodo.org/record/44673)
- COSMOS data: taking the src catalog from each ccd, matched sources between visits. Which matching method from stack should use? R:
import lsst.afw.table as afwTable match = afwTable.matchRaDec(srcRef, srcVis, afwGeom.Angle(1, afwGeom.arcseconds))
- src cat from individual ccds and visits, how to preserve the match result and original visit result?
- Need of a multi-band matcher (in progress)
- Changed strategy and focus on ProcessCdd to understand better each step and progress on QA
- CFHT astrometry checks see
- Median value of astrometric scatter (from the positions recorded by the pipeline) is 23 mas (mag < 21). Checks internal astrometry between visits.
- demo running check-astrometry on different output data repositories
- COSMOS DECam large astrometric scatter (>200 mas), probably CP WCS issue
- Colin: good design choice, small datasets and small pieces of code
- Mario: suggests to look into
pipeQA, it has two components test (?)
pipeQAthat runs on a given data repository (it should handle any obs package) and display
pipeQAwhich produce the plots. Which parts of the framework can bre reused?
Action item: Mario send presentations and references on
- Will it work with SQuaSH?
- David: Simultaneous astrometry. JimB and Dominque B. talked about what’s needed to bring simulateous astrometry
- UW is planing to do this in this cycle, @parejkoj is leading the effort to bring HSC code (simultaneous photometric solution) over
- Action Item: David look into the that first and contact @parejkoj to see how to include Dominiques code. Set up a phone conf week from Tuesday. See also https://jira.lsstcorp.org/browse/RFC-123
- successfuly run 3 bands coadd through DRP, results look reasonable, next ingest variable sources
- updated online cookbook here: https://github.com/DarkEnergyScienceCollaboration/Twinkles/blob/master/code/twinkles_cookbook.md
- lower floor 1% in g, 0.6% r and i - what is causing the residual systematic floor?
- check aperture photometry
- Looking at the astrometry matcher failures, see examples at https://confluence.lsstcorp.org/display/SQRE/Bulge+Survey+Processing
- Using default configuration, maximum offset 3 arcsec, might turn that up (
calibrate.astrometry.matcher.maxMatchDistArcSec = 3.0)
- two solvers, default matcher requires you to be close while astrometry.net can solve blind option
- minimum matching number of pairs looks ok (
calibrate.astrometry.matcher.minMatchedPairs = 30)
- not on
- not on
- Joachim Moeyens has run MOPS on test datasets, got it run all the way through to tracks, only works on his Mac, produces garbage on linux, maybe memory issues, working on it
- introduced Juan Pablo Gomez, working on CFHT images