) Low-latency Gravitational-wave Alerts for Multimessenger Astronomy during the Second Advanced LIGO and Virgo Observing Run

Advanced LIGO ’ s second observing run ( O2 ) , conducted from 2016 November 30 to 2017 August 25, combined with Advanced Virgo ’ s ﬁ rst observations in 2017 August, witnessed the birth of gravitational-wave multimessenger astronomy. The ﬁ rst ever gravitational-wave detection from the coalescence of two neutron stars, GW170817, and its gamma-ray counterpart, GRB 170817A, led to an electromagnetic follow-up of the event at an unprecedented scale. Several teams from across the world searched for EM / neutrino counterparts to GW170817, paving the way for the discovery of optical, X-ray, and radio counterparts. In this article, we describe the online identi ﬁ cation of gravitational-wave transients and the distribution of gravitational-wave alerts by the LIGO and Virgo collaborations during O2. We also describe the gravitational-wave observables that were sent in the alerts to enable searches for their counterparts. Finally, we give an overview of the online candidate alerts shared with observing partners during O2. Alerts were issued for 14 candidates, 6 of which have been con ﬁ rmed as gravitational-wave events associated with the merger of black holes or neutron stars. Of the 14 alerts, 8 were issued less than an hour after data acquisition.


INTRODUCTION
Gravitational-wave (GW) multi-messenger astronomy provides a unique view of the cosmos.In this paper, we explain the procedures used during the second observing run of the advanced ground-based gravitational-wavedetector network to issue alerts for multi-messenger follow-up.We also include a summary of all alerts issued to observing partners and an update on the status of candidate events.
The Advanced Laser Interferometer Gravitationalwave Observatory (LIGO) detectors (Abbott et al. 2015) are installed in the US at Hanford, WA and Livingston, LA while the Advanced Virgo detector (Acernese et al. 2015) is located in Cascina, Italy near Pisa.The detectors use a modified Michelson laser interferometer design to measure GW strain.A passing GW causes a differential length change in the detector arms, producing interference of the laser beams at the beam splitter, and giving an optical readout proportional to the GW strain.
In September 2015 the two Advanced LIGO detectors began their first observing run (O1), lasting four months.The first direct detection of gravitational waves, GW150914, from the coalescence of binary black holes (BBH; Abbott et al. 2016b) marked the beginning of gravitational-wave (GW) astronomy.Two additional BBH merger signals, GW1510121 (Abbott et al. 2016c) and GW151226 (Abbott et al. 2016d), were identified before the end of O1.Following hardware and software upgrades, the second Advanced LIGO observing run (O2) began on 30 November 2016.Advanced Virgo joined the network in August 2017 for the last month of data acquisition.
A number of additional BBH coalescences were detected in O2 (see Abbott et al. 2017aAbbott et al. ,b,c, 2018a)).Furthermore, on August 17, 2017, at 12:41:04 UTC a binary neutron star (BNS) inspiral signal (GW170817) was observed (Abbott et al. 2017d).Less than two seconds later, the short gamma-ray burst (sGRB) GRB 170817A was detected by two space-based instruments: the Gamma-ray Burst Monitor (GBM) onboard Fermi (Goldstein et al. 2017), and the spectrometer anticoincidence shield (SPI-ACS) onboard INTEGRAL (Savchenko et al. 2017).This joint observation provided the first direct evidence that at least a fraction of sGRBs have a BNS system as progenitor, as predicted by Eichler et al. 1989;Paczynski 1986Paczynski , 1991.Short (Hirata et al. 1987) and the Irvine-Michigan-Brookhaven (Bionta et al. 1987) neutrino detectors, a few hours before its optical counterpart was discovered.In addition, GRBs and SNe are expected to produce relativistic outflows in which particles (protons and nuclei) can be accelerated and produce high-energy neutrinos by interacting with the surrounding medium and radiation (see, e.g., Murase 2018).
One further class of transient GW sources are magnetars, i.e., rotating NSs with very intense magnetic fields (∼ 10 15 G).Theoretical models predict that when these stars undergo starquakes, asymmetric strains can temporarily alter the geometry of the star and GWs could be emitted (see, e.g., Corsi & Owen 2011).Electromagnetic phenomena possibly associated with magnetar starquakes include Soft Gamma Repeaters (SGRs) and Anomalous X-ray Pulsars (AXPs), sources that sporadically emit short bursts of gamma-rays and X-rays (see Mereghetti 2008 for a review).Starquakes can also cause radio/X-ray pulsar glitches: sudden increases in the rotational frequency of a highly magnetized, rotating NS (pulsar) followed by exponential decays, which bring the pulsar rotational frequency back down to its initial value (see, e.g., Espinoza et al. 2011).
During O1 and O2, extensive EM observing campaigns searched for counterparts to GW candidates identified in low-latency.Significant improvements were made between these two observing runs regarding the data analysis software and source modeling, allowing important additional information to be distributed in low-latency during O2.For CBC events, 3D sky localization maps were released, providing information about the direction and the luminosity distance of the source (Singer et al. 2016a), while in O1, only 2D sky localization maps were provided, without distance information.During O2, probabilities that at least one lowmass object was present in the coalescing binary system and that tidally disrupted material formed a massive accretion disk around the merged object were reported.This information is useful in assessing the likelihood that a merger could power an EM transient (Foucart 2012;Pannarale & Ohme 2014).
During O1 and the first part of O2, with the GW network formed only by the two Advanced LIGO interferometers, sources were typically localized in sky areas ranging from a few hundreds to several thousands of square degrees (see, e.g., Abbott et al. 2016e,d, 2017a.Improvements in localization areas were made since Advanced Virgo joined the gravitational-wave detector network starting August 1, 2017.For instance, GW170814 and GW170817 were localized by the three detector net-work within a few tens of square degrees, see Abbott et al. 2017b,d.Jointly observing the same event in both gravitational waves and electromagnetic radiation provides complementary insights into the progenitor and its local environment.The GW signal is key to determining several physical properties of the source such as the masses and system properties (inclination, orientation, spin, etc.).The EM counterpart provides information about radioactive decay, shocks, the emission mechanism of the central engine, magnetic fields, beaming and also probes the surrounding environment of the source (see for instance Berger 2014).The detection of an EM counterpart also can give precise localization and lead to the identification of the host galaxy of the source.The distance estimated from the GW data combined with the measured redshift of the host galaxy enables measurement of the Hubble constant (Schutz 1986;Holz & Hughes 2005;Nissanke et al. 2010Nissanke et al. , 2013a;;Abbott et al. 2017f;Seto & Kyutoku 2018;Hotokezaka et al. 2018;Vitale & Chen 2018).Precise measurements of the host galaxy distance and the binary inclination given by the EM observations can be used to reduce the degeneracy in the GW parameter estimation (see, e.g., Guidorzi et al. 2017;Cantiello et al. 2018;Mandel 2018;Chen et al. 2018).Furthermore, the detection of an EM counterpart may increase the confidence in the astrophysical origin of a weak GW signal (Kochanek & Piran 1993).It also provides constraints on the relative merger rates of the two classes of compact binaries (BNS and NS-BH), on the beaming angle of sGRBs, and the NS equation of state (Abadie et al. 2010;Chen & Holz 2013;Pannarale & Ohme 2014;Clark et al. 2015;Dominik et al. 2015;Regimbau et al. 2015;Siellez et al. 2016;Radice et al. 2018).Finally, joint GW and EM observations can provide constraints on fundamental physics (Abbott et al. 2017g).
In this paper, we describe the identification of GW transients and the distribution of GW alerts performed during O2 by the LIGO and Virgo collaborations.We also detail the GW event information shared with the astronomy community and give an overview of the EM follow-up strategies.
In section 2 we present an overview of the online GW analysis, with a description of the online analysis detection pipelines, the vetting and the approval processes for potential GW events.In section 3 we summarize the GW alerts that were distributed during O2 and the properties of the gravitational wave candidates after the offline analysis.We describe the information that was shared with astronomers including how this was used during the electromagnetic/neutrino follow-up activities.Finally, in section 4 we present our conclusions.

ONLINE GRAVITATIONAL WAVE ANALYSIS
In this section, we describe the two classes of searches for GW transients, modeled and unmodeled, that contributed triggers for low-latency EM follow-up (in section 2.1).We also present the full vetting and validation process of candidate events (in section 2.2) and distribution of low-latency alerts during O2 (in section 2.3).Offline search pipelines2 also led to the identification of additional candidate events GW170729 and GW170818 (see Abbott et al. 2018a).

Brief description of online pipelines
The modeled (CBC) searches specifically look for signals from compact binary mergers of neutron stars and black holes (BNS, NS-BH, and BBH systems).The unmodeled (burst) searches on the other hand, are capable of detecting signals from a wide variety of astrophysical sources in addition to compact binary mergers: core-collapse of massive stars, magnetar starquakes, and more speculative sources such as intersecting cosmic strings or as-yet unknown GW sources.

Online modeled searches
GstLAL (Messick et al. 2017), MBTAOnline (Multi-Band Template Analysis, Adams et al. 2016) and Py-CBC Live (Nitz et al. 2018) are analysis pipelines designed to detect and report compact binary merger events with sub-minute latencies.Such pipelines use discrete banks of waveform templates to cover the target parameter space of compact binaries and perform matched filtering on the data using those templates, similar to the offline analyses (Usman et al. 2016;Messick et al. 2017) that produced the O1 and O2 catalog of compact binaries (Abbott et al. 2018a).The online and offline analyses differ in various ways.The most important configuration choices of online analyses are reviewed here.
The mass and spin parameter space considered by the online pipelines in O2 is summarized in Table 1.All pipelines assume that, while the gravitational wave signal dwells in the detector sensitive band, the spins of the compact objects are aligned or antialigned with the orbital angular momentum, and that orbital eccentricity is negligible.Additional details of the PyCBC Live and GstLAL banks can be found in Dal Canton & Harry 2017 and Mukherjee et al. 2018, respectively.In the case of PyCBC Live, the online and final offline analyses covered exactly the same space.For GstLAL, the offline bank extended to a larger total mass of 400M .
A matched-filtering analysis is performed by each pipeline, producing triggers for each detector's data stream whenever the matched-filter single-detector signal to noise ratio (SNR) peaks above a threshold given in Table 1.Due to the small probability of a signal being detectable in Virgo and not in LIGO during O2, PyCBC Live did not use Virgo to produce triggers; Virgo's data was nevertheless still analyzed and used for the sky localization of candidates from LIGO.
Matched filtering alone is insufficient in non-Gaussian detector noise, producing frequent non-astrophysical triggers with large SNR (Abbott et al. 2016f).Pipelines can choose among different techniques to mitigate this effect: calculating additional statistics based on the template waveform (signal-based vetoes), explicitly zeroing out loud and short instrumental transients before matched-filtering (gating), and vetoing triggers based on known data-quality issues which are reported with the same latency as the strain data itself.In O2, all matched-filter searches employed signal-based vetoes; PyCBC Live and MBTAOnline applied vetoes based on low-latency data-quality information, while GstLAL applied gating.
The trigger lists produced by matched filtering and cleaned via the aforementioned procedures are searched for coincidences between detectors.Coincident triggers are ranked based on their SNRs and signal-based vetoes and the consistency of their SNRs, arrival times and arrival phases at the different detectors with an astrophysical signal.The pipelines construct this ranking and convert it to a statistical significance in different ways, described next.A measure of significance produced by all pipelines for each candidate is the estimated false-alarm rate (FAR), i.e., the rate at which we expect events with at least as high a ranking as the candidate to be generated due to detector noise.
MBTAOnline constructs a background distribution of the ranking statistic by making every possible coincidence from single-detector triggers over a few hours of recent data.It then folds in the probability of a pair of triggers passing the time coincidence test.
PyCBC Live's ranking of coincident triggers in O2 was somewhat simpler than the final offline analysis: it did not account for the variation of background over the parameter space (Nitz et al. 2017) and it did not include the sine-Gaussian signal-based veto (Nitz 2018).Py-CBC Live estimated the background of accidental coincidences by using time shifts between triggers from different detectors, as done by the offline analysis (Usman et al. 2016).The amount of live time used for background estimation in PyCBC Live was 5 hours, to be compared with ∼5 days of the offline analysis.This choice limited the inverse false-alarm rate of online detections to ∼100 years maximum, insufficient for claiming a very significant detection, but adequate for generating rapid alerts for astronomers.On the other hand, this choice gave the background estimation a faster response to variations in noise characteristics, which is useful considering the limited data quality flags available to the online analysis.GstLAL calculates the significance of triggers by constructing a likelihood-ratio ranking statistic that models the distribution of trigger properties for noise and GW events (Cannon et al. 2015).The background is computed by synthesizing likelihood ratios from a random sampling of a probability density that is estimated using non-coincident triggers accumulated over the course of an observing run, which are taken to be noise.

Online unmodeled searches
The two unmodeled signal searches (burst), cWB and oLIB, work by looking for excess power in the timefrequency (TF) domain of the GW strain data (Klimenko et al. 2016;Lynch et al. 2017).The cWB pipeline does this by creating TF maps at multiple resolutions across the GW detector network and identifying clusters of TF data samples with power above the baseline detector noise.Excess power clusters in different detectors that overlap in time and frequency indicate the presence of a GW event.The signal waveforms and the source sky location are reconstructed with the maximum likelihood method by maximizing over all possible timeof-flight delays in the detector network.The cWB detec-tion statistic is based on the coherent energy obtained by cross-correlating the signal waveforms reconstructed in the detectors.It is compared to the corresponding background distribution to identify significant GW candidates.
oLIB uses the Q transform to decompose GW strain data into several TF planes of constant quality factors Q, where Q ∼ τ f 0 .Here, τ and f 0 are the time resolution and central frequency of the transform's filter/wavelet, respectively.The pipeline flags data segments containing excess power and searches for clusters of these segments with identical f 0 and Q spaced within 100 ms of each other.Coincidences among the detector network of clusters with a time-of-flight window up to 10 ms are then analyzed with a coherent (i.e., correlated across the detector network) signal model to identify possible GW candidate events.
Similarly to PyCBC Live, both cWB and oLIB use local time slides to estimate the background and calculate the candidates' false alarm rates (FAR is detailed in section 3.3.1).

Vetting and approval process
During O1 and O2, all CBC and burst GW triggers were stored in an interactive database (see section 2.2.1) and required to pass a series of vetting procedures, both automatic (section 2.2.3) and manual (section 2.2.4), with the help of supervised protocols (2.2.2).

GraceDb and LVAlert
The Gravitational-wave Candidate Event Database (GraceDb 3 ) is a centralized hub for aggregating and disseminating information about candidate events from GW searches.It features a web interface for displaying event information in a human-friendly format, as well as a representational state transfer application program interface (RESTful API) for programmatic interaction with the service.A Python-based client code package is also maintained to facilitate interactions with the API; this set of tools allows users to add new candidate events to the database, annotate existing events, search for events, upload files, and more.
During O2, GraceDb sent push notifications about candidate event creation and annotation to registered listeners via the LIGO/Virgo Alert System (LVAlert), a real-time messaging service based on the Extensible Messaging and Presence Protocol (XMPP) and its publish-subscribe (pubsub) extension.Python-based command-line tools were provided to send and receive notifications, create messaging nodes, and manage node subscriptions.Typical receivers of LVAlert messages were automated follow-up processes which, when triggered, performed tasks such as parameter estimation or detector characterization for a candidate event (details in section 2.2.3).

Supervised follow-up process
Several follow-up processes responded to the entry of a GW candidate into GraceDb, notified by the arrival of an LVAlert message.Three of these processes were of immediate relevance to the EM follow-up effort: the low-latency sky localization probability map (skymap) generator for CBC triggers, BAYESTAR (Singer & Price 2016), the tracker of candidate event status/incoming information and alert generator/sender (approval processorMP ), and the tracker of other followup processing (eventSupervisor ).
In particular, approval processorMP was responsible for the decision to send alerts based on the following incoming state information: basic trigger properties from the pipelines (FAR, event time, detectors involved with the trigger), data quality and data products (sections 2.2.3 and 3.3.2),detector operator and advocate signoffs determining the result of human vetting (section 2.2.4), and other labels identifying time-correlated external triggers or signal injections performed in hardware at the sites.Hardware signal injections are simulated GW signals created by physically displacing the detectors' test masses (Biwer et al. 2017).Triggers with false alarm rates below an agreed-upon FAR threshold and with no injection or data quality veto labels generated alerts to the astronomers involved in the LIGO and Virgo EM follow-up community via the GCN network (see section 3.2) and GraceDb web services.

Online automatic data vetting
State information was provided to low-latency analysis pipelines indicating when the detectors' data were suitable for use in astrophysical analysis.This included times when the detectors were operating in a nominal state and data calibration was accurate.The lowlatency pipelines also dealt with the additional challenge of transient noise artifacts known as glitches, which often occurred in the detectors' data (Abbott et al. 2016f, 2019. To reduce the effect of glitches, which can mimic true GW signals to some degree but are uncorrelated in the GW detectors, multiple strategies were employed by LIGO and Virgo, including automatically produced data quality vetoes and human vetting of candidate events (see section 2.2.4).Data quality vetoes indicated times when a noise source known to contaminate the astrophysical searches was active.These vetoes were defined using sensors that measured the behavior of the instruments and their environment.This data quality information was applied in several steps.A set of data quality vetoes were generated in real time and provided to the low-latency pipelines alongside the detector state information.If a candidate GW event occurred during a time that had been vetoed, it was not reported for EM followup.Given that these vetoes could potentially prevent a true GW signal from being distributed, this category of data quality information was reserved for severe noise sources.
In parallel with this effort, low-latency algorithms searched LIGO data for correlations between witness sensors and the GW strain data to identify noise sources that might not have been included in defined data quality vetoes.For example, iDQ (a streaming machine learning pipeline based on Essick et al. 2013 andBiswas et al. 2013) reported the probability that there was a glitch in h(t) based on the presence of glitches in witness sensors at the time of the event.In O2, iDQ was used to vet unmodeled low-latency pipeline triggers automatically.

Human vetting
Human vetting of GW triggers was a critical part of the EM follow-up program, and had to be completed before sending any alert to the astronomers during O2.Potentially interesting triggers were labeled by approval processorMP to require signoffs from follow-up advocates and operators at each relevant detector site.
Different groups of persons from the collaborations were involved in the decision-making process including Rapid Response Teams (RRT) with commissioning, computing, and calibration experts from each of the de-tector sites, pipeline experts, detector characterization experts, and EM follow-up advocates.
First, the on-site operators had to check the status of the instruments within one minute of the trigger, to ensure that unusual events (thunderstorms, trucks driving close to the buildings, etc.) did not happen at the time of the GW trigger and that the interferometer status was nominal.
Second, the experts and on-duty advocates met during an on-call validation process organized immediately after being notified of the trigger.All previously mentioned algorithms in section 2.2.3 and additional data quality information not accessible at low-latency timescales were considered.For example, the Omega scan and Omicron scan algorithms (Chatterji et al. 2004;Robinet 2016) created time-frequency visualizations of witness sensor data around the time of the candidate event.This allowed for detailed views of instrumental or environmental noise that could potentially influence the detectors' GW strain data.In O2, this information was used to identify false triggers due to noise and veto them before they were reported for EM follow-up.
Third, pipeline experts were asked to check pipeline results, in particular to evaluate the significance of marginal triggers.In the case of more than one viable candidate event (within 1 second for CBC and 5 seconds for burst triggers), the advocates selected the most promising candidate based on pre-established criteria (e.g.lowest FAR, choosing CBC over burst triggers).
When Virgo joined the LIGO network, it was not used to estimate the FAR of the GW candidate, but only to constrain the sky localization.
Finally, the EM follow-up advocates selected the skymap to send depending on the cross-checks done by the RRT at the different instrument sites, with priority given to the two LIGO detectors as the most sensitive instruments in the network.Then, they released the skymap to the external community and composed the GCN circular (see section 3.2).
When necessary, the pipeline experts and the data quality team, with the help of the RRT, recommended a retraction after days or weeks, using extended data investigation (Abbott et al. 2019) and/or updated FAR calculation based on additional background data.

Triggers distributed during O2
During O2, only GW candidates that passed the above series of checks were distributed to partner astronomers (see Table 2).Approximately half the triggers were rejected during the human vetting process (described in section 2.2.4) due to the presence of glitches (see Ab-bott et al. 2018bAb-bott et al. , 2019)).The number of vetoed triggers decreased by 80% from the first half of the O2 observing run to the second due to pipeline software upgrades to avoid transient noise.Other candidate events were vetoed because they were generated due to specific hardware problems or by not meeting the requirements of the O2 alert distribution policy (e.g., single-detector triggers, FAR being above the O2 threshold value, and very high latencies).
The list of distributed triggers during O2 and their online characteristics are provided in Table 2.We note that both CBC and burst pipelines identified the loudest GW candidate events.Six low-latency CBC candidates were ultimately confirmed as GW detections and are described in detail in Abbott et al. (2018a).G288732 (subsequently named GW170608) occurred when LIGO-Hanford was undergoing angle-to-length decoupling (a regular maintenance procedure which minimises the coupling between the angular position of the test-mass mirrors and the measurement of the strain) Abbott et al. (2017a), whereas for G268556 (i.e., GW170104), the calibration state was not nominal (Abbott et al. 2017c), creating a high latency in the distribution of alerts.These two real events were recovered due to expert vigilance rather than automated procedures.Moreover, G298048 (i.e., GW170817) was first identified as a single-detector trigger in the LIGO-Hanford data; a glitch in LIGO-Livingston caused the trigger to be rejected and the SNR was too low in Virgo to be detected.
Burst event G270580 was retracted offline due to its correlation with seismic noise (LIGO Scientific Collaboration & Virgo Collaboration 2017a).The CBC candidates G275697, G275404 and G299232 were not present in the offline pipeline analysis whereas other marginal candidates have been listed in Abbott et al. (2018a).The burst triggers G274296, G277583, G284239 and G298389 are consistent with background noise based on their event parameters and FARs; hence they are of no further interest.The high latency in sending alerts for the two oLIB events, G284239 and G298389, was due to their skymap generation.

DISTRIBUTION OF ALERTS
In this section, we present GW candidate information that we distributed and how this supported the EM observational campaigns.

O2 partners network
For O2, LIGO/Virgo signed 95 memoranda of understanding (MoUs) with different institutions, agencies, and groups of astronomers from more than 20 countries.The goal was to enable multi-messenger observations of Table 2. Characteristics of the distributed triggers which passed the EM follow-up validation process: time of the GW candidate event, status of the event after offline analysis (Confident i.e., Confidently detected GW event; Retracted due to further noise investigation; or NFI i.e., No Further Interest, not present in the offline analysis or consistent with noise), nature of the candidate with an EM-Bright classifier (described in section 3.3.2;if N/A, classifier not available for burst triggers), list of online searches that detected the candidate event (the pipeline selected for the distributed alert is in bold, some of the pipelines are not indicated in the first GCN circular since they reported the trigger with larger latency), its FAR (online pipeline-dependent, see section 3.3.1),the latency between the event time and event submission into GraceDb and the delay between the event time and the alert distribution (first GW notice sent to GCN for distribution to partners, see section 3.2).astrophysical events by GW detectors with a wide range of telescopes and instruments from EM and neutrino astronomy.
During O2, 88 groups had operational facilities and the ability to receive and send notifcations regarding their observations through the GCN network (see section 3.2).More than 100 space and ground-based instruments were involved in the EM follow-up campaign by covering radio, optical, near-infrared, X-ray and gammaray wavelengths.The telescopes sensitive in the optical bands were the most numerous, representing half of the instruments.The follow-up network also included three facilities capable of detecting high-energy neutrinos: Ice-Cube, ANTARES, Pierre Auger, searching for transients in the northern and southern hemispheres.

Distribution of the alerts via the GCN network
The Gamma-ray Coordinates Network (GCN) 4 was adopted from the GRB community to be used as an alert platform for both LIGO/Virgo observations and multimessenger follow-up.There are two types of GCN alerts: notices and circulars.During O2, the LIGO/Virgo GCN network was private; a requester had to be a member of the LV-EM Forum 5 to receive and send any messages.This is in contrast with normal public operation of GCN as used by the GRB community for decades.The LV-EM Forum, which consists of a wiki and mailing list, allowed registered astronomers to access information about GW candidate events selected for follow-up observations.GCN/LVC notices (i.e., LIGO/Virgo-astronomers notices) are machine-readable-computer-generated messages containing basic information about GW candidate events (e.g., time of the event and/or a sky localization probability map) or EM counterpart candidates.For the LIGO and Virgo collaborations' alerts, three types of GCN/LVC notices were produced: preliminary, initial, and update, although the preliminary notices were distributed only internally within the LIGO/Virgo collaborations while the others were sent to all members of the LV-EM forum.There was the possibility of sending a retraction notice as well.
• The preliminary notice contains only basic trigger information such as the trigger time (equivalent to the event UTC time), the online pipeline that generated the trigger, and the event false alarm rate.
It may also contain a skymap if one is available.It 4 https://gcn.gsfc.nasa.gov 5 https://gw-astronomy.org/ reports unvetted GW candidates and is produced ∼1-3 minutes after the actual event time.
• The initial notice is available ∼20-1000 minutes after the event (see Table 2) and is the result of further processing and human vetting of the event (see section 2.2).In addition to the fields provided in the preliminary notices, it contains a link to the first sky localization probability map and source classification information if available for CBC candidate events.
• The update notice is available from hours to months after the event and reports offline and parameter estimation analysis, in terms of improved FAR and sky localization.
During O2, there were 198 individuals and groups that received one or more of the three LVC notice types by any of the distribution methods and formats (i.e., VOevents, binary socket packets, and email-based methods).
The GCN circulars are human-generated prose-style descriptions of the event or follow-up observations made.They are generally sent shortly after their associated notices.For example, the LVC team generated one or two circulars for each GW candidate event with the first being sent ∼1-2 hours after the event time.Circulars are largely used to give information about follow-up observations, characteristics of the instruments/telescopes, and EM counterpart candidates.During O2, there were 385 recipients of the LVC/astronomers private circulars.

Information sent to observing partners
During O1 and O2, LIGO/Virgo notices and circulars contained basic trigger information such as the event time, corresponding online pipeline name, the list of contributing instruments (H1, L1, V1), and a sky localization probability map.In the case of CBC triggers for O2, additional information about the nature of the source (see section 3.3.2) and its localization with distance (see section 3.3.3)was provided.

Significance of the alerts
The significance of an online GW trigger during O2 was determined primarily by its false alarm rate (FAR).The FAR of a trigger quantifies the rate at which triggers of a given kind would be generated by an online detection pipeline from data that are void of any GW signal.Only triggers with a FAR below a pre-defined threshold were considered for EM follow-up.For the majority of O2, this threshold on FAR was once per two months (1.9×10 −7 Hz).Thus, any trigger that was generated by an online detection pipeline which could have Table 3. Properties of the GW alerts including the network SNR, the candidate event FAR, the sky localization area, and luminosity distances.Note that sky localization area and luminosity distances for the online search can differ from results mentioned in the distributed GCNs a .Furthermore, the distance estimates stated in GCN circulars are the a posteriori mean ± standard deviation while distance estimates and confidence intervals stated in the table are the a posteriori median and central 90% intervals.For confident GW events, the table shows results obtained from the offline refined analysis for comparison.Network SNR and FAR are the offline analysis results obtained with the pipeline selected for online distribution of the alerts (see Table 2 and Table 1 in Abbott et al. (2018a)).Offline luminosity distance and sky localization area (50% and 90% confidence regions) are listed also in Table 8 from Abbott et al. (2018a), with small differences arising from using the posterior data samples directly versus the generated skymap files  b The network SNR and the false alarm rate depend on the pipeline that triggered the event.
c No candidate event was found during the offline analysis.
d Localization is obtained as the arithmetic mean of cWB and LIB.
e All skymaps excluding those using Virgo data round sky localization areas to the nearest 10; otherwise, to the nearest 1.
1.0 2.83 10.0 100.0 been generated simply by noise at a rate higher than once per two months was rejected for the EM follow-up program.The FAR estimation is specific to the pipeline that triggered the event (see section 2.1 and Table 3 for distributed alerts and the associated FARs).In Table 2, the eight triggers which were not confirmed as confident events were reported by five different pipelines.This is consistent with the expected number of false alarms from five pipelines in 118 days of coincident data from LIGO-Hanford, LIGO-Livingston, and Virgo (Abbott et al. 2018a).

Source classification of CBC candidate events
In an event where at least one of the component compact objects is a neutron star, the GW event is more likely to be accompanied by an EM counterpart.A new low-latency pipeline was implemented in O2 to provide observers with a source classification for compact binary coalescences.In low latency, the earliest event information that is available to use are the point estimates.The point estimates are values of the masses (m 1 , m 2 ), and the aligned components of spin (χ 1 , χ 2 ) of the template that triggered to give the lowest false alarm rate during the search.However, these point estimates have uncertainties and are expected to be offset with respect to the true component values (Finn & Chernoff 1993;Jaranowski & Krolak 1994;Cutler & Flanagan 1994;Poisson & Will 1995;Arun et al. 2005;Lindblom et al. 2008;Nielsen 2013;Ohme et al. 2013;Hannam et al. 2013).Thus, any inferences drawn purely from the point estimates are prone to detection pipeline biases.To mitigate this effect, an effective Fisher formalism, introduced in Cho et al. (2013), was employed to construct an ellipsoidal region around the triggered point.This region, called the ambiguity ellipsoid, increases the chances of including the region of the parameter space that matches best with the true parameters of the source.This ambiguity ellipsoid is populated with 1000 points (a total of 1001 points including the original point estimate) which are called the ellipsoid samples.For each ellipsoid sample, the source classification quantities are computed.The dimensionality of the ambiguity ellipsoid is determined by the number of parameters required to compute the source classification quantities.
In O2 we delivered a twofold classification: the first which gives the probability that at least one neutron star is present in the binary, and the second which gives the probability that there is some baryonic mass left outside the merger remnant, i.e., the EM-Bright classification.While the first classification requires only one parameter for the inference to be conducted, namely the secondary mass component, the second classification, which is more model dependent, potentially needs more parameters than just the secondary mass.Indeed, we adopted the EM-Bright classification method from Foucart (2012) and implemented as in Pannarale & Ohme (2014), which uses three parameters (m 1 , m 2 , χ 1 ), the masses of the primary and secondary objects, and the aligned spin component of the primary object respectively.The method estimates the mass remaining outside the black hole after a NS-BH merger, which includes the mass of the accretion disk, the tidal tail, and/or unbound ejecta.A 3D ambiguity ellipsoid was generated around the triggered point to enclose a region of 90% match within its boundary.This was done in the (M c , η, χ 1 ) parameter space where M c = (m 1 m 2 ) 3/5 /(m 1 +m 2 ) 1/5 is the chirp mass and η = m 1 m 2 /(m 1 + m 2 ) 2 is the symmetric mass ratio.This was achieved using infrastructure developed in Pankow et al. (2015).The fraction of ellipsoid samples with secondary mass less than 2.83 M constituted the first classifier, namely, the probability that there is at least one neutron star in the binary.
Next, the mass left outside the black hole was computed for each ellipsoid sample using the fitting formula, Eq.( 8) of Foucart (2012).The fraction of ellipsoid samples for which this was greater than zero was calculated.This constituted the second classifier.
It is important to note that Foucart's fitting formula is only valid in the NS-BH region of the parameter space.In O2, we made the assumption that binary neutron star mergers always emit EM radiation (i.e., EM-Bright: 100%) and binary black hole mergers are always void of such emission (i.e., EM-Bright: 0%, or equivalently, EM-Dark).Thus, the second classifier was computed only for ellipsoid samples with one component mass less than 2.83 M .
In Figure 1, we can see different regions of the parameter space where the aligned spin component has been suppressed and only the mass values are shown.The blue region is the BNS parameter space where every ellipsoid sample is treated as EM-Bright.The dark grey region depicts the BBH parameter space where all ellipsoid samples are treated as EM-Dark.The light grey and green shaded regions are the NS-BH part of the parameter space where the EM-Bright probability is computed using Foucart's fitting formula.The green shaded regions show at which part of this parameter space the ellipsoid samples will give non-zero remnant mass outside the final black hole.The various shades of green discriminate between different χ 1 values, so that, for example, an ellipsoid sample with mass values (7.0, 2.0)M will give non-zero remnant mass outside the black hole according to Foucart's fitting formula if the value of χ 1 is slightly greater than 0.5, but no mass left outside the black hole below this value.Additionally, this figure also shows ellipsoid samples for GW170817.The detection pipeline point estimate for this source was consistent with a binary neutron star system.Upon construction of the ambiguity ellipsoid around this point estimate, we found that all the ellipsoid samples lie completely within the blue shaded region that is always assumed to be EM-Bright.In contrast, a second event which is a binary black hole system, GW170608, is also depicted and its ellipsoid samples lie entirely in the EM-Dark regime.
During O2, source classification information was provided (see Table 2) on the basis of the detection pipeline within a few minutes (depending upon the component masses) of the GW detection.In the future, during the third observing run of LIGO and Virgo (O3), source classification information will be provided at multiple levels of refinement as parameter estimation results are made available.

Skymaps and Luminosity Distances
Currently, CBC sky localization probability maps (skymaps) for modeled searches are produced by two different algorithms, based on latency and sophistication: LALInference and BAYESTAR.LALInference uses stochastic sampling techniques for the entire parameter space of a CBC signal, such as Markov Chain Monte Carlo (MCMC) and nested sampling (Veitch et al. 2015).Kernel density estimation is applied to the posterior samples to construct a smooth probability distribution from which the sky location and distance information is calculated.Although LALInference skymaps use the most complete description of the signal, sampling is computationally expensive, with a latency ranging from hours to days and weeks.BAYESTAR circumvents this issue by utilizing the fact that most of the information related to localization is captured by the arrival time, coalescence phase, and amplitude of the signal (Singer & Price 2016). 6As implemented in O2, the BAYESTAR likelihood is equivalent to that of LALInference.The marginalization is carried out via gaussian quadratures and lookup tables.Hence, the computation can be completed within a few seconds.Due to its highly parallel nature, a typical BAYESTAR skymap is computed in 30 s.
Both LALInference and BAYESTAR provide distance information in the skymaps.The distance is estimated from the moments of the posterior distance distribution conditioned on sky position.7In the case of LALInference the moments are calculated from a kernel density estimate trained on the posterior samples while for BAYESTAR the moments are calculated by numerical quadrature of the posterior probability distribution.
As mentioned in section 2.1.2,burst triggers are generated by two algorithms, cWB and oLIB which produce their respective skymaps.The detection statistic of cWB is sensitive to the time delay in arrival of the signal at the detector sites and, thus, is a function of the sky position.The skymap is constructed based on the likelihood at each point in the sky (see Klimenko et al. 2016 for details).The oLIB skymap algorithm, LALIn-ferenceBurst, is similar to its CBC counterpart, LALInference, in the sense of being a template based search algorithm, except that it uses only sine-Gaussian templates.It reports a posterior in nine parameters where marginalization of parameters apart from sky position forms the skymap.Unlike CBC skymaps, burst skymaps do not contain distance information due to the lack of signal model.
Each skymap is distributed as a FITS file, a postprocessed representation of the posterior samples to facilitate common queries and calculations regarding area and distance/volume when applicable.Consistent but non-numerically identical results are expected of integrals computed using FITS files versus MCMC with the posterior samples.Thus, luminosity distance medians in Table 3 and in Table III of Abbott et al. (2018a) differ but agree to within about 5% of the uncertainties in these quantities.
It is not unusual for both CBC and burst pipelines to identify the same astrophysical event, especially for heavier BBH mergers where the waveform is of shorter duration.In such cases, it is expected that the modeled CBC skymaps have smaller sky localizations.While there might be differences in the sky localizations, most of the probability is contained around the true location (see Vitale et al. 2017 for a comparative study).
Figure 2 shows the skymaps distributed during O2 using the low-latency algorithms discussed above.The upper panel shows the sky localizations of the high significance candidates (FAR < 1/(100 yr) = 3×10 −10 Hz), which are confident GW events.Their corresponding refined sky localizations are shown in Figure 3. Taking into account the 90% confidence region, the initial sky localizations are largely consistent with the final localizations, with GW170814 being the exception (see section 3.3.4).
A number of candidates (principally from burst pipelines) are consistent with noise and are not considered to be GW events.These are shown in the middle panel of Figure 2. The bottom panel of the same figure shows the triggers rejected by offline analysis.

Three-Detector Observations
The Virgo contribution to O2 is noteworthy in significantly improving the localizations of the events GW170809, GW170814 and GW170817.8As an example, for GW170814, the 50% sky localization area is confined in a single region of tens of square degrees in the southern hemisphere.We note that Virgo data was used to produce updated skymaps of GW170823 (LIGO Scientific Collaboration & Virgo Collaboration 2017x,d) soon after identification of the signal.Subsequent data validation studies identified problems with the Virgo data around GW170823 which made it unreliable for use in parameter estimation: the final sky localization relies only on the LIGO data.
A note should be made regarding the initial and refined skymaps of GW170814 (Abbott et al. 2017b,d): it is expected that the initial and updated skymaps for compact binary coalescence events are similar unless there are significant changes in data calibration, data quality or glitch treatment or low-latency parameter estimations.
We observed a significant shift between the first GW170814 sky localization area and its update (LIGO Scientific Collaboration & Virgo Collaboration 2017y,z).At the time of GW170814, the Virgo power spectral density (PSD) changed significantly with respect to the estimated PSD used to precompute the template bank by the GstLAL online search.Consequently, the phase of the whitening filter for Virgo was no longer cancelled out by the templates.This resulted in a Virgo residual phase, which produced a phase shift in the Virgo SNR time series causing an east shift of the 50% credible region of the sky localization area.
The antenna patterns for the three detectors are shown in Figure 4.The patterns represent the sensitivity of a detector to an event on the sky.The generic L-shaped detectors are most sensitive to signals coming from a direction perpendicular to the plane of its arms; this explains the two antipodal regions of maximum sensitivity.The plane of the arms of the detector form the least sensitive region.In this plane, the detectors are insensitive to the signal if directed along a diagonal of the L shape giving four islands of insensitivity.

Electromagnetic/neutrino follow-up activity of gravitational waves alerts
Searches for electromagnetic/neutrino counterparts employed a variety of observing strategies, including archival analysis, prompt searches with all-sky instruments, wide-field tiled searches, targeted searches of potential host galaxies, and deep follow-up of individual sources.They took into account the properties of the instruments, their observational capabilities (e.g., location on Earth for ground-based telescopes, pointing strategy for space-based instruments), and the characteristics of possible counterparts within their sensitivity band.For instance, the GW170817/GRB 170817A observational campaign perfectly illustrates the different observing strategies that led to the identification of the associated multi-wavelength electromagnetic emis- sion: the independent identification of the sGRB by Fermi, the all-sky archival searches and wide-field of view follow-up, the discovery of the host galaxy and the optical GW counterpart by galaxy catalog targeted searches, the spectroscopic characterization of the optical counterpart, and the identification of X-ray and radio counterparts with deep follow-up (Abbott et al. 2017e).Similar strategies were applied to the other triggers sent in O2, but on a more modest scale.(Kasliwal et al. 2017), provided pre-merger images and for prompt/early emission.The time window around the GW candidate used to search for the EM counterpart is defined on the basis of the type of GW event and the counterpart properties expected in a specific band.For GRBs, it typically covered a few seconds to minutes.In the case of neutrinos, a window of ±500 s around the merger was used to search for neutrinos associated with prompt and extended gamma-ray emission (Baret et al. 2011), and a longer 14-day time window after the GW detection to cover predictions of longer-lived emission processes (Fang & Metzger 2017).
Tiled and galaxy catalog targeted searches -The LIGO/Virgo alerts enabled EM follow-up campaigns by scanning large portions of the gravitational-wave sky localization error box or by targeting galaxies located within it (Gehrels et al. 2016).In the case of CBC triggers, the 3D sky-distance maps (see section 3.3.3)were used to set observational strategies using the available galaxy catalogs (Abbott et al. 2012;Nissanke et al. 2013b;Hanna et al. 2014).Other strategies were also employed, for example selecting strong-lensing galaxy clusters that lie within the 90% credible region (GLGW Hunters Smith et al. 2017).This early follow-up of gravitational waves generally lasted tens of hours after the alert with observations from X-ray telescopes (such as Swift/XRT  During the O2 follow-up campaign, most of the X-ray and optical candidates were classified through spectroscopic observations, which identified contaminants such as Galactic novae, supernovae, and active galactic nuclei (see e.g., observation campaign of GW170814 campaign by Copperwheat et al. 2017).9 During the GW170104 follow-up campaign, the AT-LAS survey reported a rapidly fading optical source called ATLAS17aeu in coincidence with the GW skymaps, ∼21.5 hours after the GW trigger time.Deeper investigations with a collective approach demonstrated that ATLAS17aeu was the afterglow of a long, soft gamma-ray burst GRB 170105A, unrelated with GW170104 (Bhalerao et al. 2017;Stalder et al. 2017;Melandri et al. 2018).This was an example where a coordinated follow-up of a GW event led to a serendipitous observation of an unrelated interesting event in time-domain astronomy.
Long term follow-up -The long term follow-up of gravitational waves is also indispensable.One of the main challenges in radio follow-up of GW events is the association of the counterpart candidate found in the GW source localization region with the GW event, primarily due to a lack of temporal coincidence (Hotokezaka & Piran 2015;Palliyaguru et al. 2016).However, the science return is potentially immense for such long term follow-up.For example, long-term X-rays, optical, and radio monitoring of GW170817 provided constraints on jet emission scenarios and models (Hotokezaka et al. 2016;Haggard et al. 2017;Mooley et al. 2017;Hallinan et al. 2017b;Margutti et al. 2018;Ghirlanda et al. 2018).
Figure 5 summarizes the exchange of information between LIGO/Virgo and observing partners showing the extensive follow-up activity.More than 20 circulars were generated during each follow-up campaign.From Table 3, we note that the two oLIB events (G284239 and G298389) were the least followed due to their lower significance and higher latency in delivery of the initial skymaps.Also, more than 40 GCNs were generated for GW candidates that included a neutron star as one of the binary components (G275404, G275697, G298048, and G299232).G299232 was more extensively followed due to its classification as a potential NS-BH than confident detections like GW170814 or GW170608, which were BBH coalescences.This underscores the importance of source classification during O3, when observers might want to allocate their valuable resources in the most efficient manner possible.
From the EM follow-up activity side, no significant counterpart associated with BBH events was discovered; the most promising candidate was a weak gamma-ray transient found by AGILE during GW170104 lasting 32 ms and occuring 0.5 s before the GW event (Verrecchia et al. 2017) but not confirmed by other instruments.

CONCLUSION
The O2 follow-up campaign of GW candidate events was a comprehensive effort of collaborating groups in astronomy and astro-particle physics.This effort was enabled by GW alerts distributed by the LIGO and Virgo collaborations.The triggers were produced by modeled searches for compact binary coalescences and unmodeled searches for transients such as the core-collapse of massive stars or neutron star instabilities.
During O2, 14 alerts were distributed with latencies ranging from 22 minutes up to 16 hours, most of them in less than an hour.Six events were declared as confident GW events associated to the merger of black holes or neutrons stars.The latency in sending alerts was dominated by human vetting of the candidate, which was necessary to validate data quality information beyond the ability of automated checks in place.O2 alerts, with false alarm rates less than one per two months, were distributed via the private GCN (Gamma-ray Coordinates Network) and contained GW information required for an efficient follow-up: the event time, sky localization probability map, and estimated false alarm rates.For compact binary merger candidates, skymaps with a third dimension (distance), the probability of the system to contain a neutron star and the probability to be electromagnetically bright were provided.The sky localization area of distributed events, which was hundreds to thousands of square degrees with the two LIGO interferometers, was dramatically reduced at the end of the campaign with the inclusion of Virgo.
The O2 follow-up program enabled the first combined observation of a neutron-star merger in gravitational waves (GW170817), gamma rays (GRB 170817A), and at optical wavelengths (AT 2017gfo).Together with the identification of the host galaxy and the subsequent observations of the X-ray and radio counterparts, the data collected on this event has yielded multiple groundbreaking insights into kilonova physics, the origin of heavy elements, the nature of neutron-star matter, cosmology, and basic physics.The success of GW170817 and the larger O2 follow-up campaign demonstrates the importance of a coordinated multi-wavelength follow-up program for O3 and beyond.
Future priorities of the LIGO/Virgo Collaborations include further reduction in latency of GW alerts.The first hours after BNS mergers are crucial for observing the early X-rays, UV and optical emissions with space and ground instruments.For example, in the case of GW170817, the five hours delay in distributing skymaps, due to human intervention required to window out a glitch in LIGO-Livingston data, prevented the discovery of early emission, which could have revealed more about the the merger remnant and emission processes.
Beginning with the O3 observing run, LIGO and Virgo will issue public alerts 10 .There will be automated preliminary notices generated based on the low-latency analysis.The FAR threshold for issuing preliminary notices will be set so that it yields alerts with high confidence (at the level of 90%) of having astrophysical origin for GW source types with populations that have been reliably measured until now.For other transient sources that have not been detected yet, the threshold will be lower, at the level of 1 per year.These will be followed by human vetted initial notices or retraction notices with a latency on the order of tens of minutes for high-interest candidates and within hours for more routine detections.We expect an increase in the number of GW events; BBH merger candidates will dominate by one order of magnitude from a few per week to a few per month whereas the BNS coalescence candidates are anticipated to occur a few times per year (Abadie et al. 2010;Abbott et al. 2016cAbbott et al. , 2017dAbbott et al. , 2018c,a),a).Both the increase in the number of significant candidate events and the need to reduce the latency of sending alerts will require an updated alert distribution infrastructure with a nearly fully-automated vetting protocol.
We have detailed the transient identification and alert systems utilized during the second LIGO/Virgo observing run.This work played a crucial role in ushering in the era of gravitational wave multi-messenger astronomy.

a
In bold, selected pipeline for distribution of the alert to O2 partners b Due to the non-standard way in which this trigger was found, the PyCBC Live low-latency pipeline was run by hand over a short period of data (tens of minutes) in order to produce a trigger for follow-up as quickly as possible.The precision of the FAR estimate is limited by the use of a shorter than normal period of data.c The online GstLAL trigger was identified as a single-detector trigger.d The sky localization sent to partners five hours after the trigger time was derived from a PyCBC analysis after the high-amplitude glitch in LIGO-Livingston was windowed out (LIGO Scientific Collaboration & Virgo Collaboration 2017b; Abbott et al. 2017d).The FAR was calculated with H1 only.e The first circular sent to partners for G298048 informed that a GW candidate event with a single instrument was associated with the time of a Fermi GBM trigger (LIGO Scientific Collaboration & Virgo Collaboration 2017c).The initial Notice sent to partners, at 13:08 UTC, contained a skymap simply representing the quadrupolar antenna response function of the LIGO-Hanford detector over the entire sky.fThe sky localization sent to partners was derived from a PyCBC analysis(LIGO Scientific Collaboration & Virgo Collaboration 2017d) . A: LIGO Scientific Collaboration & Virgo Collaboration (2017e) -B: Abbott et al. (2018a) -C: LIGO Scientific Collaboration & Virgo Collaboration (2017f) -D: LIGO Scientific Collaboration & Virgo Collaboration (2017g,a) -E: LIGO Scientific Collaboration & Virgo Collaboration (2017h) -F: LIGO Scientific Collaboration & Virgo Collaboration (2017i) -G: LIGO Scientific Collaboration & Virgo Collaboration (2017j) -H: LIGO Scientific Collaboration & Virgo Collaboration (2017k,l) -I: LIGO Scientific Collaboration & Virgo Collaboration (2017m) -J: LIGO Scientific Collaboration & Virgo Collaboration (2017n,o) -K: LIGO Scientific Collaboration & Virgo Collaboration (2017p) -L: LIGO Scientific Collaboration & Virgo Collaboration (2017q) -M: LIGO Scientific Collaboration & Virgo Collaboration (2017r) -N: LIGO Scientific Collaboration & Virgo Collaboration (2017s) -O: LIGO Scientific Collaboration & Virgo Collaboration (2017t) -P: LIGO Scientific Collaboration & Virgo Collaboration (2017u) -Q: LIGO Scientific Collaboration & Virgo Collaboration (2017b) -R: LIGO Scientific Collaboration & Virgo Collaboration (2017v) -S: LIGO Scientific Collaboration & Virgo Collaboration (2017w) -T: LIGO Scientific Collaboration & Virgo Collaboration (2017x) -U: LIGO Scientific Collaboration & Virgo Collaboration (2017d)

Figure 2 .
Figure2.Distributed low-latency O2 skymaps in ICRS coordinates -Mollweide projection.The shaded areas correspond to the confidence region that encloses 90% of the localization probability.The inner lines define the target regions at a 10% confidence level with changing color scheme at every 10% increase in confidence.The upper panel shows confident events, the middle panel GW candidates consistent with noise, and the bottom panel the triggers rejected by the offline analysis.

Figure 3 .
Figure3.Offline O2 sky localizations for the confident events published in the official LIGO and Virgo catalog -Mollweide projection.The shaded areas define the 90% confidence levels.The inner lines define the target regions at a 10% confidence level with changing color scheme at every 10% increase in confidence.

Figure 4 .
Figure 4. Antenna patterns of the GW detectors in the network at the time of the GW170817 event Upper.LIGO-Hanford.Middle.LIGO-Livingston.Bottom.Virgo.ICRS coordinates -Mollweide projection.The position of the optical transient AT 2017gfo is indicated with a red star.The color indicates the strength of the response with yellow being the strongest and blue being the weakest.At the location of GW170817, the antenna pattern amplitude for V is 2.5 to 3 times lower than for H and L.
Deep follow-up and classification of the counterpart candidates -After identification of potential counterparts, further classification was pursued with narrow field-ofview and sensitive instruments.The large numbers of candidates and limited availability of larger instruments were two of the difficulties in counterpart identification.

Figure 5 .
Figure 5. Summary of the exchange of information between LIGO/Virgo and its partners showing the extensive followup activity.The color code for the alerts refers to the status of the alerts (confident, rejected, no further interest triggers).

Table 1 .
Major parameters of O2 online search pipelines based on compact binary merger waveform models.
9Figure1.This figure shows the different regimes of operation by the source classifier used in O2.The BNS region is given by (m1, m2) ∈ (0, 2.83)M (cyan).The upper limit of 2.83M is the maximum NS mass allowed by the 2H EOS Kyutoku et al. (2010) used in the source classification software.Any system lying in this region is always considered to have an EM counterpart.The region m1 > 2.83M with m2 ≤ 2.83M is the NS-BH region of the source classifier.The baryonic mass left outside the BH is computed in this region.In this scheme, the presence of any such matter is considered to provide the potential for an EM counterpart.This boundary of zero mass left outside the final BH is a function of the spin of the system.