Papers › Experience deploying an analysis facility for the Rubin Observatory's Legacy Survey of...

Experience deploying an analysis facility for the Rubin Observatory's Legacy Survey of Space and Time (LSST) data

28 Mar 2024arXiv:2403.19321links table onlyarchive 2025-07-28

Gabriele Mainetti, Fabio Hernandez, Fabrice Jammes, Quentin Le Boulc'h

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

The Vera C. Rubin Observatory is preparing for the execution of the most ambitious astronomical survey ever attempted, the Legacy Survey of Space and Time (LSST). Currently in its final phase of construction in the Andes mountains in Chile and due to start operations in 2025 for 10 years, its 8.4-meter telescope will nightly scan the southern sky and collect images of the entire visible sky every 4 nights using a 3.2 Gigapixel camera, the largest imaging device ever built for astronomy. Automated detection and classification of celestial objects will be performed by sophisticated algorithms on high-resolution images to progressively produce an astronomical catalog eventually composed of 20 billion galaxies and 17 billion stars and their associated physical properties. In this paper, we briefly present the infrastructure deployed at the French Rubin data facility (operated by IN2P3 computing center, CC-IN2P3) to deploy the Rubin Science Platform, a set of web-based services to provide effective and convenient access to LSST data for scientific analysis. We describe the main services of the platform, the components that provide those services and our deployment model. We also present the Kubernetes-based infrastructure we are experimenting with for hosting the LSST astronomical catalog, a petabyte-scale relational database developed for the specific needs of the project.

PaperPDFCode

Code

lsst/qserv-operator officialmentioned in paper report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections