SLAC - IPAC meeting at DM AHM 2015-02-10

Date

10 Feb 2015

Data Access Web Services demo

Workflow for non-trivial queries

Say a query is: "return cutouts for all sources matching a given database query, say "select sourceId from Source where sourceId in (123, 444, 567).
Check it applies cleanly to usecase Xiuqin described in DM-1916.

Qserv testing

Terminology

dataset / repo etc
In IPAC archives, dataset always refers to a collection of data.
- For WISE, each data release is a dataset: like preliminary release, allsky release, AllWISE release, ...
- For Spitzer, each legacy or exploration team produce a set of data, they are re leased with each team name or the program name
- Sometimes a dataset includes both catalogs and images; sometimes only catalogs or images in a dataset.
- Inside a dataset, they are further separated into smaller units, sometimes by type (catlog, image, spectrum).
- Images can be further separated by level of data products (level1-single frame image, leve2-coadded image), and by wavelength (wise has 4 bands).
- For each image, there are also ancillary data associated with it, like artifacts, uncertainty, coverage, PSF file, mask, ...
organization of data will affect the REST API when specifying resource. What's repo definition?
Also, "types"
- see DM-1916
- Level = DC, L1, L2, L3, dev
- (Image) Collection = some label (e.g. DR1, DR2, ktl/test20150202)
- (Image) Kind = raw, fpC, deepCoadd, diffim, template, etc.

VO cutout service

http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/caom2ops/examples
the CADC sources are here https://code.google.com/p/opencadc/source/browse/#git%253Fstate%253Dclosed
IPAC team familiar, but not with details, will read up about it
also, Serge wrote image cutout code for IRSA. Discuss all that at the DM-AHM

IPAC table format

API