Community Follow-Up in t he OIR System

1. Community Follow-Up in the OIR System LSST All-Hands Meeting August 14, 2012 Tom Matheson & Steve Ridgway

2. Event Broker • Spectroscopy workshop • Gemini instrumentation

3. NOAO Event Broker ProjectNOAO LSST Working GroupLSST All Hands MeetingAugust 13 - 17, 2012

4. Overview An Event Broker is an automated service that augments a transient/variable alert stream by association of auxiliary information, characterization, classification, and publication with support of filters, detection gates and other services. The motivation for the NOAO project is to guarantee availability to the community of a proven broker service at the time that the LSST survey alert stream begins circa 2022.

5. Current WG Proposal to NOAO Director Event Broker: The objective of the present formulation of the WG project is to prototype essential functionality, to operate the prototype capabilities for near-term science objectives, to develop a scalable architecture, and based on the experience acquired, to develop the requirements for the LSST-scale broker service. Pending resource availability, the second phase of the task will be completed in FY2014.

6. High Level Requirements • For a given area of sky, obtain a time-series of photometric observations of sources in that area. • Execute algorithms on the time series, storing the output of the algorithms. • Visualize the output of the algorithms. • Update the photometric observations when new material becomes available. • Be able to associate external sources of information with the objects.

7. Spectroscopy in the LSST Era • Two-day workshop in Tucson next Spring • Explore the infrastructure and operational modes needed to follow up LSST discoveries • Diverse participation • If you would like to be involved, please let me know

10. What Capabilities Do GeminiUsers Want? Surveys of the US community over the last four years have shown that the greatest demand for Gemini instrumentation is general purpose spectrographs. • Altair Report-2008 (http://www.noao.edu/system/altair/) • Currents Survey-2010 (http://www.noao.edu/currents/200910.html) • System Roadmap Report-2012 (http://ast.noao.edu/about/committees/system-roadmap)

11. Gemini Infra-Red Optical Spectrometer • High-throughput • Single object • Wide-wavelength coverage (near UV to near IR) • Moderate resolution (R ~ 5000) US Gemini Science and Technology Advisory Committee members: Kevin Luhman (Penn State), Tom Matheson (NOAO), Henry Roe (Lowell), Nathan Smith (Arizona)

12. Web Page to Receive Input http://ast.noao.edu/node/197 Please e-mail me if you can’t find this page.

14. Potential GIROS Compromises • Reduce wavelength coverage • Blue cutoff at 400 nanometers • Red cutoff in H band (~ 1800 nanometers) • 360 to 1100 nanometers (OUV optimized, silicon detector only) • 800 to 2500 nanometers (near-IR optimized) • Reduce spectral resolution • R~3500 beyond 1000 nanometers • R~3000, or lower below 1000 nanometers • Fiber-fed, bench-mounted spectrograph • Wholly fiber-fed • Hybrid with some wavelength coverage diverted through fiber Note: Silver mirror dramatically affects throughput below 400 nanometers

15. NSF Proposals 2010: I2-SSI: A Framework for Time-Critical Response to Astrophysical Events Management Plan 2011: SI2-SSI: A Framework for Time-Domain Science: Time-Critical Response to Astrophysical Events Project team: NOAO & LSST staff, Kirk Borne (GMU)

16. Proposed FY13 Milestones • 1. Develop a conceptual design for an LSST-scale broker. • 2. Build functional prototypes for at least two of the following components: • Event generator: From a time-series database, generate a list of events identified by coordinates. • Data amalgamation: For a list of target coordinates, associate specific data from other data bases, as needed for science studies. • Target characterization: Find target coordinates in a characterization space. • 3. Utilize the prototype capability to carry out two science studies: • LSST raw alert rate on stellar variables • Eruptive event identification (identify useful ancillary data)

17. Second Level Requirements - I • Ingest the photometric observations specific to Stripe 82 into a database. • Preserve the catalog parameters of the observations in the database tables. • The photometric time series will be organized to allow frequent analysis of all objects in the database. • The photometric series can be augmented. • Products of analysis algorithms can be associated with objects in the database. • There will be an executive that can: • Accept analysis algorithms in a standard format. • Run the algorithms on a regular or asynchronous basis • Store the results of the algorithms • Accept “filters,” which are higher-level algorithms that work on the output of the analysis algorithms. • Run the filters on a regular basis • Communicate positive filter results.

18. Second Level Requirements - II • 7. User interactions: • Users will be able to load new algorithms and filters. • The system will have a store of algorithms and filters. • The user will be able to visualize and search algorithm and filter products. • The user can specify external sources of information to associate. • 8. Access control: • There will be two levels of access and interaction allowed: • Public, common, or general activities. These will be involve the use of “obvious” or project-endorsed algorithms and filters. The output of these will be made publically available. • Private. Individuals will be able to load algorithms and filters for private use. There will be private database tables to hold the results.