 |
 |
> On Aug 28, 2015, at 2:27 PM, Kian-Tat Lim <[log in to unmask]> wrote: > > Jacek, > >> I think it’d be useful to document this kind of wisdom in one place. Maybe K-T has a suggestion where. Perhaps in DM-3452? > > I think it would be good to document the dataset types produced > by the various Tasks and especially the ones generated by the > transformation framework for ingest into the database. That shouldn't > be (just) in a JIRA issue. Ideally, each Task (or obs_* package for > now) should document its dataset types and metaserv, the SUI/T, and the > schema browser (if still needed given the others) should reuse that > documentation (via pointer or extract) to describe the tables in the > database. > > As to where the "integration deployment" data access Web > services are currently running, that should also be documented, perhaps > on a Confluence page. For now, I think the documentation for the HSC pipeline processing flow is this: https://confluence.lsstcorp.org/display/DM/S15+Multi-Band+Coadd+Processing+Prototype <https://confluence.lsstcorp.org/display/DM/S15+Multi-Band+Coadd+Processing+Prototype> (which has some detail on what the products actually are). I don’t think any measurement transformation was run, as no files in Lauren’s output repo (lsst-dev:/raid/lauren/rerun/LSST/STRIPE82L/v2) match the pattern for https://github.com/lsst/obs_subaru/blob/master/policy/HscMapper.paf#L386 <https://github.com/lsst/obs_subaru/blob/master/policy/HscMapper.paf#L386>. ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1