80 likes | 243 Views
Generic architecture for analyses on calibrated images. Gijs Verdoes Kleijn OmegaCEN Kapteyn Astronomical Institute. Facilitating analysis beyond the calibrated image stage. Analysis software Image differencing: VODIA/OmegaTranS Photometric redshifts: PhotZ
E N D
Generic architecture for analyses on calibrated images Gijs Verdoes Kleijn OmegaCEN Kapteyn Astronomical Institute
Facilitating analysis beyond the calibrated image stage • Analysis software • Image differencing: VODIA/OmegaTranS • Photometric redshifts: PhotZ • Galaxy surface photometry: galfit(/galphot) • Astro-WISE users likely use/develop more in future…… • Goal: • Easy running • Easy exploring input/output • Easy access final results • Method: make new classes which run routine, contain input/output, plus connections to its dependencies. • Status: design ready: presented now for final input
Bi-furcation in kind of analysis • Immediate modelling of image data • galfit, PhotZ, (galphot) • Take input from SourceLists Case A SourceLists Case B • Further manipulation of images first • OmegaTranS/Vodia • Take input from RegriddedFrame RegriddedFrames (,ReducedScienceFrame, CoaddedRegriddedFrame)
Case A: starting from SourceList • Modelling input+output stored in objects which also contain unique model ID, SourceListID (SLID)+SourceID (SID) General parameters: GalPhotModel (config parameters,creation_date,…. SLID,SID,GPID) Why two objects?: practical reason:make post-run searching fast GalPhot run on one galaxy Parameters one ellipse: GalPhotEllipse (r,dr,flux,dflux,… SLID,SID,GPID)
PhotZ example A sourcelist for each filter PhotZ run on one galaxy redshift parameters: PhotZData (z,dz,<z>,… SLID1,SID1,PhotZID) redshift parameters: PhotZData (z,dz,<z>,… SLID2,SID2,PhotZID) redshift parameters: PhotZData (z,dz,<z>,… SLID3,SID3,PhotZID) redshift parameters: PhotZData (z,dz,<z>,… SLID4,SID4,PhotZID) …………………………….. Why copy for each Sourcelist?: practical reason:make-post run searching fast
Case B: starting from frames • Vodia/OmegaTranS: adding points to existing lightcurve VodiaLightCurvePoint Parameters single difference image (ap_phot,err_ap_phot,…. RegriddedFrame1,VodiaID) Vodia runs on one star VodiaLightCurvePoint Parameters single difference image (ap_phot,err_ap_phot,…. RegriddedFrame2,VodiaID) .………………….. VodiaLightCurve: (config,…,[RegriddedFrame1,RegriddedFrame2,…],VodiaID)
Search examples • Give all GalPhotModels for source SID23 in SLID9: awe> q=(GalPhotModel.SLID==SLID9) & (GalPhotModel.SID==SID23) • Give all GalPhotEllipses for source SID23 in SLID9: awe> q=(GalPhotEllipse.SLID==SLID9) & (GalPhotEllipse.SID==SID23) • Give all GalPhotEllipses for GPID=GPID13: awe> q=(GalPhotEllipse.GPID==GPID13) • Give last-made GalPhotModel for source SID23 in SLID9: awe> q=(GalPhotModel.SLID==SLID9) & (GalPhotModel.SID==SID23) awe> lastmodel=q.max(‘GPID’)
Summary • Two kinds of ways to connect analysis on reduced data sources to image data: • Case A: Via SourceLists • Case B: Via Regridded(/Reduced/Coadd) Further add-ons: • Planned:Favorite model flag • Possible: authorname in objects?