Transient Name Server

Transient Name Server
Name	Transient Name Server
Abbreviation	TNS
Type	scientific registry
Established	2016
Discipline	astronomy
Country	International
Hosted by	University of Edinburgh

Transient Name Server The Transient Name Server is an international registry for astronomical transient names used by observatories, surveys, and research institutions to coordinate discovery designations and follow-up observations. It functions alongside observatories and missions such as European Southern Observatory, National Aeronautics and Space Administration, European Space Agency, Max Planck Society, and National Science Foundation to standardize transient nomenclature across programs like Zwicky Transient Facility, All-Sky Automated Survey for SuperNovae, Pan-STARRS, Vera C. Rubin Observatory, and Sloan Digital Sky Survey.

Overview

The service provides a centralized system for assigning provisional and official identifiers that link discoveries by projects such as Catalina Sky Survey, ASAS-SN, Gaia (spacecraft), Kepler (spacecraft), TESS, and Fermi Gamma-ray Space Telescope to follow-up facilities such as Gemini Observatory, Keck Observatory, Subaru Telescope, Very Large Telescope, and Atacama Large Millimeter Array. It integrates with data centers like Centre de Données astronomiques de Strasbourg, NASA/IPAC, Space Telescope Science Institute, European Southern Observatory Science Archive Facility, and archives used by collaborations including LIGO Scientific Collaboration, IceCube Neutrino Observatory, High Energy Stereoscopic System, and Cherenkov Telescope Array.

History and Development

The registry was developed in response to coordination needs identified by time-domain projects such as Palomar Transient Factory, Intermediate Palomar Transient Factory, Zwicky Transient Facility, and community workshops hosted by organizations like International Astronomical Union, Royal Astronomical Society, American Astronomical Society, and International Science Council. Initial design and deployment involved teams from University of Edinburgh, University of California, Berkeley, California Institute of Technology, Space Telescope Science Institute, Max Planck Institute for Astronomy, and European Southern Observatory. Funding and support sources included Science and Technology Facilities Council, National Science Foundation, European Research Council, and philanthropic partners such as Gordon and Betty Moore Foundation and Simons Foundation.

Operation and Architecture

The infrastructure uses identifiers compatible with registries and protocols adopted by International Astronomical Union committees and observatory networks such as Transient Name Server-aware brokers and services in the ecosystem including ANTARES (broker), SkyAlert, Las Cumbres Observatory, AMPEL, and Lasair. Backend components run on cloud and institutional resources provided by partners including Amazon Web Services, Google Cloud Platform, European Grid Infrastructure, and university clusters at University of Edinburgh and University of Cambridge. Software development practices follow models used in projects like Astropy, SIP (Software Infrastructure Projects), VOEvent, and Virtual Observatory standards, with continuous integration workflows influenced by GitHub, GitLab, and Travis CI.

Data Submission and Naming Conventions

Submitters from surveys such as Pan-STARRS, Zwicky Transient Facility, ASAS-SN, ATLAS (survey), and Gaia (spacecraft) register candidates via web forms or programmatic APIs modeled after protocols used by Virtual Observatory, VOEvent Protocol, and archives at Centre de Données astronomiques de Strasbourg. Naming rules align with recommendations from International Astronomical Union working groups and mirror conventions found in catalogs like Minor Planet Center and SIMBAD, while cross-matching uses services from VizieR, NASA Exoplanet Archive, and HEASARC. The system issues provisional names, coordinates, discovery timestamps, and attribution metadata consistent with citation practices in journals such as The Astrophysical Journal, Monthly Notices of the Royal Astronomical Society, and Astronomy & Astrophysics.

Usage and Applications

Researchers from institutions including Harvard-Smithsonian Center for Astrophysics, Princeton University, Massachusetts Institute of Technology, Carnegie Institution for Science, University of Tokyo, and Peking University use the registry to coordinate spectroscopic follow-up at facilities like Magellan Telescopes, Large Binocular Telescope, SOAR Telescope, and NOIRLab observatories. Time-domain science enabled involves work on supernovae studied by teams behind SNfactory, SuperNova Legacy Survey, and Pan-STARRS1 Medium Deep Survey; tidal disruption events linked to groups at University of Oxford and University of California, Berkeley; kilonova searches coordinated with LIGO Scientific Collaboration and Virgo (detector); and counterpart localization for Fermi Gamma-ray Space Telescope and IceCube Neutrino Observatory alerts.

Governance, Policies, and Access

Operational governance involves stakeholders from organizations such as International Astronomical Union, American Astronomical Society, European Southern Observatory, Space Telescope Science Institute, and funding bodies like National Science Foundation and European Research Council. Policies on naming priority, attribution, embargoes, and dispute resolution reflect practices codified by committees resembling those at International Astronomical Union and are informed by agreements among survey consortia including Zwicky Transient Facility, Pan-STARRS, LSST Project, and Gaia Consortium. Access tiers mirror data policies seen at NASA, ESA, and national observatories, with APIs and user accounts provided to professional teams and vetted facilities.

Limitations and Challenges

Challenges include scale and rate issues comparable to those faced by Vera C. Rubin Observatory and Zwicky Transient Facility, interoperability complexities similar to Virtual Observatory efforts, and governance tensions akin to debates at International Astronomical Union and American Astronomical Society meetings. Technical constraints involve cross-matching performance against catalogs like Gaia Data Release 3, Pan-STARRS Data Release, and SDSS; data quality heterogeneity among contributors such as ASAS-SN and ATLAS (survey); and allocation of resources from cloud providers like Amazon Web Services and infrastructures like European Grid Infrastructure. Social and policy hurdles echo disputes in collaborations such as LIGO Scientific Collaboration and Event Horizon Telescope over credit, embargoes, and rapid communication.

Category:Astronomical catalogues