1 / 4

PD 1.16: SkyAlert – VAO integration study

PD 1.16: SkyAlert – VAO integration study. Matthew J. Graham, Caltech Andrew Drake, Caltech Ashish Mahabal, Caltech Roy Williams (LIGO). Motivation. Transient sources community One of the last frontiers of astronomy, Decadal Review, …

thyra
Télécharger la présentation

PD 1.16: SkyAlert – VAO integration study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PD 1.16: SkyAlert – VAO integration study Matthew J. Graham, Caltech Andrew Drake, Caltech Ashish Mahabal, Caltech Roy Williams (LIGO)

  2. Motivation Transient sources community One of the last frontiers of astronomy, Decadal Review, … CRTS, Fermi/SWIFT, MOA/OGLE, IAUT/CBAT/ATEL, AAVSO, GAIA, LOFAR, SkyMapper, LIGO, LSST, A(SKA)P, … wants robust and reliable tools for working with VOEvents: production, subscription, etc. (VOEventLib) SkyAlert (http://www.skyalert.org) excellent prototype of requested brokering service users use a Web interface to define tasks - messaging, archive retrieval, computation, etc. - that are performed when an appropriate event is received community user base (currently 233 subscribers) independent funding to 2012 VAO Director would like VAO to become clearinghouse for transient events Three birds, one stone need to understand how to align it with VAO requirements

  3. Questions What are the primary requirements for a SkyAlert-type product? Does SkyAlert meet these? Is there any requested/missing functionality? (Some ideas already) Is there functionality that needs to be refactored for improved performance? What is the state of the existing codebase? What are the potential points of failure? What are the potential bottlenecks? How scalable is it? How extensible is it? What are its third-party dependencies? How compatible is it with existing VAO elements? What level of testing is there? What is the status of the existing VOEvent infrastructure? Transport Publishers Repositories Registry What is its operations plan? How well does this integrate with the VAO Operations Plan?

  4. Deliverables Schedule for VAO Year 2/3 integration activities: SkyAlert VOEvent infrastructure Hardware requirements Servers Repositories Risk assessment of integration work Which bits are needed when? External dependencies, e.g., LSST 2012 Data Challenge, GAIA 2013 Real Event Challenge Contingency plan What if…

More Related