SearcharxivSearch

arXiv subjects

Guy Rixon

Publications and source records attributed to Guy Rixon.

At least 19 recordsLinked to original sources

A free-floating-planet microlensing event caused by a Saturn-mass object

A population of free-floating planets is known from gravitational microlensing surveys. None have a directly measured mass, owing to a degeneracy with the distance, but the population statistics indicate that many are less massive than Jupiter. We report a microlensing event -- KMT-2024-BLG-0792/OGLE-2024-BLG-0516, which was observed from both ground- and space-based telescopes -- that breaks the mass-distance degeneracy. The event was caused by an object with 0.219^{+0.075}_{-0.046} Jupiter masses that is either gravitationally unbound or on a very wide orbit. Through comparison with the statistical properties of other observed microlensing events and predictions from simulations, we infer that this object likely formed in a protoplanetary disk (like a planet), not in isolation (like a brown dwarf), and dynamical processes then ejected it from its birth place, producing a free-floating object.

astro-ph.EP

Preparing for Gaia Searches for Optical Counterparts of Gravitational Wave Events during O4

The discovery of gravitational wave (GW) events and the detection of electromagnetic counterparts from GW170817 has started the era of multimessenger GW astronomy.The field has been developing rapidly and in this paper,we discuss the preparation for detecting these events with the ESA Gaia satellite,during the 4th observing run of the LIGO-Virgo-KAGRA (LVK) collaboration that has started on May 24,2023. Gaia is contributing to the search for GW counterparts by a new transient detection pipeline called GaiaX. In GaiaX, a new source appearing in the field of view of only one of the two telescopes on-board Gaia is sufficient to send out an alert on the possible detection of a new transient. Ahead of O4, an experiment was conducted over a period of about two months. During the two weeks around New Moon in this period of time, the MeerLICHT (ML) telescope located in South Africa tried (weather permitting) to observe the same region of the sky as Gaia within 10 minutes. Any GaiaX detected transient was published publicly. ML and Gaia have similar limiting magnitudes for typical seeing conditions at ML. At the end of the experiment, we had 11861 GaiaX candidate transients and 15806 ML candidate transients, which we further analysed and the results of which are presented in this paper. Finally, we discuss the possibility and capabilities of Gaia contributing to the search for electromagnetic counterparts of gravitational wave events during O4 through the GaiaX detection and alert procedure.

astro-ph.HE

RVS Spectra of Gaia Photometric Science Alerts

Gaia Photometric Science Alerts (GPSA) publishes Gaia G magnitudes and Blue Photometer (BP) and Red Photometer (RP) low-resolution epoch spectra of transient events. 27 high-resolution spectra from Gaia's Radial Velocity Spectrometer (RVS) of 12 GPSAs have also been published. These 27 RVS epoch spectra are presented next to their corresponding BP and RP epoch spectra in a single place for the first time. We also present one new RVS spectrum of a 13th GPSA that could not be published by the GPSA system. Of the 13 GPSA with RVS spectra, five are photometrically classified as unknown, five as supernovae (three as SN Ia, one as SN II, one as SN IIP), one as a cataclysmic variable, one as a binary microlensing event and one as a young stellar object. The five GPSAs classified as unknown are potential scientific opportunities, while all of them are a preview of the epoch RVS spectra that will be published in Gaia's fourth data release.

astro-ph.SR

The fast transient sky with Gaia

The ESA Gaia satellite scans the whole sky with a temporal sampling ranging from seconds and hours to months. Each time a source passes within the Gaia field of view, it moves over 10 CCDs in 45 s and a lightcurve with 4.5 s sampling (the crossing time per CCD) is registered. Given that the 4.5 s sampling represents a virtually unexplored parameter space in optical time domain astronomy, this data set potentially provides a unique opportunity to open up the fast transient sky. We present a method to start mining the wealth of information in the per CCD Gaia data. We perform extensive data filtering to eliminate known on-board and data processing artefacts, and present a statistical method to identify sources that show transient brightness variations on ~2 hours timescales. We illustrate that by using the Gaia photometric CCD measurements, we can detect transient brightness variations down to an amplitude of 0.3 mag on timescales ranging from 15 seconds to several hours. We search an area of ~23.5 square degrees on the sky, and find four strong candidate fast transients. Two candidates are tentatively classified as flares on M-dwarf stars, while one is probably a flare on a giant star and one potentially a flare on a solar type star. These classifications are based on archival data and the timescales involved. We argue that the method presented here can be added to the existing Gaia Science Alerts infrastructure for the near real-time public dissemination of fast transient events.

astro-ph.SR

IVOA Recommendation: SSO - Single-Sign-On Profile: Authentication Mechanisms Version 2.0

Approved client-server authentication mechanisms are described for the IVOA single-sign-on profile: No Authentication; HTTP Basic Authentication; TLS with passwords; TLS with client certificates; Cookies; Open Authentication; Security Assertion Markup Language; OpenID. Normative rules are given for the implementation of these mechanisms, mainly by reference to pre-existing standards. The Authorization mechanisms are out of the scope of this document.

astro-ph.IM

IVOA recommendation: VOSpace specification v2.0

VOSpace is the IVOA interface to distributed storage. This specification presents the first RESTful version of the interface, which is functionally equivalent to the SOAP-based VOSpace 1.1 specification. Note that all prior VOSpace clients will not work with this new version of the interface.

astro-ph.IM

IVOA Recommendation: StandardsRegExt: a VOResource Schema Extension for Describing IVOA Standards

This document describes an XML encoding standard for metadata about IVOA standards themselves, referred to as StandardsRegExt. It is intended to allow for the discovery of a standard via an IVOA identifier that refers to the standard. It also allows one to define concepts that are defined by the standard which can themselves be referred to via an IVOA identifier (augmented with a URL fragment identifier). Finally, it can also provide a machine interpretable description of a standard service interface. We describe the general model for the schema and explain its intended use by interoperable registries for discovering resources.

astro-ph.IM

IVOA Recommendation: TAPRegExt: a VOResource Schema Extension for Describing TAP Services

This document describes an XML encoding standard for metadata about services implementing the table access protocol TAP [TAP], referred to as TAPRegExt. Instance documents are part of the service's registry record or can be obtained from the service itself. They deliver information to both humans and software on the languages, output formats, and upload methods supported by the service, as well as data models implemented by the exposed tables, optional language features, and certain limits enforced by the service.

astro-ph.IM

IVOA Recommendation: IVOA Support Interfaces

This document describes the minimum interface that a (SOAP- or REST-based) web service requires to participate in the IVOA. Note that this is not required of standard VO services developed prior to this specification, although uptake is strongly encouraged on any subsequent revision. All new standard VO services, however, must feature a VOSI-compliant interface. This document has been produced by the Grid and Web Services Working Group. It has been reviewed by IVOA Members and other interested parties, and has been endorsed by the IVOA Executive Committee as an IVOA Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. IVOA's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability inside the Astronomical Community.

astro-ph.IM

IVOA Recommendation: VOSpace specification Version 1.15

VOSpace is the IVOA interface to distributed storage. This version extends the existing VOSpace 1.0 (SOAP-based) specification to support containers, links between individual VOSpace instances, third party APIs, and a find mechanism. Note, however, that VOSpace-1.0 compatible clients will not work with this new version of the interface.

astro-ph.IM

IVOA Recommendation: An IVOA Standard for Unified Content Descriptors Version 1.1

This document describes the current understanding of the IVOA controlled vocabulary for describing astronomical data quantities, called Unified Content Descriptors (UCDs). The present document defines a new standard (named UCD1+) improving the first generation of UCDs (hereafter UCD1). The basic idea is to adopt a new syntax and vocabulary requiring little effort for people to adapt softwares already using UCD1. This document also addresses the questions of maintenance and evolution of the UCD1+. Examples of use cases within the VO, and tools for using UCD1+ are also described.

astro-ph.IM

IVOA Recommendation: Maintenance of the list of UCD words Version 1.20

According to what is stated in the IVOA Recommendation "An IVOA standard for Unified Content Descriptors", a procedural document should be created in order to maintain (add, change, suppress words) the standard list of UCD1+ words "The UCD1+ Controlled Vocabulary". This document describes the procedure to maintain the standard list of UCD1+ words.

astro-ph.IM

IVOA Recommendation: The UCD1+ controlled vocabulary Version 1.23

This document describes the list of controlled terms used to build the Unified Content Descriptors, Version 1+ (UCD1+). The document describing the UCD1+ can be found at the URL: http://www.ivoa.net/Documents/latest/UCD.html. This document reviews the structure of the UCD1+ and presents the current vocabulary.

astro-ph.IM

IVOA Recommendation: IVOA Single-Sign-On Profile: Authentication Mechanisms Version 1.01

Approved client-server authentication mechanisms are described for the IVOA single-sign-on profile: digital signatures (for SOAP services); TLS with passwords (for user sign-on points); TLS with client certificates (for everything else). Normative rules are given for the implementation of these mechanisms, mainly by reference to pre-existing standards.

astro-ph.IM

IVOA Recommendation: VOResource: an XML Encoding Schema for Resource Metadata Version 1.03

This document describes an XML encoding standard for IVOA Resource Metadata, referred to as VOResource. This schema is primarily intended to support interoperable registries used for discovering resources; however, any application that needs to describe resources may use this schema. In this document, we define the types and elements that make up the schema as representations of metadata terms defined in the IVOA standard, Resource Metadata for the Virtual Observatory [Hanicsh et al. 2004]. We also describe the general model for the schema and explain how it may be extended to add new metadata terms and describe more specific types of resources.

astro-ph.IM

IVOA Recommendation: IVOA Registry Interfaces Version 1.0

Registries provide a mechanism with which VO applications can discover and select resources--e.g. data and services--that are relevant for a particular scientific problem. This specification defines the interfaces that support interactions between applications and registries as well as between the registries themselves. It is based on a general, distributed model composed of so-called searchable and publishing registries. The specification has two main components: an interface for searching and an interface for harvesting. All interfaces are defined by a standard Web Service Description Language (WSDL) document; however, harvesting is also supported through the existing Open Archives Initiative Protocol for Metadata Harvesting, defined as an HTTP REST interface. Finally, this specification details the metadata used to describe registries themselves as resources using an extension of the VOResource metadata schema.

astro-ph.IM

IVOA Recommendation: IVOA Credential Delegation Protocol Version 1.0

The credential delegation protocol allows a client program to delegate a user's credentials to a service such that that service may make requests of other services in the name of that user. The protocol defines a REST service that works alongside other IVO services to enable such a delegation in a secure manner. In addition to defining the specifics of the service protocol, this document describes how a delegation service is registered in an IVOA registry along with the services it supports. The specification also explains how one can determine from a service registration that it requires the use of a supporting delegation service.

astro-ph.IM

IVOA Recommendation: Table Access Protocol Version 1.0

The table access protocol (TAP) defines a service protocol for accessing general table data, including astronomical catalogs as well as general database tables. Access is provided for both database and table metadata as well as for actual table data. This version of the protocol includes support for multiple query languages, including queries specified using the Astronomical Data Query Language (ADQL [1]) and the Parameterised Query Language (PQL, under development) within an integrated interface. It also includes support for both synchronous and asynchronous queries. Special support is provided for spatially indexed queries using the spatial extensions in ADQL. A multi-position query capability permits queries against an arbitrarily large list of astronomical targets, providing a simple spatial cross-matching capability. More sophisticated distributed cross-matching capabilities are possible by orchestrating a distributed query across multiple TAP services.

astro-ph.IM