The LIGO Open Science Center (LOSC) fulfills LIGOs commitment to release, archive, and serve LIGO data in a broadly accessible way to the scientific community and to the public, and to provide the information and tools necessary to understand and use
the data. In August 2014, the LOSC published the full dataset from Initial LIGOs S5 run at design sensitivity, the first such large-scale release and a valuable testbed to explore the use of LIGO data by non-LIGO researchers and by the public, and to help teach gravitational-wave data analysis to students across the world. In addition to serving the S5 data, the LOSC web portal (losc.ligo.org) now offers documentation, data-location and data-quality queries, tutorials and example code, and more. We review the mission and plans of the LOSC, focusing on the S5 data release.
Just as the astronomical Time Domain is a catch-phrase for a diverse group of different science objectives involving time-varying phenomena in all astrophysical regimes from the solar system to cosmological scales, so the Virtual Observatory is a com
plex set of community-wide activities from archives to astroinformatics. This workshop touched on some aspects of adapting and developing those semantic and network technologies in order to address transient and time-domain research challenges. It discussed the VOEvent format for representing alerts and reports on celestial transient events, the SkyAlert and ATELstream facilities for distributing these alerts, and the IVOA time-series protocol and time-series tools provided by the VAO. Those tools and infrastructure are available today to address the real-world needs of astronomers.
VOEvent defines the content and meaning of a standard information packet for representing, transmitting, publishing and archiving information about a transient celestial event, with the implication that timely follow-up is of interest. The objective
is to motivate the observation of targets-of-opportunity, to drive robotic telescopes, to trigger archive searches, and to alert the community. VOEvent is focused on the reporting of photon events, but events mediated by disparate phenomena such as neutrinos, gravitational waves, and solar or atmospheric particle bursts may also be reported. Structured data is used, rather than natural language, so that automated systems can effectively interpret VOEvent packets. Each packet may contain zero or more of the who, what, where, when & how of a detected event, but in addition, may contain a hypothesis (a why) regarding the nature of the underlying physical cause of the event. Citations to previous VOEvents may be used to place each event in its correct context. Proper curation is encouraged throughout each events life cycle from discovery through successive follow-ups. VOEvent packets gain persistent identifiers and are typically stored in databases reached via registries. VOEvent packets may therefore reference other packets in various ways. Packets are encouraged to be small and to be processed quickly. This standard does not define a transport layer or the design of clients, repositories, publishers or brokers; it does not cover policy issues such as who can publish, who can build a registry of events, who can subscribe to a particular registry, nor the intellectual property issues.
