Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Introduction

….

Those with ideas for future newsletter items should contact the LSST:UK Project Managers (George Beckett and Terry Sloan: lusc_pm@mlist.is.ed.ac.uk), while everyone is encouraged to subscribe to the Rubin Observatory Digest for more general news from the US observatory team.

Bob Mann


New logo for the Vera C. Rubin Observatory

In early December 2020, the Rubin Observatory unveiled its new logo and explained that the new logo “is a visual representation of Rubin Observatory’s central purpose: to collect light from celestial objects and transform it into data for scientific discovery.”

Terry Sloan


The LSST:UK Community Alert Broker

R. D. Williams, K. W. Smith, G. Francis, A. Lawrence, S. Smartt, D. R. Young, M. Schwamb, C. Frohmaier, and T. Sloan

The LSST survey is focused on the dynamic sky: a source is not just brightness, but a history of brightness. One major product is the “alerts”, that report new sources and changes in brightness. Most observing nights are expected to produce millions of alerts, each perhaps 50 kB, so the data volume per night can be of order a terabyte. For a scientist to get what they want from this firehose, there will be “community brokers” that ingest the data and allow scientists to utilise it effectively. Only a limited number of brokers can be supported – because of the high data rates – so there is a competition. Thus in December 2020 the LSST:UK submitted a proposal to become a community broker.

Our broker is Lasair[1], the main partners being the University of Edinburgh and Queen’s University Belfast (Lasair means flame or flash in Scottish and Irish Gaelic). Although the LSST survey has not started, there is already a prototype transient stream – ZTF – on which we have built the first versions of Lasair. The architecture of the LSST stream will be similar to ZTF.

Lasair will provide a flexible and powerful platform that will enable worldwide users -- individual users, other projects, and citizen science -- to achieve their own science. Lasair will provide access to a rich variety of added value information and external data sources alongside the alert data, all of which can be interrogated, using queries, filters, watchlists, streaming queries and a programming interface. Lasair uses scalable technology and runs on the STFC-funded IRIS infrastructure. Although powerful, Lasair has an easy on-ramp for scientists from  web pages and simple SQL, then on to Jupyter notebooks on their own machines, and then to high-performance mining co-located with the data. Lasair offers direct access with a staged approach: scientists can start with a simple, immediate mechanism using familiar SQL-like languages. These SQL-like queries can be custom made or users can choose and modify one of our pre-built and tested queries. These queries return an initial selection of objects, based on our rich value-added data content, and users can then run their own local code on the results. Users can build up to running  their own code on both the stream and the database with high-throughput resources in the IRIS cloud. The SQL filters and code can be made public, shared with a group of colleagues, copied, modified, and excellent examples and their outputs are featured on the Lasair web page.

A broad overview of the Lasair design is shown in the figure below.

Alerts arrive from the Rubin Observatory at left, and are cached and saved. Several “tagging” systems add value about sky context (Sherlock), external multi-messenger alerts, user-created watchlists of their own sources, classification engines, and featured of the light curves. User queries and filters are processed and results despatched, and the enriched alert stream kept in databases. The alerts can be utilised in several ways: by web, jupyter-style notebook, a programming interface (API), or received as real-time streams.

The Lasair team welcomes astronomers and technologists to have a try at the new (beta) version[1], and report comments and suggestions to lasair-help@lists.roe.ac.uk.

[1] https://lasair-iris.roe.ac.uk/

Roy Williams


DESC Tomographic Challenge

Joe Zuntz



 

Recent LSST:UK outputs

LSST:UK has recently produced the following technical reports.

Title

Author

Description

D3.7.1 Report on optimal metrics for measuring the impact of the LSST pipeline sky subtraction on low-surface-brightness flux at different spatial scales

Aaron Watkins, Chris Collins, Sugata Kaviraj

To expand LSST’s scientific reach into the low surface brightness (LSB) regime, where nearly all of its extragalactic discovery space lies, an accurate sky subtraction is paramount. The current LSST pipeline sky subtraction routine must therefore be optimized for LSB work. The first step in this optimization is to test the current implementation and determine how much improvement is required for LSB work to proceed. This requires the development of metrics for measuring the over-subtraction currently induced by the sky subtraction.

We have devised such a metric using model galaxy injections: the difference in model magnitudes pre- and post-sky subtraction, or Δm. Using this metric, we have tested both the final, local sky subtraction done at the deep coadd level, as well as the full focal plane sky subtraction done to remove night sky emission. While both show systematic over-subtraction below µλ~26 mag/arcsec2 , the final local sky subtraction’s effect is significantly worse, and also shows a trend with model size for high surface brightness models that is absent from the full focal plane sky subtraction. Though these tests only established a baseline, it is already apparent that the final sky subtraction step makes LSB work infeasible with LSST, and even heavily impacts high surface brightness objects with scales larger than 10". In future work, we will expand the parameter space to include more realistic galaxy profiles to determine the full scope of the problem, and then begin devising mitigation strategies.

 

Terry Sloan


 

  • No labels