Kilonova Luminosity Function Constraints Based on Zwicky Transient Facility Searches for 13 Neutron Star Merger Triggers during O3

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and

Published 2020 December 22 © 2020. The American Astronomical Society. All rights reserved.
, , Citation Mansi M. Kasliwal et al 2020 ApJ 905 145 DOI 10.3847/1538-4357/abc335

Download Article PDF
DownloadArticle ePub

You need an eReader or compatible software to experience the benefits of the ePub3 file format.

0004-637X/905/2/145

Abstract

We present a systematic search for optical counterparts to 13 gravitational wave (GW) triggers involving at least one neutron star during LIGO/Virgo's third observing run (O3). We searched binary neutron star (BNS) and neutron star black hole (NSBH) merger localizations with the Zwicky Transient Facility (ZTF) and undertook follow-up with the Global Relay of Observatories Watching Transients Happen (GROWTH) collaboration. The GW triggers had a median localization area of 4480 deg2, a median distance of 267 Mpc, and false-alarm rates ranging from 1.5 to 10−25 yr−1. The ZTF coverage in the g and r bands had a median enclosed probability of 39%, median depth of 20.8 mag, and median time lag between merger and the start of observations of 1.5 hr. The O3 follow-up by the GROWTH team comprised 340 UltraViolet/Optical/InfraRed (UVOIR) photometric points, 64 OIR spectra, and three radio images using 17 different telescopes. We find no promising kilonovae (radioactivity-powered counterparts), and we show how to convert the upper limits to constrain the underlying kilonova luminosity function. Initially, we assume that all GW triggers are bona fide astrophysical events regardless of false-alarm rate and that kilonovae accompanying BNS and NSBH mergers are drawn from a common population; later, we relax these assumptions. Assuming that all kilonovae are at least as luminous as the discovery magnitude of GW170817 (−16.1 mag), we calculate that our joint probability of detecting zero kilonovae is only 4.2%. If we assume that all kilonovae are brighter than −16.6 mag (the extrapolated peak magnitude of GW170817) and fade at a rate of 1 mag day−1 (similar to GW170817), the joint probability of zero detections is 7%. If we separate the NSBH and BNS populations based on the online classifications, the joint probability of zero detections, assuming all kilonovae are brighter than −16.6 mag, is 9.7% for NSBH and 7.9% for BNS mergers. Moreover, no more than <57% (<89%) of putative kilonovae could be brighter than −16.6 mag assuming flat evolution (fading by 1 mag day−1) at the 90% confidence level. If we further take into account the online terrestrial probability for each GW trigger, we find that no more than <68% of putative kilonovae could be brighter than −16.6 mag. Comparing to model grids, we find that some kilonovae must have Mej < 0.03 M, Xlan > 10−4, or ϕ > 30° to be consistent with our limits. We look forward to searches in the fourth GW observing run; even 17 neutron star mergers with only 50% coverage to a depth of −16 mag would constrain the maximum fraction of bright kilonovae to <25%.

Export citation and abstract BibTeX RIS

1. Introduction

Gravitational-wave (GW) astrophysics is achieving a new frontier every 2 yr. On 2015 September 14, the Advanced LIGO/Virgo Collaboration (LVC) celebrated the revolutionary discovery of GWs from merging massive stellar black holes (BBHs; Abbott et al. 2016). On 2017 August 17, the physics and astronomy communities jointly celebrated the detection of GWs from the first binary neutron star (BNS) merger that lit up the entire electromagnetic (EM) spectrum (Abbott et al. 2017a, 2017b; Coulter et al. 2017; Evans et al. 2017; Goldstein et al. 2017; Haggard et al. 2017; Hallinan et al. 2017; Margutti et al. 2017; Troja et al. 2017; Kasliwal et al. 2019b). On 2019 April 26, the first candidate neutron star black hole (NSBH) merger was announced by Advanced LIGO/Virgo (Ligo Scientific Collaboration & VIRGO Collaboration 2019a, 2019b), and since then, there have been eight additional candidate NSBH events.

Unlike a BNS system, the very existence of an NSBH binary was observationally unconstrained. No pulsar in the Milky Way is known to have a black hole companion. A compact BNS merger has a viable stellar evolutionary formation channel (Tauris et al. 2015), since a few ultrastripped supernovae (SNe) have been seen (De et al. 2018; Nakaoka et al. 2020; Yao et al. 2020). On the other hand, it has been argued that the supermassive black holes in the nuclei of galaxies assist in the formation of compact NSBH (and BBH) systems by the eccentric Kozai–Lidov (EKL) mechanism (Naoz 2016; Stephan et al. 2019). Unlike a BNS merger, for which GW170817 serves as the Rosetta Stone of what to look for, theoretical predictions of the EM counterparts to NSBH mergers span a wide spectrum, depending on the system parameters (e.g., mass ratio, spin of the black hole, equation of state of the neutron star). While some scenarios predict that the neutron star is swallowed whole by the black hole and there is no EM emission, others predict a luminous kilonova where, compared to the BNS case, more lanthanide-rich material is ejected dynamically while comparable masses are ejected from the disk (e.g., Rosswog 2005; Foucart 2012; Hotokezaka et al. 2013; Kiuchi et al. 2015; Kawaguchi et al. 2016; Kasen et al. 2017; Kruckow et al. 2018; Broekgaarden et al. 2019; Nakar 2020; Fernández et al. 2020).

LIGO/Virgo's third observing run (O3; from 2019 April to 2020 March) has yielded real-time alerts on six BNS mergers and nine NSBH mergers. Alerts and localization maps were publicly released within minutes to a few hours after the mergers. Updates to localization maps and false-alarm rates (FARs) were released days to weeks after the mergers. The median localization was 4480 deg2. The median distance to BNS mergers was 214 Mpc, and that to NSBH mergers was 377 Mpc.

Given that the optical counterpart of GW170817 was first observed only 10.8 hr after merger, there is considerable debate on how the early emission evolves. Different models predict different early evolution (e.g., Drout et al. 2017; Kasliwal et al. 2017; Arcavi 2018; Piro & Kollmeier 2018; Waxman et al. 2018). Thanks to the low latency in the public O3 alerts, prompt follow-up was undertaken. Despite the localizations being coarser and the distances being further than expected (Abbott et al. 2018), the Global Relay of Observatories Watching Transients Happen (GROWTH 57 ) collaboration undertook systematic searches and extensive follow-up of every trigger with a worldwide network of telescopes. We used three discovery engines, the Zwicky Transient Facility (ZTF; Bellm et al. 2018; Masci et al. 2018; Graham et al. 2019), Palomar Gattini-IR (PGIR; Moore & Kasliwal 2019; De et al. 2020a), and Dark Energy Camera (DECam; Goldstein et al. 2019), and a suite of 17 follow-up facilities. Candidate counterparts and follow-up results from these searches were promptly announced via Gamma-ray Coordinates Network (GCN) circulars. In addition to GROWTH, several teams undertook wide-field searches for optical counterparts in O3, including Electromagnetic counterparts of Gravitational wave sources at the Very Large Telescope (ENGRAVE; Levan 2020), Global Rapid Advanced Network Devoted to the Multi-messenger Addicts (GRANDMA; Antier et al. 2020), Gravitational-wave Optical Transient Observer (GOTO; Gompertz et al. 2020), All Sky Automated Survey for SuperNovae (ASAS-SN; Shappee et al. 2014), Asteroid Terrestrial Last Alert System (ATLAS; Tonry et al. 2018), Panoramic Survey Telescope and Rapid Response System (PanSTARRS; Chambers et al. 2016), MASTER-Net (Lipunov et al. 2017), Searches after Gravitational Waves Using ARizona Observatories (SAGUARO; Lundquist et al. 2019), Dark Energy Survey Gravitational Wave Collaboration (DES-GW; Soares-Santos et al. 2017), Burst Optical Observer and Transient Exploring System (BOOTES), KM3Net, 58 and VINROUGE 59 (PI: Tanvir). We also undertook a wide-field radio search with the Australian Square Kilometre Array Pathfinder (ASKAP; Dobie et al. 2019).

This paper focuses on events that contain at least one neutron star; see Graham et al. (2020) for our candidate counterpart to a binary black hole merger. The LVC published GW190425 as a confirmed astrophysical BNS with a total system mass of 3.4 M (Abbott et al. 2020a). The LVC also published GW190814 as a confirmed astrophysical merger of a 23 M black hole with a 2.6 M compact object (Abbott et al. 2020b). While we await the final LVC results on the candidature and binary parameters of all other merger candidates from O3, we use the classifications and parameters released via GCN circulars. We refer to GW190814 and GW190425 as "sources" or "confirmed events" and use a "GW" prefix in the name. We refer to all others as "triggers" or "candidate events" with an "S" prefix in the name. We refer to the full set as "events."

We have previously published our search results for the highest-significance mergers: GW190425 (Coughlin et al. 2019d), GW190814 (Dobie et al. 2019; Andreoni et al. 2020b), and S2001015ae and S200115j (Anand et al. 2020). Here we focus on ZTF searches of the full set of O3 triggers and the implications of the joint nondetection of kilonovae from all merger candidates. In Section 2, we summarize the GW trigger selection criteria. In Section 3, we detail the discovery, follow-up, and rejection of candidate optical counterparts. In Section 4, we examine the model-independent implications of the luminosity function of kilonovae. In Section 5, we summarize our key results and look ahead to future GW observing runs.

2. Summary of GW Triggers

During the third LIGO/Virgo observing run, we triggered target-of-opportunity (ToO) searches based on the following criteria: (a) an initial classification with the highest probability of either BNS, NSBH, or MassGap; (b) if MassGap, then a nonzero probability of containing a neutron star; and (c) a visibility and mapping speed allowing us to observe >30% of the initial BAYESTAR sky map (Singer & Price 2016) within 24 hr of merger.

A total of 15 GW events satisfied criteria (a) and (b). In Table 1, we summarize 13 GW triggers during O3 for which we obtained either serendipitous or triggered coverage with the ZTF (we did not get any ZTF data on S190510g, as the sky position was too far south, or S190924h, as the sky position was too close to the Moon). In Figures 13, we show the ZTF coverage overlaid on the GW localization contours. Since the public ZTF survey systematically covers the accessible northern sky at an average cadence of 3 days to a median depth of 20.5 mag (Bellm et al. 2018), we "serendipitously" covered several GW sky maps. Serendipitous coverage contributed to more than 30% enclosed probability for the following triggers: GW190814, S190910d, S190910h, S190923y, S190930t, S200105ae, and S200213t. To improve depth/coverage/response time, we triggered ZTF ToO observations for 11 out of 15 events (and undertook DECam searches for three events; see Andreoni et al. 2019c, 2020b; Goldstein et al. 2019). Our triggered ToO observations optimized the trade-off between depth (more exposure time per pointing) and coverage of the localization map (more pointings to enclose more probability) using the gwemopt algorithm. A detailed case study of the ToO observations can be found in Coughlin et al. (2019d) and Anand et al. (2020). For S191205ah, our triggered observations were not completed due to bad weather, and only a small fraction was covered serendipitously. For S190910h, given the coarse localization, we relied only on serendipitous coverage as part of regular ZTF operations. For S190923y, given the large time lag between GW alert and first target visibility, we also relied only on serendipitous coverage.

Figure 1.

Figure 1. The ZTF coverage maps of two BNS triggers (S190901ap and GW190425) and two NSBH triggers (S190426c and GW190814) during O3 of LIGO/Virgo. Each square represents a ZTF pointing, and the solid line denotes the latest available GW 90% localization contour. Despite both BNS triggers being localized to a π of the sky, the ZTF was able to map the accessible localization area in a few hours.

Standard image High-resolution image
Figure 2.

Figure 2. Top: ZTF coverage maps of the two same-day triggers occurring on September 10 (S190910d and S190910h) during O3 of LIGO/Virgo. Given the spatial and temporal overlap of these two GW triggers, some field observations contributed to coverage of both. Bottom: ZTF coverage maps of two NSBH triggers (S190923y and S190930t) during O3. Each square represents a ZTF pointing, and the solid line denotes the latest available GW 90% localization contour.

Standard image High-resolution image
Figure 3.

Figure 3. The ZTF coverage maps of the triggers during the second half of O3 of LIGO/Virgo: S191205ah, S191213g, S200105ae, S200115j, and S200213t. The top and bottom panels show opposite sides of the globe. Each square represents a ZTF pointing, and the solid line denotes the latest available GW 90% localization contour.

Standard image High-resolution image

Table 1. Summary of ZTF Follow-up of 13 GW Triggers in O3

NameFAR (Pt )LocalizationDistanceClass P1 P2 Time LagDepth E(BV)
GW1904251 per 69,000 yr (1%)7461 deg2 156 ± 41 MpcBNS24.13% (45.92%)23.90% (44.62%)0.003 hr21.50.03
S190426c1 per 1.6 yr (58%)1131 deg2 377 ± 100 MpcNSBH52.33% (59.69%)51.57% (57.40%)13.06 hr21.50.34
GW1908141 per 1025 yr (1%)23 deg2 267 ± 52 MpcNSBH88.57% (87.00%)78.37% (70.60%)0.00 hr21.00.02
S190901ap1 per 4.5 yr (14%)14,753 deg2 241 ± 79 MpcBNS56.94% (50.67%)49.39% (42.76%)3.61 hr21.00.03
S190910d1 per 8.5 yr (2%)2482 deg2 632 ± 186 MpcNSBH32.99%(42.50%)31.17% (39.64%)1.51 hr20.30.04
S190910h1 per 0.9 yr (39%)24,264 deg2 230 ± 88 MpcBNS33.26% (42.95%)28.92% (38.44%)0.015 hr20.40.08
S190923y1 per 0.67 yr (32%)2107 deg2 438 ± 133 MpcNSBHNA (38.99%)NA (19.22%)13.73 hr20.10.09
S190930t1 per 2.0 yr (26%)24,220 deg2 108 ± 38 MpcNSBHNA (50.63%)NA (43.42%)11.91 hr21.10.05
S191205ah1 per 2.5 yr (7%)6378 deg2 385 ± 164 MpcNSBHNA (5.68%)NA (4.85%)10.66 hr17.90.04
S191213g1 per 0.89 yr (23%)4480 deg2 201 ± 81 MpcBNS27.50% (0.80%)25.10% (0.09%)0.013 hr20.40.30
S200105aeNA (97%)7373 deg2 283 ± 74 MpcNSBH52.39% (56.40%)43.99% (47.96%)9.96 hr20.20.05
S200115j1 per 1513 yr (1%)765 deg2 340 ± 79 MpcNSBH22.21% (34.92%)15.76% (18.17%)0.24 hr20.80.13
S200213t1 per 1.8 yr (37%)2326 deg2 201 ± 80 MpcBNS72.17% (79.29%)70.48% (76.08%)0.40 hr21.20.19

Note. We list the GW FAR and, in parantheses, the probability that the event is terrestrial (Pt ). We list the total size of the GW localization region, the GW median distance, and the most probable GW classification. We report the integrated probability within the 90% contour of the LALInference sky map, covered by triggered and serendipitous ZTF searches during the first 3 days after merger observed at least once (P1) and probability observed at least twice (P2). In parentheses, we include the coverage based on the BAYESTAR sky map. For some alerts, only BAYESTAR sky maps were made available. All estimates correct for chip gaps and processing failures. We also report the time lag between merger time and the start of ZTF observations (hours), the median depth (AB mag), and the median line-of-sight extinction.

Download table as:  ASCIITypeset image

The location of Palomar Observatory relative to LIGO's quadrupolar antenna sensitivity pattern helps minimize the time lag to respond to triggers in real time (see Figure 4); the latency to first observation was between 11 s and 13.7 hr. (The lowest latency of 11 s was enabled by serendipitous coverage.) As predicted by simulations (Nissanke et al. 2013; Kasliwal & Nissanke 2014), all (but one) GW public alerts were accessible from Palomar Observatory, and more than half could be followed up within 4 hr of the merger. Throughout the paper, we only use enclosed probability based on the LALInference sky map, as it is deemed more accurate (Veitch et al. 2015), when available. The LALInference sky maps were mostly released only after our observations were completed. Hence, the enclosed probability estimates were systematically lower than those estimated by the observation plan based on the initial BAYESTAR sky maps (see Table 1).

Figure 4.

Figure 4. Distribution of response time, defined as the time lag between merger time and earliest possible observation time at a given site, for all 15 BNS/NSBH triggers in O3. We define that observations can begin when at least 30% of the enclosed probability of a GW localization contour is above airmass 2.0 and the Sun is 12° below the horizon at a given site. The size of the filled circles scales with the number of triggers in each time bin. Note that the location of Palomar Observatory enables a response to more triggers than CTIO overall (13 vs. 10 triggers) and a larger number (seven vs. two triggers) within 4 hr after merger.

Standard image High-resolution image

The process for triggering ToO observations for a survey system like the ZTF differs from traditional telescopes, as it involves halting the ongoing survey observations and scheduling observations of only certain fields as selected by an observation plan. Observation plans are generated by gwemopt, 60 a code base for optimizing galaxy-targeted and synoptic searches within GW sky maps (Coughlin et al. 2018, 2019a). Over the course of O3, we implemented several improvements to the existing code framework, including additional features that allow us to strategically handle sky maps spanning thousands of square degrees, slice sky maps by R.A. and schedule slices separately, and balance coverage in multiple filters. These improvements, among others, are described in Almualla et al. (2020). All of our triggered follow-up of GW events, gamma-ray bursts (GRBs; T. Ahumada et al. 2020, in preparation), and high-energy neutrino events (Stein et al. 2020) occurs through a user interface called the GROWTH ToO Marshal, 61 a database designed to ingest GCN circulars, display event properties and sky maps, design plans, trigger observations, query for candidates within the observed region, and retrieve summary statistics for completed observations, including probability covered and median depth (Coughlin et al. 2019a; Kasliwal et al. 2019a).

3. Investigating Candidate Counterparts

Our candidate vetting methodology has continued to improve over the past few years, starting with Fermi afterglow searches (Singer et al. 2015), to BBH searches in O1 (Kasliwal et al. 2016), to BNS and NSBH searches in O3 (Coughlin et al. 2019a; Anand et al. 2020). We graphically summarize the candidate vetting process in Figure 5. Here we first discuss the prompt vetting procedure that quickly led to a GCN circular announcing candidate counterparts (Section 3.1). Next, we discuss follow-up of the candidates to discern their nature (Section 3.2). Finally, we discuss a deeper offline search to look for any missed candidates (Section 3.3).

Figure 5.

Figure 5. Flowchart to show how our candidate vetting funneled from a large number of spatially and temporally consistent alerts, to a smaller number of candidates that deem human vetting, to an even smaller number of candidates that warrant detailed follow-up characterization over the course of O3.

Standard image High-resolution image

3.1. Initial Transient Vetting

For each of the 13 GW triggers followed up by ZTF, we systematically identified transient candidates within the localization region and ruled them out using various metrics. Below, we summarize the transient filtering process and results from our candidate vetting.

The GROWTH team has three independent database systems to retrieve interesting objects in real time: the GROWTH Marshal (Kasliwal et al. 2019a), the Kowalski 62 system (Duev et al. 2019), and the Alert Management, Photometry and Evaluation of Lightcurves (AMPEL) system (Soumagnac & Ofek 2018; Nordin et al. 2019). Each platform retrieves a stream of AVRO packet alerts (Patterson et al. 2019) containing significant object detections identified by the ZTF image subtraction pipeline, defined as a >5σ change in brightness relative to a reference image (Masci et al. 2018). Each of these objects undergoes a series of filtering steps in order to identify candidates that could be interesting to pursue for follow-up. The following criteria were common for all three queries.

  • 1.  
    Positive subtraction. The object must have brightened relative to the reference image.
  • 2.  
    Astrophysical. The object must have a real bogus (rb) score >0.25 or a deep learning (drb) score >0.8 (Duev et al. 2019; Mahabal et al. 2019) for it to be considered astrophysical.
  • 3.  
    Not stellar. The object must be >2'' away from a cataloged point source in the PanSTARRS Point Source Catalog (Tachibana & Miller 2018).
  • 4.  
    Far from a bright source. The object must be at least 20'' away from a bright (mAB < 15 mag) star to avoid blooming artifacts.
  • 5.  
    Not moving. The object must have at least two detections separated by at least 15 minutes to reject asteroids (moves <4'' hr−1)
  • 6.  
    No previous history. The object must not have any historical detections in the ZTF alert stream prior to the GW merger time.

While the GROWTH Marshal queried all fields triggered as part of the ToO search, the Kowalski and AMPEL queries searched for candidates in both serendipitous and triggered data within the 95% contour of the latest sky map that was available. The AMPEL query 63 had further image quality cuts performed to reject poor subtractions based on morphology, an additional cut based on proximity to known solar system objects, and another cut based on cross-matching to the Gaia Data Release 2 (DR2) catalog and PS1 to identify likely stellar sources.

All candidates that passed the filtering criteria were saved to the GROWTH Marshal for further vetting in real time by a dedicated team of scanners. If a transient was consistent with the nucleus of a galaxy and the mid-infrared colors (based on the Wide-field Infrared Survey Explorer (WISE) catalog; Wright et al. 2010) of the host galaxy were consistent with active galactic nuclei (AGNs), the candidate was deemed unrelated.

All viable candidates were promptly announced to the worldwide community via GCN circulars, and many teams (not only GROWTH) triggered follow-up observations for many of our candidates. 64 Using the GROWTH Marshal system, we prioritized and triggered follow-up of candidates that exhibited rapid photometric evolution (faster than 0.3 mag day−1), showed red colors, or were close to a host galaxy with a redshift consistent with the GW distance constraint.

3.2. Examining Promising Candidate Counterparts with Additional Follow-up

We now briefly describe how we ruled out the association between vetted counterpart candidates and the GW event. A detailed account of every candidate announced via GCN is in Appendix B.

The GROWTH team obtained follow-up with the following facilities to characterize the photometric and/or spectroscopic evolution: the Liverpool Telescope (LT; Steele et al. 2004), Lowell Discovery Telescope (LDT, 65 formerly known as the Discovery Channel Telescope), Las Cumbres Observatory (LCO; Brown et al. 2013), Apache Point Observatory (APO; Huehnerhoff et al. 2016), Kitt Peak EMCCD Demonstrator (KPED; Coughlin et al. 2019b), Lulin One-meter Telescope (LOT; Huang et al. 2005), GROWTH-India telescope (GIT; 66 V. Bhalerao et al. 2020, in preparation), Palomar 60 inch telescope (P60; Cenko et al. 2006), Palomar 200 inch Hale Telescope 67 (P200), Keck Observatory, 68 Gemini Observatory, 69 Southern African Large Telescope 70 (SALT), Himalayan Chandra Telescope 71 (HCT), and Gran Telescopio Canarias 72 (GTC). Figures 6 and 7 illustrate examples of follow-up by the GROWTH team on some ZTF candidates. The specific instrument configurations and data reduction methods are described in Appendix A.

Figure 6.

Figure 6. Collage of spectra taken during our GW follow-up in O3, one from each spectroscopic facility. The spectra displayed include six Type II SNe, one AGN, and one Type Ia SN and were taken with LT+SPRAT and GTC+OSIRIS in Roque de los Muchachos, Spain; P200+DBSP on Palomar Mountain, USA; Keck1+LRIS and Gemini+GMOS-N on Maunakea, USA; SALT+RSS in Sutherland, South Africa; HCT+HFOSC in Hanle, India; and LDT+Deveny in Happy Jack, USA.

Standard image High-resolution image
Figure 7.

Figure 7. Collage of candidate counterparts found during real-time searches. We show a 7'' × 7'' region with north up and east left for the discovery (NEW) and reference (REF) images. We also show the light curve of the candidate, where the u-, g-, r-, i-, and z-band data are shown in blue, green, red, yellow, and black respectively. The ZTF data are presented with filled circles, while data from the LT, GIT, Keck, WHT, and LCO are presented as filled diamonds, squares, elongated diamonds, crosses, and pentagons, respectively. Absolute magnitude is shown for the candidates with a known redshift, and upper limits are shown as inverted triangles. We also display the spectra of the transient where available and mark the hydrogen and helium lines for ZTF19aasmddt (SN II), the H and He ii features of ZTF19abvionh (CV), and the Mg i and Mg ii lines for ZTF19abvizsw (long GRB afterglow).

Standard image High-resolution image

The follow-up observations include both photometric and spectroscopic data. Moreover, the association of a candidate with a GW trigger was rejected if its properties fell into one or more of the categories described as follows.

  • 1.  
    Inconsistent spectroscopic classification. We ruled out candidates that could be spectroscopically classified as SNe, AGNs, cataclysmic variables (CVs), and other flare stars. We used SNID (Blondin & Tonry 2007) and dash (Muthukrishna et al. 2019) to classify the SNe and AGNs found in our searches. The CVs and variable stars often showed hydrogen features at zero redshift.
  • 2.  
    Inconsistent distance. We ruled out candidates whose spectroscopic redshift was not consistent with the GW distance within 2σ. We cross-matched the transient positions with the Census of the Local Universe (CLU; Cook et al. 2019) galaxy catalog and the NASA Extragalactic Database (NED) to look up host redshifts where available. We also cross-matched the candidates against the Photometric Redshifts Legacy Survey (PRLS; Zhou et al. 2020) catalog and reported the photometric redshifts when the spectroscopic redshift was unavailable.
  • 3.  
    Slow photometric evolution. As kilonovae are expected to evolve faster than SNe, we ruled out candidates that evolved slower than 0.3 mag day−1. We used ForcePhot 73 (Yao et al. 2019), a forced photometry package, to examine the transient light curves. To quantify the evolution of a given transient, we define the parameter αf = Δmt [mag day−1], where f corresponds to the filter used to determine the variation in magnitude (Δm) over time (Δt). A positive α indicates a fading source, while a negative α describes a rising source. The baseline (Δt) is defined to be the number of days it takes an object to rise from its discovery to its peak magnitude (α < 0) or the number of days it takes the transient to fade from peak to undetectable by ZTF (α > 0). We used a minimum time baseline of 3 days to compute slopes.
  • 4.  
    Outside of the latest LALInference map. The majority of the candidates were selected and announced via GCN based on the promptly available BAYESTAR map (Singer & Price 2016). When the LALInference map was made available, if a candidate was outside the 90% probability contour, we rejected it.
  • 5.  
    Artifacts. Most of the ZTF ghosts and artifacts are well known (Bellm et al. 2018; Masci et al. 2018) 74 and masked automatically. Additionally, we take further precautions by ignoring transients close to bright stars in our initial vetting. However, for example, our extensive analysis revealed a subtle gain mismatch in the reference images that posed as a faint and fast transient (see discussion related to ZTF19aassfws in Appendix B). All references for ToOs were rebuilt after this artifact was identified.
  • 6.  
    Asteroids. Sometimes slow-moving asteroids, especially near stationary points, can mimic a fast-fading transient (Jedicke et al. 2016). For these objects, either a more careful inspection of the centroids or movement in follow-up imaging served as the reason for rejection.
  • 7.  
    Previous activity. Candidates were rejected if they showed previous detections prior to the GW merger time in other surveys, e.g., the Catalina Real Time Survey (CRTS; Djorgovski et al. 2011), Palomar Transient Factory (PTF; Law et al. 2009), intermediate Palomar Transient Factory (iPTF; Cao et al. 2016; Masci et al. 2017), and PS1 (Tachibana & Miller 2018).

Some candidates prompted panchromatic follow-up. We followed up five candidates in the ultraviolet and X-ray with the Neil Gehrels Swift Observatory (see the Appendix for details). We followed up two candidates in the radio with the Arcminute Microkelvin Imager (AMI) and one with the Karl G. Jansky Very Large Array (VLA; see the Appendix for details). All candidates, grouped by GW trigger, are listed in Tables 210, along with their respective rejection criteria.

Table 2. List of Candidate Counterparts to S190426c

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19aasmftmAT2019sne325.900447977.83156340.156 [s] g = 18.78 ± 0.19SN Ia
ZTF19aaslzjfAT2019snh320.626298265.81345160.028 [s] g = 19.45 ± 0.14SN Ia
ZTF19aasmddtSN2019fht299.250559.70167480.028 [s] g = 18.6 ± 0.11SN II
ZTF19aasmekbAT2019snl300.601398714.2873159 g = 17.33 ± 0.04 αg  = 0.24
ZTF19aassfwsAT2019fuc298.667861161.2400121 r = 21.35 ± 0.21Artifact
ZTF19aaslszpAT2019snj301.343462853.39904770.084 [s] g = 20.12 ± 0.15 αr  = 0.01, AGN
ZTF19aaslolfAT2019snn288.783853979.4357187 r = 21.12 ± 0.18 αr  < 0.01, AGN, PS1
ZTF19aaslozuAT2019snr306.314498165.1093759 r = 20.59 ± 0.21 αg  = 0.06, AGN, PS1
ZTF19aasshpfAT2019snt315.476865170.2055771 r = 19.99 ± 0.23 αr  < 0.01
ZTF19aaslphiAT2019sno297.380997761.9605925 r = 21.26 ± 0.20 αr  = −0.08
ZTF19aaslpdsAT2019snq306.262518661.521461 r = 19.9 ± 0.14 αr  = 0.03
ZTF19aasmzqfAT2019aaco353.520491178.9577781 r = 19.86 ± 0.09 αr  = 0.01
ZTF19aaslzfkAT2019snd308.96827172.3536353 g = 20.0 ± 0.26 αg  = −0.02
ZTF19aaslvwnAT2019snf299.05984646.463559 g = 20.68 ± 0.17 αr  < 0.01
ZTF19aasmdirAT2019sng300.23600079.504002 g = 20.07 ± 0.11 αr  < 0.01

Download table as:  ASCIITypeset image

Table 3. List of Candidate Counterparts to S190901ap

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19abvizswAT2019pim279.4728261.4979841.26 [s] r = 19.89 ± 0.16Long GRB afterglow
ZTF19abwvalsAT2019pni73.25055512.693030.091 [s] r = 18.96 ± 0.30SN Ia
ZTF19abvixoyAT2019pin279.55297227.420935 r = 18.93 ± 0.10 αr  = 0.23, CV
ZTF19abvionhAT2019pip253.75092414.051330.0985 [s] g = 20.57 ± 0.31 αg  = 0.10, CV
ZTF19abwsmmdAT2019pnc22.666409−19.7124050.0972 [s] g = 19.78 ± 0.18 αg  = 0.03
ZTF19abvislpAT2019pnx220.34970854.1511530.10 [s] r = 19.98 ± 0.20 αr  = 0.05
ZTF19abxdvcsAT2019qev252.01047741.920087 g = 20.64 ± 0.28 αg  = 0.03

Download table as:  ASCIITypeset image

Table 4. List of Candidate Counterparts to S190910d

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19abyfhovAT2019pvu260.69342911.4244360.13 [s] g = 19.92 ± 0.22SN Ia
ZTF19abyfbiiAT2019pvz255.4416211.6022540.118 [s] r = 19.60 ± 0.16SN Ia 91T
ZTF19abyfazmAT2019pwa290.53587648.0691620.38 [s] g = 17.53 ± 0.03CV, αr  = 0.09
ZTF19abyfhaqAT2019pvv303.14859349.3926070 [s] g = 18.01 ± 0.31 αr  = 0.15, Galactic

Download table as:  ASCIITypeset image

Table 5. List of Candidate Counterparts to S190910h

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19abyhezaAT2019pxi332.91339160.3958160 [s] r = 16.14 ± 0.13CV, αr  = 0.08
ZTF19abyhhmlAT2019pxj339.69163555.9366490 [s] r = 17.36 ± 0.12CV, αr  = 0.13
ZTF19abyirjlAT2019pxe30.47117630.733550.1 [s] r = 19.45 ± 0.13SN Ia
ZTF19abyjcomAT2019pxk32.93635312.033344 r = 19.63 ± 0.24Artifact
ZTF19abyjconAT2019pxl33.25246912.472604 r = 19.87 ± 0.19Artifact
ZTF19abyjcooAT2019pxm33.08971212.297698<0.03 [p] r = 19.95 ± 0.24 αr  = 0.06
ZTF19abyjfiwAT2019pxn39.18680734.647299 g = 20.13 ± 0.21 αr  < 0.01
ZTF19abygvmpAT2019pzg28.97625841.0909790.049 [s] r = 20.13 ± 0.25SN II
ZTF19abyiwiwAT2019pzi340.52144155.220244 r = 18.58 ± 0.30 αg  = 0.20
ZTF19abylleuAT2019pyu355.338225−23.450706 r = 19.19 ± 0.24 αg  = 0.03
ZTF19abymhyiAT2019pzh340.8557234.186344<0.03 [p] g = 20.36 ± 0.23 αg  = −0.13

Download table as:  ASCIITypeset image

Table 6. List of Candidate Counterparts to S190923y

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19acbmoplAT2019rob114.04020728.487381<0.03 [p] g = 19.64 ± 0.27 αg  = 0.01

Download table as:  ASCIITypeset image

Table 7. List of Candidate Counterparts to S190930t

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19acbpqlhAT2019rpn319.921663637.52207210.026 [s] g = 19.47 ± 0.18SN II
ZTF19acbwaahAT2019rpp162.327748922.98273020.031 [s] r = 17.61 ± 0.08SN Ia
ATLAS19wynAT2019rpj339.836739731.49162620.0297 [s] g = 19.32 ± 0.11SN II

Download table as:  ASCIITypeset image

Table 8. List of Candidate Counterparts to S191205ah

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19acxpnvdAT2019wkv175.3618518.241201<0.03 [p] i = 19.58 ± 0.20 αg  = 0.06
ZTF19acxoywkAT2019wix149.89614813.9150510.05 [s] r = 19.69 ± 0.21 αg  = −0.15
ZTF19acxoyraAT2019wid153.0937758.6093300.09 [s] r = 19.14 ± 0.19 αg  = 0.05
ZTF19acxpwlhAT2019wiy155.71297023.603273<0.24 [p] g = 19.77 ± 0.19 αr  = 0.07
ZTF19acyifljAT2019wmy152.89987423.9438430.081 [s] r = 20.05 ± 19.63SN Ia
ZTF19acxowrrAT2019wib154.87145827.8837380.05 [s] r = 19.00 ± 0.13SN II
ZTF19acyitgaAT2019wmn159.7968305.1619420.071 [s] r = 19.20 ± 0.16SN Ia

Download table as:  ASCIITypeset image

Table 9. List of Candidate Counterparts to S191213g Reported in GCN 26424 and 26437

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF19acykzskSN2019wqj32.90454734.0413460.021 [s] g = 19.0 ± 0.06SN II
ZTF19acymaruAT2019wnh80.461954−19.2664010.167 [s] r = 19.92 ± 0.16SN Ia
ZTF19acykzspAT2019wne28.35914431.8010120.16 [s] r = 20.08 ± 0.31SN Ia
ZTF19acyfohaAT2019wkl85.104365−18.0976300.04 [s] g = 17.31 ± 0.08SN Ia
ZTF19acymcwvAT2019wni36.24892047.4978440.09 [s] r = 19.76 ± 0.24SN Ia
ZTF19acykwsdAT2019wnl33.08807241.388708 r = 19.3 ± 0.25Artifact
ZTF19acylvusAT2019wnk83.631136−19.4202440.104 [s] r = 19.45 ± 0.24SN Ia
ZTF19acymcnaAT2019wnn33.20789940.9997260.138 [s] r = 20.48 ± 0.22 αr  = −0.01, AGN
ZTF19acykyquAT2019wre38.81964638.319851 g = 20.94 ± 0.21Stellar—PS1-DR2
ZTF19acykyrzAT2019wrf36.06497238.080388 g = 20.83 ± 0.17Stellar—PS1-DR2
ZTF19acykyzjAT2019wrg36.05662451.367126 g = 19.75 ± 0.20 αr  = −0.03
ZTF19acykzfyAT2019wrh43.11519441.660303 g = 20.34 ± 0.20Stellar—PS1-DR2
ZTF19acyldumAT2019wrn79.681883−7.185279 g = 19.41 ± 0.13PS1-DR2 detection
ZTF19acyldunAT2019wrt79.199993−7.4786820.057 [s] g = 19.42 ± 0.17 αr  = 0.09, LBV
ZTF19acymapaAT2019wro78.207321−5.948936 g = 18.54 ± 0.22 αr  = −0.06
ZTF19acymaxuAT2019wrp82.952485−26.694523<0.13 [p] r = 18.65 ± 0.06 αr  = 0.03
ZTF19acymixuAT2019wrr90.91393660.7282450.14 [s] r = 19.66 ± 0.32SN Ia
ZTF19acymlhiAT2019wrs91.592426−18.804727 r = 17.99 ± 0.26 αr  = −0.17

Note. The candidates for which photometric evolution has been calculated with a baseline (Δt) between 2 and 3 days are marked with .

Download table as:  ASCIITypeset image

Table 10. List of Candidate Counterparts to S200213t

NameTNSR.A.Decl.Host/RedshiftDiscov. MagRejection Crit.
ZTF20aamvqxlAT2020ciy29.23792153.6688820.102 [s] g = 19.44 ± 0.17SN Ia
ZTF20aamvnthAT2020cjb18.33772149.6455390.061 [s] g = 19.95 ± 0.17SN II
ZTF20aamvoxxAT2020cjg39.39909526.9206160.097 [s] g = 19.47 ± 0.12SN Ia
ZTF20aamvtipAT2020cje38.08253827.8100940.151 [s] g = 20.3 ± 0.16SN Ia
ZTF20aamvnatAT2020ciz27.23955256.3545790.0 [s] g = 17.42 ± 0.05CV
ZTF20aamvmzjAT2020cja27.18919551.430481 g = 19.46 ± 0.11 αr  = 0.04
ZTF20aamvoehAT2020cjc33.50201138.9363170.14 [s] g = 20.25 ± 0.12SN Ia
ZTF20aamvoddAT2020cjf37.48238750.3194270.0 [s] g = 18.92 ± 0.11Stellar flare
ZTF20aanakwbAT2020cls6.521539142.7737224 g = 20.75 ± 0.27Stellar
ZTF20aanaltdAT2020clt9.740671643.44106950.2 [s] g = 20.57 ± 0.23SN Ia
ZTF20aanakskAT2020clu19.435639931.1744954<0.03 [p] g = 20.27 ± 0.10PS1
ZTF20aanallxAT2020clv6.366660851.2233877 g = 20.58 ± 0.28Outside the LALInfernce map
ZTF20aanaoyzAT2020clw24.594099523.38225690.276 [s] g = 21.28 ± 0.27SN Ia
ZTF20aamvpvxAT2020clx31.940298120.03061470.074 [s] g = 19.95 ± 0.14SN II
ZTF20aanamcsAT2020crc13.743334543.49802450.093 [s] g = 20.98 ± 0.28SN II
ZTF20aanakgeAT2020crd12.630623341.4841780.1272 [s] g = 20.38 ± 0.33SN Ia
ZTF20aanaqheAT2020cre17.042579645.5256583 g = 20.63 ± 0.27 αg  = −0.08
ZTF20aanakesAT2020cly2.098544338.0441264 g = 20.79 ± 0.21PS1
ZTF20aanakcdAT2020cmr8.157122341.31563710.077 [s] g = 20.48 ± 0.17SN IIn

Download table as:  ASCIITypeset image

3.3. Candidates from Deeper Offline Searches

We complemented our real-time analysis described above with a deeper offline search by relaxing the selection criteria (e.g., requiring only one detection instead of two). The following steps describe our offline search.

  • 1.  
    We used Kowalski to query the ZTF database looking for any source (i) located within 95% of the most updated sky map, (ii) never detected before the merger time, (iii) with at least one detection within 72 hr of merger, (iv) with the last detection occurring within 10 days of the first detection, and (v) passing real/bogus thresholds of rb > 0.5 and drb > 0.8 (or braai > 0.8; Duev et al. 2019). Further details on the selection criteria will be described in I. Andreoni et al. (2020, in preparation).
  • 2.  
    Forced point-spread function (PSF) photometry was performed at the location of each transient candidate using ForcePhot, setting a detection threshold of signal-to-noise ratio (S/N) > 3, where the images were available.
  • 3.  
    The flux measured using forced photometry was stacked nightly in each band, allowing us to become sensitive to fainter sources when multiple images were available on the same night.
  • 4.  
    The rising and fading rates were computed in each band with a linear fit before and after the brightest data point of each light curve. A time baseline of >3 hr was required for the fit to be performed.
  • 5.  
    Candidates were selected with a fading rate more rapid than 0.3 mag day−1 or rising rate faster than 1 mag day−1. We rejected candidates still detected after 6, 12, and 14 days after the merger time in the g, r, and i bands, respectively. More details are given in I. Andreoni et al. (2020, in preparation).

The Kowalski query initially returned 8026 sources for the 13 GW triggers. Applying all of the selection criteria described above, 453 candidates survived the automatic cuts. Of these, 21 had at least two ZTF alerts, and 432 had only one ZTF alert (additional detections were recovered by forced photometry and stacking).

Of the 21 sources with at least two detections in the ZTF alert stream, only five candidates passed visual inspection of the images and light curves: ZTF19acbxacj was an AGN candidate (Assef et al. 2018; Bailer-Jones et al. 2019); ZTF19abwsfsl was a cataloged CV (Gaia Collaboration 2018); ZTF19acbqtue was followed up with the Gemini Multi-Object Spectrograph (GMOS-N), and a quiescent source was found at g = 24.69 ± 0.07 mag with a color g − i = 1.89 mag, consistent with an M dwarf (West et al. 2011); ZTF19abyndjf was a fast-evolving transient without an obvious host galaxy; and ZTF19acbwtmt was hostless and had a previous detection in the PS1-DR2 catalog from 2012 (see Figure 8). For the last two candidates, upper limits between the GW merger time and the first transient detection disfavor their multimessenger association with S190930t or S190910d, respectively (see Figure 8).

Figure 8.

Figure 8. Collage of candidate counterparts found in deeper offline searches. Each candidate in the top row has two or more ZTF alerts: ZTF19acbqtue was ruled out, as we found a quiescent stellar source with GMOS-N; ZTF19abyndjf does not have a galaxy in its vicinity; and ZTF19acbwtmt had archival activity in PS1-DR2. Each candidate in the bottom row had only one ZTF alert but was flagged as interesting after performing forced photometry. These three candidates are nuclear transients that are ruled out, as their absolute magnitudes are brighter than what is expected for kilonovae.

Standard image High-resolution image

Of the 432 sources with only one detection in the ZTF alert stream, only nine candidates passed the visual inspection of the images and light curves. Most other candidates were ruled out as stellar flares, image subtraction artifacts, asteroids, or sporadic nuclear variability. Of these nine candidates, six had photometric or spectroscopic redshifts of the host galaxy too far to be consistent with the GW distance. All three remaining candidates were found during follow-up of S190901ap: ZTF19abvpeir, ZTF19abvozxv, and ZTF19abvphxm. All three are likely SNe or AGNs, given that their absolute magnitudes at the distance of their putative hosts are between −18.0 and −18.8 mag and their locations are consistent with the Galaxy nuclei. We show some light curves and host galaxies in Figure 8.

In summary, all candidates were ruled out as possible kilonovae in both the real-time and offline analyses.

4. Discussion

We start by treating all triggers as bona fide astrophysical events regardless of FAR, assuming that kilonovae accompanying BNS and NSBH mergers are drawn from a common population, and analyzing the implications of zero kilonova detections. Later, we relax these assumptions. Since kilonova models have a wide range of estimates depending on several intrinsic and extrinsic parameters (e.g., ejecta mass, ejecta velocity, lanthanide fraction, viewing angle, remnant lifetime), we took a model-independent approach toward constraining the luminosity function.

Serving as our benchmark is GW170817. The ZTF observations were taken as g- and r-band pairs, and GW170817 was discovered at an i-band magnitude of 17.3 mag about 10.8 hr after merger (Coulter et al. 2017). Compiling and fitting all published data in the g and r bands for GW170817 in the first 3 days after merger (Andreoni et al. 2017; Arcavi et al. 2017; Coulter et al. 2017; Cowperthwaite et al. 2017; Díaz et al. 2017; Drout et al. 2017; Evans et al. 2017; Pian et al. 2017; Smartt et al. 2017; Utsumi et al. 2017; Valenti et al. 2017; Pozanenko et al. 2018), we find that GW170817 had a decline rate of 0.9 mag day−1 in the r band and 1.3 mag day−1 in the g band. Extrapolating this decline rate to merger time and correcting for line-of-sight extinction, GW170817 may have peaked at −16.54 mag in the r band and −16.69 mag in the g band (we caution that some kilonova models predict a finite rise time). Here we choose to compare the ZTF limits to an average of these two filters, i.e., −16.6 mag at peak and a decline rate of 1 mag day−1.

4.1. Joint Probability of Zero Detections

We estimate the joint probability of zero kilonova detections as a product of (1 − qi ) terms, where qi is the enclosed probability for each event as listed in Table 1 (see the sixth column; we used LALInference probability where available). If we were sufficiently sensitive to finding kilonovae in all 13 GW events, the joint probability of zero detections would be only 0.017%. However, each merger had a different observed depth, observed cadence, and GW distance estimate and thus a different sensitivity to detecting kilonovae.

First, we use the median image depth for each trigger and the median GW distance to each trigger to compute a median absolute magnitude sensitivity limit. We correct the median absolute magnitude for the median extinction along the line of sight. In Figure 9, in each luminosity bin, we compute the joint nondetection probability only for the subset of events for which the ZTF observations were sufficiently sensitive. We find that ZTF follow-up of four (six) GW events had a sensitivity deeper than −16.0 mag (−16.6 mag), and the joint nondetection probability is only 4.5% (0.34%). Moreover, three of the four (four of the six) had a preliminary BNS classification, and for all three, the ZTF follow-up began within 4 hr of merger (see Table 1).

Figure 9.

Figure 9. Joint probability of zero detections as a function of absolute magnitude of the kilonova after correcting for line-of-sight extinction. Solid lines represent rough estimates from median estimates. Filled circles represent estimates that take into account the spatial variation in depth, GW distance, and GW probability.

Standard image High-resolution image

Second, we use injection and recovery of fake sources to better quantify both the degree of variation in the depths of individual exposures and the spatial variation in the GW distance estimates. We use an open-source tool called simsurvey 75 (Feindt et al. 2019). As input, the tool takes a list of ZTF pointings (observation time, R.A., decl., limiting magnitude, filters, processing success of each CCD quadrant). We inject 10,000 sources distributed according to the 3D GW sky map probability distribution in each luminosity bin (50 bins between −10 and −20 mag). Initially, we assume that each kilonova stays at a constant luminosity between the merger time and 3 days after merger. We require a single observation at the necessary depth for recovery. In addition to losing sources in unobserved fields, we lose sources that land in ZTF chip gaps, chips that failed processing, or chips that were less sensitive due to higher line-of-sight Galactic extinction. This tool does not take into account any detections that would be lost to inefficiency in the software pipeline.

The recovery fraction for each event is shown in Figure 10. We convert this to a joint nondetection probability estimate by multiplying (1 − pi ) in each luminosity bin and overlay this as discrete points on the median estimates above in Figure 9. We find consistent results; the joint probability of zero detections at −16.1 mag (−16.6 mag) is only 4.2% (0.8%). If we separate the NSBH and BNS populations, the joint nondetection probability at −16.6 mag is 9.7% for NSBH and 7.9% for BNS. This is not surprising, as the BNS triggers were, on average, closer than the NSBH triggers. We note that this application of simsurvey is different compared to previous applications for SN rates, which were uniform in volume. Taking into account the exact 3D GW sky map is more accurately representative of our success in searching for the counterpart to a GW source on an event-by-event basis.

Figure 10.

Figure 10. Event-by-event recovery efficiency using simsurvey as a function of absolute magnitude for BNS (left panel) and NSBH (right panel) mergers. The recovery efficiency corresponds to the number of kilonovae detected divided by the total number of kilonovae injected. Kilonovae were injected according to the 3D probability distribution of the sky map.

Standard image High-resolution image

Third, in addition to spatial variations in depth and distance, we take into account the possible time variations in the light curves of kilonovae (Figure 11). The time window for our observations is limited to within 3 days of merger. We relax the constant luminosity assumption above and inject kilonovae into simsurvey that fade linearly between zero and 1 mag day−1. In Figure 11, we color-code the recovery efficiency for a given peak luminosity and photometric decay rate in any filter (g or r band). Any slice of this plot can be converted to a joint probability of zero detections as a function of absolute magnitude. We compare to the GW170817 benchmark of an extrapolated peak of −16.6 mag day−1 and a fade rate of 1 mag day−1. We find a joint probability of zero detections of 7%.

Figure 11.

Figure 11. Composite efficiency map using simsurvey assuming a linear model for the kilonova with a peak absolute magnitude and fixed decay rate. The color-coding shows the recovery efficiency, or the number of recovered kilonovae within observed regions divided by the total number of kilonovae injected in the sky map. Based on an analysis of a compilation of data from GW170817 (Andreoni et al. 2017; Coulter et al. 2017; Cowperthwaite et al. 2017; Díaz et al. 2017; Drout et al. 2017; Evans et al. 2017; Pian et al. 2017; Smartt et al. 2017; Utsumi et al. 2017; Valenti et al. 2017; Arcavi 2018; Pozanenko et al. 2018), we compute an average extrapolated peak magnitude of ∼−16.6 and a decay rate of ∼1 mag day−1. If all kilonovae are like GW170817, the joint probability of zero detections is 7%.

Standard image High-resolution image

Fourth, in addition to spatial and time variations, we inject kilonova models into simsurvey and calculate the recovery fraction. We use the best fit to GW170817 from the kilonova model grid in Dietrich et al. (2020) computed using the radiative transfer code POSSIS (Bulla 2019). This model fit assumes a rise time, color evolution, and viewing angle of GW170817. The joint nondetection probability is 30%. Even if all kilonova ejecta parameters were similar to GW170817, the viewing angle would be different for different events. Assuming random viewing angles drawn from a distribution uniform in cos(θ), we inject a model grid and find that the joint nondetection probability is 49%. We caution that the model used here underestimates the early g-band flux of GW170817 by 0.3 mag; thus, the recovery fraction estimated here could also be underestimated.

4.2. Constraining the Kilonova Luminosity Function

Next, we consider the implications of the zero-detection probability function on the underlying luminosity function. Let us say the luminosity function dictates that a fraction fb of kilonovae are brighter than a given absolute magnitude. Then,

where CL is the confidence level and pi is the event-by-event probability of detection. At a given absolute magnitude, we compute pi as the recovery fraction from the simsurvey injections for the fading and flat light-curve evolution estimates discussed above that take into account the spatial variation in distance, depth, and enclosed probability. Solving for fb at a 90% confidence level, we plot our results in Figure 12. At the bright end, we find that no more than ≈40% of kilonovae can be brighter than −18 mag. At the faint end, our observations place no constraints on the luminosity function fainter than −15.5 mag. The luminosity of GW170817 at the merger time is unknown, and various models predict diverse rates of evolution in that first day after merger. As discussed above, we use an extrapolated peak of −16.6 mag and a fade rate of 1 mag day−1 for GW170817 as a benchmark. We find that no more than <57% (<89%) of kilonovae could be brighter than −16.6 mag for the flat (fading) light-curve assumptions.

Figure 12.

Figure 12. Constraints on the underlying luminosity function of kilonovae represented as the maximum allowed fraction of kilonovae brighter than a given peak absolute magnitude. Constraints are derived at a 90% confidence level. We show constraints assuming flat photometric evolution (orange squares) and fading by 1 mag day−1 (green asterisks). We also show the event-by-event constraint based on a median estimate (yellow circles, dotted line). We correct this median estimate by the probability that the GW alert was terrestrial (red circles, dotted line). We compare to a model grid published in Kasen et al. (2017; dashed black line) and find that the limiting line suggests that some kilonovae must either have Mej < 0.03 M or Xlan > 10−4. The limiting line (blue dashed line) for another model grid (Bulla 2019; Dietrich et al. 2020) suggests that some kilonovae must be fainter than GW170817 with Mej,dyn < 0.005 M, Mej,pm < 0.05 M, or ϕ > 30°.

Standard image High-resolution image

The GW triggers had a very wide range of FARs. Weighting by the available low-latency values for the terrestrial probability (ti ), we fold this into our luminosity function constraint as

In Figure 12, we show that the resulting constraints on fb (red line) are worse only by a difference of ≈10%.

Next, we investigate the implications of this constraint on the kilonova parameter space. There are no theoretical luminosity functions available in the literature that we can directly compare to. A model grid is available (Kasen et al. 2017) as a function of three parameters: ejecta mass Mej, ejecta velocity vej, and lanthanide fraction Xlan. The best-fit model to GW170817 from Kasen et al. (2017) suggested two components: a blue kilonova (0.025 M, 0.3 c, 10−4.5) and a red kilonova (0.04 M, 0.1 c, 10−2). The blue component dominates at an early time and is more relevant to the ZTF searches described in this paper. Comparing to our luminosity function constraints, we find that our limits suggest that a wide range of parameters are allowed, e.g., Mej = [0.03, 0.1] M, vej = [0.05, 0.3] c, and Xlan = [10−5, 10−4]; stricter distributions that yield a brighter kilonova population (e.g., higher ejecta mass or lower lanthanide fraction) are not allowed. Thus, some kilonovae must have Mej ≤ 0.03 M or Xlan > 10−4 to be consistent with the ZTF constraints.

Similarly, we compare our luminosity function constraints to the kilonova grid from Dietrich et al. (2020) computed using the radiative transfer code POSSIS (Bulla 2019). In addition to the observer viewing angle, this grid depends on three parameters: the dynamical ejecta mass (Mej,dyn), the postmerger wind ejecta mass (Mej,pm), and the half-opening angle of the lanthanide-rich ejecta component (ϕ). A model with Mej,dyn = 0.005 M, Mej,pm = 0.05 M, and ϕ = 30° provides a good fit to GW170817 (see Figure 8 of Dietrich et al. 2020). As shown in Figure 12, our constraints suggest that some kilonovae must be fainter than GW170817, i.e., must have either Mej,dyn < 0.005 M, Mej,pm < 0.05 M, or ϕ > 30°.

5. Conclusions and Way Forward

In summary, the ZTF coverage (excluding weather-impacted S191205ah) spanned enclosed probabilities from 22% to 89%, median depths from 20.1 to 21.5 mag, and time lags between merger and the start of observations from 11 s to 13.7 hr. The follow-up by the GROWTH team comprised 340 UltraViolet/Optical/InfraRed (UVOIR) photometric points, 64 OIR spectra, and three radio images. Additionally, many other teams also followed up ZTF candidates. Thanks to the extensive follow-up, all candidate counterparts were ruled out.

The GW triggers had localization areas ranging from 23 to 24,264 deg2, distances from 108 to 632 Mpc, and FARs from 1.5 to 10−25 yr−1. Assuming that all GW alerts were astrophysical, we conclude that the joint probability of zero detections is only 4.2% if all kilonovae are at least as bright as GW170817 at discovery. Furthermore, assuming kilonovae from BNS and NSBH mergers are drawn from a common population, we find that no more than <57% (<89%) of kilonovae could be brighter than −16.6 mag for the flat (fading by 1 mag day−1) assumptions respectively at 90% confidence.

The median time lag of the ZTF observations in O3 was only 1.5 hr after merger. This further constrains the unknown, early-time emission of kilonovae in the g and r bands. Some models predict that the early emission could be very hot and bright in the UV; this can only be addressed once wide-field UV imagers (e.g., Dorado, ULTRASAT, and DUET) are launched.

Given the expected differences in sensitivity between the LIGO and Virgo interferometers, events in O4 are likely to be similarly coarsely localized (until KAGRA or LIGO India come online with high sensitivity). Moreover, given the increased GW sensitivity, we expect more events that are further away. Thus, we plan to implement stricter selection criteria. Specifically, for O4, we plan to only trigger on events with FARs lower than 1 yr–1 (i.e., four out of 15 events in O3 would fail this criterion). We plan to only trigger on NSBH events with a nonzero HasRemnant probability (i.e., six out of eight NSBH triggers in O3 would fail this criterion, including GW190814). As we did in O3, we plan to only trigger on MassGap events with a nonzero HasNS probability. In summary, only five out of the 13 events followed up in O3 would pass our new plan for trigger criteria in O4.

The first phase of the ZTF survey ran from 2018 March to 2020 September. The second phase of the ZTF is expected to run from 2020 October to 2023 September. Searches with ZTF Phase II are planned to be up to 2 mag deeper than nominal survey operations, even with 1000 deg2 localizations, thanks to the availability of deeper stacks as reference images. We plan to require a minimum median image depth of −16.0 mag and minimum enclosed probability of 50% in the first 4 hr of observations. The ZTF mapping speed allows 3600 deg2 to be mapped in 4 hr to achieve the necessary depth for a median GW distance of 300 Mpc. If the event is more distant, we will increase our exposure time from 180 to 600 s to go deeper. For events that are either too distant or too coarsely localized, we will not undertake triggered searches and will rely only on serendipitous searches of the all-sky public survey at 2 days' cadence to 20.4 mag.

Moreover, redder searches will better constrain the kilonova phase space and probe higher lanthanide fractions. The ZTF II would push to the red, since broader reference coverage is now available in the i-band filter (see Sagués Carracedo et al. 2020 for detailed simulations on gain in depth and red sensitivity). New wide-field infrared surveyors are also coming online (e.g., WINTER at Palomar Observatory, USA, and DREAMS at Siding Springs Observatory, Australia)

We look forward to searches in the fourth observing run, as detections will be more likely. For zero detections, about 17 neutron star mergers with only 50% enclosed probability to a depth of −16 mag would constrain the luminosity function fraction brighter than GW170817 to <25% (only 11 events with 75% enclosed probability would place a similarly stringent limit). Thus, as the sample size grows, even with partial coverage of sky maps, the luminosity function of kilonovae will be strongly constrained.

We conclude with some thoughts on what would strengthen the partnership between the GW physics community and the EM astronomy community. First, we encourage efforts that would speed up the release of the more accurate LALInference map (Veitch et al. 2015). Since the LALInference map was often only available after our observations were completed, our net expectation value dropped by 10%, and our net joint nondetection probability dropped by a factor of 2 between the BAYESTAR (Singer & Price 2016) map and the LALInference map. Moreover, three triggers never had an LALInference map released (S190923y, S190930t, and S191205ah).

Second, it is critical that a reliable FAR and terrestrial probability are released as soon as possible. If an event is going to be retracted (or the FAR increases significantly) based on offline analysis, it is essential that the EM community be notified immediately via GCN, so that all pending follow-up can be halted. Third, if the classification of an event changes in offline analysis, the EM community should be promptly notified via GCN. Fourth, since HasNS and HasRemnant are somewhat model-dependent (e.g., Foucart et al. 2018; Chatterjee et al. 2020) but will drive the decision of whether or not some EM teams trigger follow-up, we request the release of rough estimates/ranges for more directly determined parameters (e.g., mass ratio, inclination, and chirp mass) that can help with the EM decision. We strongly encourage any algorithmic or technological development that will enable more accurate 3D skymaps, FARs, HasNS, and HasRemnant at lower latency to better inform the EM community's follow-up decisions.

In summary, the lessons learned from both the single detection in O2 and the dozen nondetections in O3 bode well for an exciting future for multimessenger astrophysics in the coming decade.

This work was supported by the Global Relay of Observatories Watching Transients Happen (GROWTH) project, funded by the National Science Foundation under PIRE grant No. 1545949. GROWTH is a collaborative project among the California Institute of Technology (USA), University of Maryland College Park (USA), University of Wisconsin Milwaukee (USA), Texas Tech University (USA), San Diego State University (USA), University of Washington (USA), Los Alamos National Laboratory (USA), Tokyo Institute of Technology (Japan), National Central University (Taiwan), Indian Institute of Astrophysics (India), Indian Institute of Technology Bombay (India), Weizmann Institute of Science (Israel), The Oskar Klein Centre at Stockholm University (Sweden), Humboldt University (Germany), Liverpool John Moores University (UK), and University of Sydney (Australia). Based on observations obtained with the Samuel Oschin Telescope 48 inch and the 60 inch telescope at the Palomar Observatory as part of the Zwicky Transient Facility project. The ZTF is supported by the National Science Foundation under grant No. AST-1440341 and a collaboration including Caltech, IPAC, the Weizmann Institute for Science, the Oskar Klein Center at Stockholm University, the University of Maryland, the University of Washington, Deutsches Elektronen-Synchrotron and Humboldt University, Los Alamos National Laboratories, the TANGO Consortium of Taiwan, the University of Wisconsin at Milwaukee, and Lawrence Berkeley National Laboratories. Operations are conducted by COO, IPAC, and UW. The ZTF forced photometry service was funded under Heising-Simons Foundation grant No. 12540303 (PI: Graham). The SED Machine is based upon work supported by the National Science Foundation under grant No. 1106171.

The GROWTH-India telescope is a 70 cm telescope with a 0.7° field of view, set up by the Indian Institute of Astrophysics and the Indian Institute of Technology Bombay with support from the Indo-US Science and Technology Forum (IUSSTF) and the Science and Engineering Research Board (SERB) of the Department of Science and Technology (DST), Government of India (https://sites.google.com/view/growthindia/). It is located at the Indian Astronomical Observatory (Hanle), operated by the Indian Institute of Astrophysics (IIA). The GROWTH-India project is supported by SERB and administered by IUSSTF under grant No. IUSSTF/PIRE Program/GROWTH/2015-16. This research has made use of the VizieR catalog access tool, CDS, Strasbourg, France (doi: 10.26093/cds/vizier). The original description of the VizieR service was published in A&AS 143, 23. These results made use of the Lowell Discovery Telescope (LDT) at Lowell Observatory. Lowell is a private, nonprofit institution dedicated to astrophysical research and public appreciation of astronomy and operates the LDT in partnership with Boston University, the University of Maryland, the University of Toledo, Northern Arizona University, and Yale University. The Large Monolithic Imager was built by Lowell Observatory using funds provided by the National Science Foundation (AST-1005313). The upgrade of the DeVeny optical spectrograph has been funded by a generous grant from John and Ginger Giovale and a grant from the Mt. Cuba Astronomical Foundation. The KPED team thanks the National Science Foundation and the National Optical Astronomical Observatory for making the Kitt Peak 2.1 m telescope available. We thank the observatory staff at Kitt Peak for their efforts to assist Robo-AO KP operations. The KPED team thanks the National Science Foundation, the National Optical Astronomical Observatory, the Caltech Space Innovation Council, and the Murty family for support in the building and operation of KPED. In addition, they thank the CHIMERA project for use of the Electron Multiplying CCD (EMCCD). The Liverpool Telescope is operated on the island of La Palma by Liverpool John Moores University in the Spanish Observatorio del Roque de los Muchachos of the Instituto de Astrofisica de Canarias with financial support from the UK Science and Technology Facilities Council. Some spectroscopic observations were obtained with the Southern African Large Telescope (SALT). The Photometric Redshifts for the Legacy Surveys (PRLS) catalog used in this paper was produced thanks to funding from the U.S. Department of Energy Office of Science, Office of High Energy Physics, via grant DE-SC0007914. This publication has made use of data collected at Lulin Observatory, partly supported by MoST grant 108-2112-M-008-001. Based on observations made with the Gran Telescopio Canarias (GTC), installed at the Spanish Observatorio del Roque de los Muchachos of the Instituto de Astrofísica de Canarias on the island of La Palma.

M.M.K. acknowledges generous support from the David and Lucille Packard Foundation. M.W.C. acknowledges support from the National Science Foundation with grant No. PHY-2010970. A.G. and J.S. acknowledge support from the Knut and Alice Wallenberg Foundation and GREAT research environment grant 2016-06012, funded by the Swedish Research Council. Some of the work by D.A.P. was performed at the Aspen Center for Physics, which is supported by National Science Foundation grant PHY-1607611. D.A.P. was partially supported by a grant from the Simons Foundation. H.K. thanks the LSSTC Data Science Fellowship Program, which is funded by LSSTC, NSF Cybertraining Grant 1829740, the Brinson Foundation, and the Moore Foundation; his participation in the program has benefited this work. This work has been supported by the Spanish Science Ministry Centro de Excelencia Severo Ochoa Program under grant SEV-2017-0709. A.J.C.T. acknowledges support from the Junta de Andalucía (Project P07-TIC-03094) and Spanish Ministry Projects AYA2012-39727-C03-01, AYA2015-71718R, and PID2019-109974RB-I00. V.A.F. was supported by grant RFBR 19-02-00432. I.A. acknowledges support by a Ramón y Cajal grant (RYC-2013-14511) of the Ministerio de Ciencia, Innovación, y Universidades (MICIU) of Spain. He also acknowledges financial support from MCIU through grant AYA2016-80889-P. A.A.M. is funded by the Large Synoptic Survey Telescope Corporation, the Brinson Foundation, and the Moore Foundation in support of the LSSTC Data Science Fellowship Program; he also receives support as a CIERA Fellow by the CIERA Postdoctoral Fellowship Program (Center for Interdisciplinary Exploration and Research in Astrophysics, Northwestern University). A.C. acknowledges support from the National Science Foundation with grant No. 1907975. W.-H.I., A.K., K.-L.L., C.-C.N., A.P., H.T., and P.-C.Y. acknowledge support from Ministry of Science and Technology (MoST) Taiwan grants 104-2923-M-008-004-MY5, 107-2119-M-008-012, 108-2628-M-007-005-RSP, and 108-2112-M-007-025-MY3. D.D. is supported by an Australian Government Research Training Program Scholarship. S.A. is supported by the GROWTH project, funded by the National Science Foundation under PIRE grant No. 1545949. A.S.C. is supported by GREAT research environment grant 2016-06012, funded by the Swedish Research Council. E.C.K. acknowledges support from the G.R.E.A.T. research environment and the Wenner-Gren Foundations. A.J.C.T. is thankful for fruitful discussions with J. Cepa, E. Fernández-García, J. A. Font, S. Jeong, A. Martín-Carrillo, A. M. Sintes, and S. Sokolov. D.A.H.B. acknowledges research support from the National Research Foundation of South Africa. S.B.P. and V.B. acknowledge BRICS grant No. "DST/IMRCD/BRICS/PilotCall1/ProFCheap/2017(G)" for part of the present work. J.S.B. was partially supported by a Gordon and Betty Moore Foundation Data-Driven Discovery grant and a grant from the National Science Foundation, "Conceptualization of a Scalable Cyberinfrastructure Center for Multimessenger Astrophysics."

Appendix A: Observing and Data Reduction Details for Follow-up Observations

A.1. Photometric Follow-up

We used the 1 and 2 m telescopes available at the LCO global network to follow up sources discovered with the ZTF. The images were taken with the Sinistro and Spectral cameras (Brown et al. 2013) at the 1 and 2 m, respectively, and scheduled through the LCO Observation Portal. 76 The exposure time varied depending on the brightness of the object, yet our requests would normally involve three sets of 300 s in the g and r bands. After stacking the reduced images, we extracted sources using the SExtractor package (Bertin & Arnouts 2010), and we calibrated magnitudes against PS1 (Chambers et al. 2016) objects in the vicinity. For nuclear transients located <8'' from their potential host, we use the High Order Transform of Psf ANd Template Subtraction code (HOTPANTS; Becker 2015) to subtract a PSF-scaled PS1 template previously aligned using SCAMP (Bertin 2006). The photometry for the nuclear candidates follows the same procedure described before but in the residual image. The images obtained with the LT were acquired using the IO:O camera with the Sloan griz filter set. They were reduced using the automated pipeline, which performs bias subtraction, trimming of the overscan regions, and flat-fielding. The image subtraction takes place once a PS1 template is aligned, and the final data come from the analysis of the subtracted image.

We used the Electronic Multiplier CCD camera at KPED to take hour-long exposures in the r band to follow up candidates. After stacking the images and following standard reduction techniques, we calibrate the extracted sources using PS1 sources in the field. When the candidate has a host galaxy, we perform image subtraction as described for the LCO.

We obtained data with the GMOS-N (Allington-Smith et al. 2002; Hook et al. 2004; Gimeno et al. 2016), mounted on the Gemini-North 8 m telescope on Maunakea. Data were analyzed after stacking four 200 s exposures in the g and i bands. The reductions were performed using the python package DRAGONS 77 provided by the Gemini Observatory. We used PS1 sources in the field to calibrate the data.

We used the LOT at the Lulin Observatory in Taiwan to follow up candidates discovered with the ZTF. The standard observations involved 240 s in the g', r', and i' bands. The reduction followed standard methods, and the sources were calibrated against the PS1 catalog. No further image subtraction was applied to the images acquired with the LOT.

We used the 0.7 m robotic GIT equipped with a 4096 × 4108 pixel back-illuminated Andor camera for LVC event follow-up during O3. The GIT is situated at the IAO (Hanle, Ladakh). We used both tiled and targeted modes for the follow-up for different GW triggers. Tiled observations typically comprise a series of 600 s exposures in the Sloan Digital Sky Survey (SDSS) r' filter. Targeted observations were conducted with varying exposure times in the SDSS u', g', r', and i' filters. All data were downloaded in real time and processed with the automated GIT pipeline. Zero-points for photometry were calculated using the PanSTARRS catalog (Flewelling 2018), downloaded from Vizier. The PSF photometry was performed with PSFEx (Bertin 2011). For sources with significant host background, we performed image subtraction with pyzogy (Guevel & Hosseinzadeh 2017), based on the ZOGY algorithm (Zackay et al. 2016).

Additionally, we obtained photometric data with the Spectral Energy Distribution Machine (SEDM; Blagorodnova et al. 2018; Rigault et al. 2019) on the P60 telescope. The processing is automated and can be triggered from the GROWTH Marshal. Standard requests involved g-, r-, and i-band imaging with the Rainbow Camera on the SEDM in 300 s exposures. The data are later reduced using a python-based pipeline that applies standard reduction techniques and a customized version of the Fremling Automated Pipeline (FPipe; Fremling et al. 2016) for image subtraction.

We used the imaging capabilities of the OSIRIS (Cepa et al. 2005) camera at the GTC to obtain 60 s exposures in the r band. Standard reduction techniques were applied to the data, and we used PS1 sources to calibrate the flux.

We obtained follow-up imaging of candidates with the Wafer Scale Imager for Prime (WASP) and the Wide-field Infrared Camera (WIRC; Wilson et al. 2003), both on the P200 telescope. For WASP data, a python-based pipeline applied standard optical reduction techniques (as described in De et al. 2020a), and the photometric calibration was obtained against PS1 sources in the field. The WIRC data were treated similarly using the same pipeline, but they were additionally stacked using Swarp (Bertin et al. 2002), while the calibration was done using the Two Micron All Sky Survey point-source catalog (Skrutskie et al. 2006).

We obtained imaging of one candidate using the Low Resolution Imaging Spectrometer (LRIS; Oke et al. 1995), mounted at the Keck I telescope. Our data were taken in the g and i bands reaching mAB ≈ 24. The data were reduced following standard methods.

We used the Large Monolithic Imager (LMI; Massey et al. 2013) on the 4.3 m LDT at Happy Jack, Arizona, to follow up the ZTF discoveries. Observations were conducted with the SDSS r filter for 90 s each, and the data were reduced using the photopipe 78 pipeline. The magnitudes were calibrated against the SDSS or Gaia catalogs (Ahumada et al. 2020) using the conversion scheme provided in Gaia documentation. 79

We used the Ultraviolet/Optical Telescope (UVOT; Roming et al. 2005) mounted on the Neil Gehrels Swift Observatory (hereafter referred to as Swift; Gehrels et al. 2004) to follow up interesting sources and track down their UV evolution. The ToO observations were scheduled in the v, b, u, w1, m2, and w2 bands for an average of 320 s exposure–1. We used the products of the Swift pipeline to determine the magnitudes. 80

We observed candidate counterparts of S200213t using the Astrophysical Research Consortium Telescope Imaging Camera (ARCTIC; Huehnerhoff et al. 2016) at the APO 3.5 m. We obtained dithered 120 s exposures binned 2 × 2 in the u, g, r, i, and z bands. Images were bias-corrected, flat-fielded, and combined using standard IRAF packages (noao, imred, and ccdred). SExtractor (Bertin & Arnouts 2010) was used to find and photometer point sources in the images using PSF photometry, and a photometric calibration to PanSTARRS field stars was performed (without filter corrections).

All photometry presented in the light curves and tables in this paper is corrected for galactic extinction using dust maps from Schlafly & Finkbeiner (2011).

We observed the field of ZTF19aassfws with the VLA in its B configuration on 2019 May 10 starting at 07:19:15 UT and 2019 June 4 starting at 08:20:32 UT. Our observations were carried out at a nominal central frequency of 3 GHz. We used 3C 286 as our bandpass and absolute flux calibrator and J1927+6117 as our complex gain calibrator. Data were calibrated using the standard VLA automated calibration pipeline available in the Common Astronomy Software Applications (CASA) package. We then inspected the data for further flagging and imaged interactively using the CLEAN algorithm. The image rms was ≈5.2 μJy for the first epoch and ≈4.6 μJy for the second epoch. Within a circular region centered on the optical position of ZTF19aassfws and of radius ≈21 (comparable to the nominal half-power beamwidth of the VLA at 3 GHz and for the B configuration), we find no significant radio emission. Thus, we set upper limits on the corresponding 3 GHz flux density of ≲16 and ≲14 μJy, respectively, for the first and second epochs.

A.2. Spectroscopic Follow-up

Using the GROWTH Marshal, we regularly triggered the Liverpool Telescope Spectrograph for the Rapid Acquisition of Transients (SPRAT; Piascik et al. 2014). SPRAT uses a 18 slit, which provides a resolution of R = 350 at the center of the spectrum. The data were reduced using the automated pipeline, which removes low-level instrumental signatures and then performs source extraction, sky subtraction, and wavelength and flux calibration.

We observed a number of transient candidates during classical observing runs with the P200 Double Spectrograph (DBSP) during O3. For the setup configuration, we used 10, 15, and 2'' slit masks; a D55 dichroic; a blue grating of 600/4000; and a red grating of 316/7500. Using a custom PyRAF DBSP reduction pipeline (Bellm & Sesar 2016), 81 we reduced our data.

We obtained several optical spectra with the 10.4 m GTC telescope (equipped with OSIRIS). We used the R1000B and R500R grisms for our observations, typically using a slit of width of 12. We used standard routines from the Image Reduction and Analysis Facility (IRAF) to perform our data reduction.

We observed ZTF19aarykkb using the DeVeny spectrograph mounted on the 4.3 m LDT. We obtained 22.5 minute exposures at an average airmass of 1.5. We used the DV2 grating (300 g mm−1, 4000 Å blaze) for this observation. Our spectra cover a wavelength range of approximately 3600–8000 Å.

In addition, we obtained a spectrum of ZTF20aarzaod with SALT (Buckley et al. 2003), using the Robert Stobie Spectrograph (RSS; Burgh et al. 2003), covering a wavelength range of 470–760 nm with a spectral resolution of R = 400. We triggered special GW follow-up program 2018-2-GWE-002 and reduced the data with a custom pipeline based on PyRAF routines and the PySALT package (Crawford et al. 2010).

Low-resolution spectra using the 2 m HCT were obtained using the HFOSC instrument; ZTF19aarykkb was observed using grisms Gr7 (3500–7800 Å) and Gr8 (5200–9000 Å), while AT2019wxt was observed using Gr7. The spectra were bias-subtracted, cosmic rays were removed, and the 1D spectra were extracted using the optimal extraction method. Wavelength calibration was effected using the arc lamp spectra FeAr (Gr7) and FeNe (Gr8). Instrumental response curves generated using spectrophotometric standards observed during the same night were used to calibrate the spectra onto a relative flux scale. The flux-calibrated spectra of ZTF19aarykkb from the two grisms were combined to a single spectrum covering the wavelength range 4000–9000 Å.

We obtained spectroscopy with the GMOS-N, mounted on the Gemini-North 8 m telescope on Maunakea, by combining six 450 s exposures on the R400 and B600 gratings. We used the GMOS long-slit capability and reduced the data following standard PyRAF techniques.

We obtained near-infrared spectroscopy of candidates using NIRES on the Keck II telescope. The data were acquired using standard ABBA dither patterns on the target source, followed by observations of an A0 telluric standard star close to the science target. The spectral traces were extracted using the spextool package (Cushing et al. 2004) for both the science target and standard star. The final spectra presented here were stacked from all individual dithers, followed by flux calibration and telluric correction using the xtellcor package (Vacca et al. 2003).

We obtained spectra using the LRIS on the Keck I telescope. The 600/4000 grism was used on the blue side and the 600/7500 grating on the red side, providing wavelength coverage between 3139–5642 Å (blue) and 6236–9516 Å (red). The exposure time was 600 s on both sides. The spectrum was reduced using LPipe (Perley 2019) with BD+28 as a flux calibrator. The red and blue relative fluxes are scaled by matching synthetic photometry to colors inferred from photometry of the transient.

Appendix B: Detailed Candidate Descriptions

Here we provide descriptions of each candidate identified within the sky map of each event followed up with the ZTF. We discuss each object announced via GCN. For candidates with a redshift, we note whether it is spectroscopic [s] or photometric [p]. Some candidates were classified as a part of coordinated spectroscopic follow-up with the Bright Transient Survey (BTS; Fremling et al. 2020) and the ZTF CLU experiment (De et al. 2020b).

B.1. GW190425

For candidates identified within the sky map of GW190425, see Coughlin et al. (2019a). Two candidate counterparts of GW190425z, ZTF19aarykkb and ZTF19aarzoad, were observed with the AMI Large Array at 15 GHz on 2019 April 26 (Rhodes et al. 2019). No radio emission was found to be associated with any of these candidates.

B.2. S190426c

We summarize the candidate counterparts to S190426c in Table 2 and the follow-up photometry in Table 11. Next, we discuss why we conclude that each one is unrelated.

Table 11. Follow-up Photometry for S190426c Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF19aasmftmAT2019sne2,458,602.6514LT g 21.330.1521.71
ZTF19aasmftmAT2019sne2,458,602.6528LT r 21.060.1021.51
ZTF19aasmftmAT2019sne2,458,602.6542LT i 20.900.1721.03
ZTF19aassfwsAT2019fuc2,458,603.6605LT g 99.099.022.32
ZTF19aassfwsAT2019fuc2,458,603.6619LT r 99.099.022.04
ZTF19aassfwsAT2019fuc2,458,603.6633LT i 99.099.021.50
ZTF19aaslszpAT2019snj2,458,603.6654LT g 20.800.0722.25
ZTF19aaslszpAT2019snj2,458,603.6668LT r 20.510.0722.12
ZTF19aaslszpAT2019snj2,458,603.6682LT i 19.190.0622.00
ZTF19aaslzjfAT2019snh2,458,603.6703LT g 20.940.1821.75
ZTF19aaslzjfAT2019snh2,458,603.6717LT r 20.400.1022.00
ZTF19aaslzjfAT2019snh2,458,603.6731LT i 20.300.1022.00
ZTF19aasmddtSN2019fht2,458,603.7113LT g 19.790.1022.77
ZTF19aasmddtSN2019fht2,458,603.7127LT r 19.430.1121.54
ZTF19aasmddtSN2019fht2,458,603.7141LT i 19.410.0921.10
ZTF19aasmddtSN2019fht2,458,604.7237LT g 19.690.0621.61
ZTF19aasmddtSN2019fht2,458,604.7251LT r 19.510.0322.29
ZTF19aasmddtSN2019fht2,458,604.7265LT i 19.550.0720.63

Download table as:  ASCIITypeset image

B.2.1. Spectroscopically Classified

ZTF19aasmftm/AT2019sne—The rising light curve of ZTF19aasmftm suggested that it could be a young and faint object with a galaxy host of mAB = 21.2 mag in PS1, so we highlighted it in Perley et al. (2019a). A few days later, GTC spectroscopy of this event (Hu et al. 2019b) classified it as a premaximum SN Ia in the outskirts of its host galaxy at z[s] = 0.156.

ZTF19aaslzjf/AT2019snh—Another candidate discovered during our second night of observations, ZTF19aaslzjf, was at low galactic latitude and seemed to be located in a nearby host galaxy. A spectrum from GTC (Hu et al. 2019b) confirmed both that this source was nearby (at z[s] = 0.086) and that it was an SN Ia located in the outskirts of the Galaxy host.

ZTF19aasmddt/SN2019fht—We highlighted this transient because its photometric redshift was consistent with the LVC distance estimate, and the light curve exhibited a rapid rise (Perley et al. 2019a). However, the GTC spectrum taken shortly afterward revealed that this transient was a young SN II prepeak in the outskirts of its galaxy at z[s] = 0.028.

ZTF19aaslszp/AT2019anj—Another candidate whose photo-z was consistent with the LVC distance estimate, ZTF19aaslszp, appeared to be relatively bright and red with a color of g − r = 0.89 mag. Subsequent ZTF and LT photometry revealed that the source appeared to have flaring behavior in the light curve. Our P200+DBSP spectrum classified the source as an AGN at z[s] = 0.084, as it shows broad hydrogen lines.

B.2.2. Slow Photometric Evolution

ZTF19aaslzfk/AT2019snd—We identified this candidate during our initial search of the imaged region within the BAYESTAR localization of S190426c (Coughlin et al. 2019c). Though the candidate had WISE detections in all four filters, its WISE colors did not definitively place this transient in the AGN class. Continued photometric monitoring of this candidate revealed its slow evolution (αg  = −0.02), ruling out its association with S190426c.

ZTF19aaslvwn/AT2019snf —We reported ZTF19aaslvwn in Perley et al. (2019a) as a lower-priority transient, with initially slow photometric evolution at low galactic latitude (b < 15°). After monitoring the transient over a period of ∼12 days, the photometry had only risen by 0.4 mag, indicating that it could not be a kilonova and was likely a CV.

ZTF19aasmdir/AT2019sng—Also reported in Perley et al. (2019a), ZTF19aasmdir was a nuclear transient at a low galactic latitude, with WISE colors consistent with an AGN within 1'' of the transient. Several days of monitoring yielded a light curve that was far more consistent with a flaring AGN than a kilonova, with a rate of evolution αr  < 0.01.

ZTF19aaslolf/AT2019snn—This nuclear candidate was a low priority in our follow-up list due to its high photometric redshift (z[p] = 0.42) and because its WISE colors placed it within the AGN locus. Though we could not spectroscopically confirm this, the slowly evolving "flaring" light curve (αr  < 0.01) and archival PS1 detections point to the AGN nature of this candidate.

ZTF19aaslphi/AT2019sno—The candidate ZTF19aaslphi had a photometric redshift that was also nominally inconsistent with the LVC distance. However, we identified it as a candidate of interest due to its relatively quick rise of ∼0.75 mag over the course of 4 days in the g band. Its later-time light curve exhibited a plateau; thus, we consider its evolution too slow to be associated with a GW event.

ZTF19aaslpds/AT2019snq—This candidate, at low galactic latitudes, had multiple detections in the r and g filters; but, as it only evolved by 0.04 mag over a day of monitoring and subsequently was not detected, we ruled it out as a potential counterpart to S190426c.

ZTF19aaslozu/AT2019snr—We included this candidate initially due to its rapid rise and gr color of 0.3 mag (Perley et al. 2019a). Though ZTF19aaslozu did not clearly fall into the AGN locus, its detections in all four WISE filters, archival detections with PS1, and slow evolution point to it being a strong AGN candidate.

ZTF19aasshpf/AT2019snt—This is a lower-priority candidate on our list discovered at r = 21.59 mag in the outskirts of a faint red galaxy. It exhibited a flat evolution (0.06 mag) over a period of 27 days, thus ruling out its association with S190426c.

ZTF19aasmzqf —We could likewise rule out the possibility of ZTF19aasmzqf being a kilonova due to its slow evolution of 0.3 mag over 28 days, despite its initial red color gr = 0.22 mag.

B.2.3. Stellar

ZTF19aasmekb/AT2019snl—Located at low galactic latitude (b = −864), ZTF19aasmekb appeared to be hostless and initially exhibited a rapid fade; its later-time light curve is photometrically consistent with a CV, and its slow evolution (αg  = 0.24) is inconsistent with a kilonova origin.

B.2.4. Artifacts

ZTF19aassfws/AT2019fuc—We highlighted ZTF19aassfws as a candidate of potential interest because its photometric redshift fell within the LIGO distance uncertainty (Perley et al. 2019a). We also obtained radio follow-up using the VLA and AMI under the Jansky VLA mapping of Gravitational Waves as Afterglows in Radio (JAGWAR; Mooley et al. 2018), and we did not detect any radio emission. However, upon careful inspection of the reference image, we identified a very subtle gain mismatch across the image. Comparing the initial photometry of the transient with the level of the gain mismatch provided a clear indication that our candidate was not astrophysical but rather an artifact. This gain mismatch problem has since been fixed by rebuilding the references.

B.3. GW190814

No candidates were identified in the ZTF follow-up of the small localization of GW190814.

B.4. S190901ap

We summarize the candidate counterparts to S190901ap in Table 3 and the follow-up photometry in Table 12. Next, we discuss why we conclude that each one is unrelated.

Table 12. Follow-up Photometry for S190901ap Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF19abvizswAT2019pim2,458,729.229GIT i 20.140.120.41
ZTF19abvizswAT2019pim2,458,729.126GIT i 20.130.0920.41
ZTF19abvizswAT2019pim2,458,729.303GIT g 21.190.0621.43
ZTF19abvizswAT2019pim2,458,729.103GIT r 20.570.1120.65
ZTF19abvizswAT2019pim2,458,730.4481LT g 22.020.1022.00
ZTF19abvizswAT2019pim2,458,730.4420LT r 21.620.0922.0
ZTF19abvizswAT2019pim2,458,730.4541LT i 21.160.0722.00
ZTF19abvizswAT2019pim2,458,730.4621LT z 20.870.1222.00
ZTF19abvizswAT2019pim2,458,731.14GIT i 99.099.020.29
ZTF19abvizswAT2019pim2,458,731.134GIT i 99.099.020.29
ZTF19abvizswAT2019pim2,458,731.118GIT r 99.099.020.98
ZTF19abvizswAT2019pim2,458,731.125GIT r 99.099.021.14
ZTF19abvizswAT2019pim2,458,731.3862LT g 22.500.2022.50
ZTF19abvizswAT2019pim2,458,731.3802LT r 22.050.1022.50
ZTF19abvizswAT2019pim2,458,731.3923LT i 21.600.1022.50
ZTF19abvizswAT2019pim2,458,731.3983LT z 21.200.2022.50
ZTF19abvizswAT2019pim2,458,731.5172LT g 22.540.1623.00
ZTF19abvizswAT2019pim2,458,731.5112LT r 22.100.1223.00
ZTF19abvizswAT2019pim2,458,731.5232LT i 21.640.1123.00
ZTF19abvizswAT2019pim2,458,731.5293LT z 21.550.2223.00
ZTF19abvizswAT2019pim2,458,732.102GIT r 99.099.019.32
ZTF19abvizswAT2019pim2,458,732.119GIT i 99.099.020.4
ZTF19abvizswAT2019pim2,458,732.125GIT i 99.099.020.43
ZTF19abvizswAT2019pim2,458,738.3819WHT r 22.600.1224.00
ZTF19abvizswAT2019pim2,458,739.3839WHT i 22.430.1224.10
ZTF19abvizswAT2019pim2,458,740.4939WHT i 22.510.1523.50
ZTF19abvizswAT2019pim2,458,740.5219WHT r 23.380.2523.70
ZTF19abvizswAT2019pim2,458,750.7337Keck1 g 23.990.1026.00
ZTF19abvizswAT2019pim2,458,750.7342Keck1 i 23.800.0925.00
ZTF19abvionhAT2019pip2,458,729.166GIT r 20.80.0521.27
ZTF19abvionhAT2019pip2,458,729.206GIT r 20.770.0621.17
ZTF19abvionhAT2019pip2,458,729.213GIT r 20.680.0821.15
ZTF19abvionhAT2019pip2,458,730.166GIT r 20.630.0421.22
ZTF19abvionhAT2019pip2,458,730.18GIT r 20.660.0521.23
ZTF19abvionhAT2019pip2,458,731.204GIT g 20.560.0621.16
ZTF19abvionhAT2019pip2,458,731.4331LT u 20.470.1121.86
ZTF19abvionhAT2019pip2,458,731.4208LT g 20.510.2922.55
ZTF19abvionhAT2019pip2,458,731.4168LT r 20.360.0922.35
ZTF19abwsmmdAT2019pnc2,458,731.5587LT g 19.860.1620.41
ZTF19abwsmmdAT2019pnc2,458,731.5641LT r 20.020.0722.02
ZTF19abwsmmdAT2019pnc2,458,731.5614LT i 20.260.0622.47
ZTF19abwvalsAT2019pni2,458,731.7095LT g 20.420.0722.63
ZTF19abwvalsAT2019pni2,458,731.7149LT r 20.040.0822.96
ZTF19abwvalsAT2019pni2,458,731.7122LT i 20.230.2422.30
ZTF19abvixoyAT2019pin2,458,729.144GIT r 18.970.0321.16
ZTF19abvixoyAT2019pin2,458,729.182GIT r 18.730.0221.17
ZTF19abvixoyAT2019pin2,458,729.238GIT i 18.970.0520.35
ZTF19abvixoyAT2019pin2,458,729.245GIT i 19.060.0520.38
ZTF19abvixoyAT2019pin2,458,729.285GIT i 19.020.120.27
ZTF19abvixoyAT2019pin2,458,729.292GIT i 18.940.120.23
ZTF19abvislpAT2019pnx2,458,734.171GIT g 99.099.020.42
ZTF19abvislpAT2019pnx2,458,734.178GIT g 99.099.020.29
ZTF19abvislpAT2019pnx2,458,735.113GIT g 99.099.020.34
ZTF19abvislpAT2019pnx2,458,735.181GIT r 99.099.019.91
ZTF19abvislpAT2019pnx2,458,733.111GIT g 99.099.020.45
ZTF19abvislpAT2019pnx2,458,733.118GIT g 99.099.020.36
ZTF19abvislpAT2019pnx2,458,735.174GIT r 99.099.019.89
ZTF19abxdvcsAT2019qev2,458,733.133GIT g 19.930.0320.7
ZTF19abxdvcsAT2019qev2,458,733.173GIT r 20.180.0520.72
ZTF19abxdvcsAT2019qev2,458,733.179GIT r 20.280.0320.82
ZTF19abxdvcsAT2019qev2,458,734.242GIT g 19.830.0320.55
ZTF19abxdvcsAT2019qev2,458,734.249GIT g 19.90.0520.38
ZTF19abxdvcsAT2019qev2,458,734.258GIT r 20.030.0520.31
ZTF19abxdvcsAT2019qev2,458,734.264GIT r 20.110.0520.32
ZTF19abxdvcsAT2019qev2,458,735.206GIT r 19.80.0519.94
ZTF19abxdvcsAT2019qev2,458,735.213GIT r 19.840.0519.89

Download table as:  ASCIITypeset images: 1 2

B.4.1. Spectroscopically Classified

ZTF19abvizsw/AT2019pim—We discovered a red transient (g r ≈ 0.5) that appeared to be hostless and fast-evolving. We had observed the location of this transient every night for the month leading up to 2019 September 1 with no previous detections, therefore indicating strongly that this object was a new transient. Gravitational Wave Inaf Team Collaboration (GRAWITA) spectroscopic observations about 10 hr later seemed to suggest that the object was a galactic K or M dwarf (Salsamo et al. 2019a), but our subsequent LRIS spectroscopic follow-up yielded a featureless continuum with Mg ii, Mg i, and Fe ii lines at z[s] = 1.26 (Burdge et al. 2019). Thus, we posited that the object could be a flaring AGN or a GRB afterglow. Observations with SVOM-GWAC-F60A (Wei et al. 2019) and the LT (Perley et al. 2019b) indicated that the light curve was rapidly decaying, suggesting that the transient was likely an orphan GRB afterglow. More than 10 other GCNs contained reported follow-ups of this transient; the collated evidence posed the coherent picture that we had, remarkably, detected an untriggered long GRB afterglow in temporal and spatial coincidence with the sky map of S190901ap. This candidate will be discussed in more detail in D. A. Perley et al. (2020, in preparation).

ZTF19abvixoy/AT2019pin—We detected this transient with an upper limit from the day before the merger, though it appeared to have a faint counterpart in PS1. GRAWITA spectroscopic observations classified this transient as a CV due to its blue continuum and weak Hα emission surrounded by broad absorption troughs (Salmaso et al. 2019b).

ZTF19abvionh/AT2019pip—The photometric redshift of the putative host of this transient initially made it an interesting candidate for association with S190901ap, even though its first two detections were separated by a short baseline of 7 minutes. About 15 hr later, spectroscopic observations with the Hobby-Eberly observatory suggested that the host galaxy GALEXASC J165500.03+140301.3 was located at a distance of ∼450 Mpc (Rosell et al. 2019); our LRIS spectrum, showing a hot blue continuum and host galaxy lines at z[s] = 0.0985, confirmed this conclusion, placing the transient outside of the GW distance error bar by 2.5σ. Upon close inspection of the spectra, we find Hα and He ii at zero redshift, suggesting that the transient is a foreground CV and the background host galaxy is unrelated.

ZTF19abwvals/AT2019pni—Another transient detected via the AMPEL alert archive, ZTF19abwvals, appeared to be red (gr ∼ 0.5) and had a photometric redshift of 0.13, slightly higher than the GW distance, also with upper limits in the g band the previous day (Stein et al. 2019c). The SNID template matching to the spectra taken with the ALFOSC spectrograph on the Nordic Optical Telescope revealed that ZTF19abwvals was a normal SN Ia, about 4–6 days postpeak (Izzo et al. 2019).

B.4.2. Slow Photometric Evolution

ZTF19abwsmmd/AT2019pnc—Further searches of the data with the AMPEL pipeline yielded two additional candidates, including ZTF19abwsmmd (Stein et al. 2019c). This candidate exhibited a blue color (gr ∼ 0.25) and had nondetections in the g band to 20.64 mag a day before the merger. The ZTF survey operations monitored it over a period of about 35 days. The light curve exhibited a change of only 0.2 mag decline over that baseline; therefore, we deemed it too slow to be associated with the GW event.

ZTF19abvislp/AT2019pnx—We performed a second search of the AMPEL alert archive in which we identified this transient, detected on the first night of observations. It was interesting due to its rising light curve and host SDSS galaxy being at a redshift of 0.1, on the upper end of the LIGO distance range. Instead of using our spectroscopic resources, we chose to monitor the transient photometrically, and its evolution over nearly 30 days proved to be too slow (αr  = 0.05) to be a kilonova.

ZTF19abxdvcs/AT2019qev—We also discovered ZTF19abxdvcs during a second AMPEL archive search and highlighted it due to its photometric redshift (z ∼ 0.118) and the fact that it had risen by more than 0.65 mag over the course of 3 days, with its first detection on the first night. Though we did not report this candidate via GCN, our continued photometric monitoring with the ZTF demonstrated that the transient was evolving with αg  = 0.03, and its light curve resembled that of an SN, so we could confidently reject it.

B.5. S190910d

We summarize the candidate counterparts to S190910d in Table 4 and the follow-up photometry in Table 13. Next, we discuss why we conclude that each one is unrelated.

Table 13. Follow-up Photometry for S190910d Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF19abyfazmAT2019pwa2,458,736.8848P60 r 18.170.0420.48
ZTF19abyfazmAT2019pwa2,458,737.3704LT g 17.950.0321.00
ZTF19abyfazmAT2019pwa2,458,737.3704LT g 17.960.0121.81
ZTF19abyfazmAT2019pwa2,458,737.3715LT r 18.300.0321.00
ZTF19abyfazmAT2019pwa2,458,737.3715LT r 18.300.0122.36
ZTF19abyfazmAT2019pwa2,458,737.3725LT i 18.650.0521.00
ZTF19abyfazmAT2019pwa2,458,737.3725LT i 18.620.0122.16

Download table as:  ASCIITypeset image

B.5.1. Spectroscopically Classified

ZTF19abyfhov/AT2019pvu—We identified this candidate during our follow-up campaign for S190910d with no available photometric redshifts due to cross-matches at its sky position (Anand et al. 2019). Castro-Tirado et al. (2019b) observed it with the 10.4 m GTC telescope equipped with OSIRIS in La Palma, Spain, about 16 hr after initial detection and derived an r-band magnitude of 20.33 mag for the transient. The best match to their spectrum indicated that the candidate was an SN Ia at z[s] = 0.133 ± 0.001. Another spectrum taken with the ACAM instrument on the William Herschel Telesope at the Roque de los Muchachos Observatory in La Palma confirmed the classification (Cannizzaro et al. 2019).

ZTF19abyfhaq/AT2019pvv—Similarly, we detected ZTF19abyfhaq with little other information than the r-band magnitude of its initial detection at 20.3 mag (Anand et al. 2019). The GTC spectrum taken (Castro-Tirado et al. 2019b) about 18 hr after the initial detection had a too-low S/N to merit a classification, but an Hα emission line at z[s] = 0 revealed that the transient was galactic and therefore unrelated.

ZTF19abyfazm/AT2019pvz—Among the other candidates identified in Anand et al. (2019), we highlighted this one as being blue (gr ∼ 0.4), with its last nondetection 1 day before the merger, and a faint source in PS1 about 25 from the transient position. Our imaging and spectroscopy with the LT showed that the transient remained bright and blue, with no obvious emission or absorption lines in the spectrum, suggesting that this was likely a CV (Perley & Copperwheat 2019a); this conclusion was further supported by a GTC spectrum (Castro-Tirado et al. 2019b).

ZTF19abyfbii/AT2019pwa—During the same initial search, we identified ZTF19abyfbii, whose proximity to an SDSS galaxy with a photometric redshift of z[p] = 0.124 placed it within the distance uncertainty for S190910d (Anand et al. 2019). Our candidate was classified as an SN Ia at z[s] = 0.1286 ± 0.0005 less than 20 hr later by GTC using the Hα, Hβ, and O ii lines in its spectrum (Castro-Tirado et al. 2019b). Further spectroscopy with the William Hershel Telescope provided a detailed classification that this transient was SN Ia 91T–like, 5 days before the peak, at z[s] = 0.118 (Cannizzaro et al. 2019).

B.6. S190910h

We summarize the candidate counterparts to S190910h in Table 5 and the follow-up photometry in Table 14. Next, we discuss why we conclude that each one is unrelated.

Table 14. Follow-up Photometry for S190910h Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF19abyjcomAT2019pxk2,458,737.5558LT g 99.099.020.75
ZTF19abyjcomAT2019pxk2,458,737.5569LT r 99.099.020.71
ZTF19abyjcomAT2019pxk2,458,737.5579LT i 99.099.020.21
ZTF19abyjconAT2019pxl2,458,737.6142LT g 99.099.021.29
ZTF19abyjconAT2019pxl2,458,737.6152LT r 99.099.021.44
ZTF19abyjconAT2019pxl2,458,737.6163LT i 99.099.021.33
ZTF19abyjcooAT2019pxm2,458,737.6234LT g 99.099.020.84
ZTF19abyjcooAT2019pxm2,458,737.6245LT r 99.099.020.89
ZTF19abyjcooAT2019pxm2,458,737.6255LT i 99.099.021.30

Download table as:  ASCIITypeset image

B.6.1. Spectroscopically Classified

ZTF19abyheza/AT2019pxi—We initially detected ZTF19abyheza at g = 19.14 ± 0.13 with the ZTF with heavy galactic extinction of ∼0.8 in the direction of the transient. One day later, Valeev et al. (2019) imaged the transient, reporting that it had brightened to r = 18.74 ± 0.05. The GTC spectroscopy revealed Hα in emission and Hβ in absorption at z[s] = 0. Synthesizing this information along with the light-curve shape suggested that this was likely a CV.

ZTF19abyhhml/AT2019pxj—According to our machine-learning algorithms derived from the PS1-DR2 catalog, we could not clearly determine whether this source was of stellar origin. Similar to the previous transient, GTC imaging demonstrated that the light curve had risen to r = 19.26 ± 0.04, and spectra exhibited the He ii and He i lines and a double-peaked Hα line, confirming that it was also a galactic CV.

ZTF19abyirjl/AT2019pxe—We highlighted ZTF19abyirjl as being of interest due to its photometric redshift, 0.1 ± 0.017. Having no other information about the transient, we monitored the light curve for several days and determined it was too slow to be associated with the GW event, with an average flat evolution. One month later, we obtained a spectrum using P200+DBSP, which clearly demonstrated through Si ii lines that it was an SN Ia.

ZTF19abygvmp/AT2019pzg—This candidate was among those candidates reported in our second set of transients (Stein et al. 2019a). We highlighted ZTF19abygvmp, a transient detected 1 hr after the merger time, in a slightly offset position from the galaxy, as it had appeared to have risen by 0.5 mag since the last nondetection. Cannizzaro et al. acquired a WHT spectrum of the source about 2 days later, but the spectrum, dominated by host galaxy light, yielded only a redshift of z[s] = 0.049, exactly consistent with the LVC distance estimate. Two weeks later, we obtained an LRIS spectrum of the source, classifying it as an SN II (also consistent with its slow photometric evolution).

B.6.2. Slow Photometric Evolution

ZTF19abylleu/AT2019pyu—23 hr after the merger, we detected this bright (r = 19.25 mag) transient with an upper limit of r = 20.4 mag from the day before. Though we could not obtain any spectra, we continued tracking the evolution of the transient over a period of ∼25 days; the r-band light curve remained relatively flat, while the g-band light curve exhibited a gradual decline. We concluded that the evolution was too slow (αg  = 0.03) to be associated with the GW event.

ZTF19abyjfiw—Valeev et al. (2019) obtained a spectrum with GTC about 2 days later that appeared to be a featureless blue continuum from which they could not derive a conclusive classification. However, the transient presents a flat evolution, with a coefficient α < 0.1. Another detection by the ZTF (4 months after merger) suggests that it could be a CV.

ZTF19abyiwiw/AT2019pzi—We identified this transient in spatial and temporal coincidence with both S190910d and S190910h at 31 galactic latitude and 2.3 mag of extinction in the direction of the transient. It was first discovered at r = 20.16 mag, but photometric follow-up determined that its evolution was too slow to be relevant, with αg  = 0.20.

ZTF19abymhyi/AT2019pzh—The object ZTF19abymhyi was faint and hostless, with detections in the g band 2 hr after the merger (Stein et al. 2019a) and upper limits of g = 20.65 mag from the day before. The transient rose by ∼0.3 mag 1 day later. However, it was ruled out because its photometric evolution did not pass our threshold, as it faded slower than expected with αg  = 0.03.

ZTF19abyjcoo/AT2019pxm—This orphan transient was discovered at r = 20.28 mag, and we rule it out due to its slow evolution (αr  = 0.06).

B.6.3. Artifacts

ZTF19abyjcom/AT2019pxk, ZTF19abyjcon/AT2019pxl—On the first night of observations following this GW event, we detected two hostless transients within the same exposure, detected within the same sky region. Imaging with the LT about 1 day later resulted in nondetections of both transients, despite the fact that other transients of a similar magnitude, discovered within the same exposure, were detected. Furthermore, despite clear detections initially in the r and g bands, we could not detect these transients in future serendipitous observations of the sky region with the ZTF. We posit that these three transients are likely cross-talk artifacts that occurred within the same exposure and therefore are unrelated.

B.7. S190923y

We summarize one candidate counterpart to S190923y in Table 6. Despite the small sky localization, the position of S190923y on the sky made it particularly challenging to access. For that reason, we chose to conduct a fully serendipitous search in ZTF data.

ZTF19acbmopl/AT2019rob—We found this transient with a photometric redshift of ≲0.03, consistent with the LVC distance reported, slightly off the nucleus of its host galaxy. It showed a slow evolution in both the r and g bands: αr  = 0.03 and αg  = 0.03.

B.8. S190930t

We summarize the candidate counterparts to S190930t in Table 7 and the follow-up photometry in Table 15. Next, we discuss why we conclude that each one is unrelated.

Table 15. Follow-up Photometry for S190930t Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ATLAS19wynAT2019rpj2,458,758.0974LOT g 19.650.0899.0
ATLAS19wynAT2019rpj2,458,758.0974LOT r 19.580.0999.0
ATLAS19wynAT2019rpj2,458,758.0974LOT i 19.550.1299.0
ATLAS19wynAT2019rpj2,458,758.8562LDT r 19.60.122.8
ZTF19acbpqlhAT2019rpn2,458,758.0937LOT g 20.800.2599.0
ZTF19acbpqlhAT2019rpn2,458,758.0937LOT r 20.670.3399.0
ZTF19acbpqlhAT2019rpn2,458,758.0937LOT i 20.800.3999.0
ZTF19acbpqlhAT2019rpn2,458,758.8548LDT r 19.800.1022.8

Download table as:  ASCIITypeset image

B.8.1. Spectroscopically Classified

ZTF19acbpqlh/AT2019rpn—We first detected this candidate 13.4 hr after the merger using our AMPEL pipeline with a magnitude of g = 20.36 mag and upper limits of g = 20.77 mag from 3 days before the merger. The transient was at a galactic latitude of b = −849. Using its spectroscopic host galaxy redshift, z[s] = 0.026, we derived an absolute magnitude of −14.91 mag (Stein et al. 2019b). The same night, we obtained a spectrum with P200+DBSP revealing a mostly featureless blue continuum with a weak broad feature around Hα suggesting that the transient could be a young core-collapse SN. Using the ZTSh 2.6 m telescope at the CrAO observatory, Mazaeva et al. (2019) imaged the SN and found that its BR color of 0.5 mag was unlike what was expected of any optical transient associated with a GW event. We followed up by taking a second spectrum with the DBSP on 2019 October 5 and confirmed that the candidate was indeed an SN II.

ZTF19acbwaah/AT2019rpp—22 hr after the merger, we detected this transient, whose slight offset from a potential galaxy host at z[s] = 0.032 lends it an absolute magnitude of −18.069 (Stein et al. 2019b). The next night, we conducted observations of this candidate with the DBSP; the spectrum was consistent with an SN Ia a few weeks after maximum light located at z[s] = 0.03 (Karambelkar et al. 2019b).

ATLAS19wyn/AT2019rpj—With the ZTF, we independently detected a candidate first reported by ATLAS (Smartt et al. 2019; ZTF19acbpsuf) 13.8 hr after the merger; ATLAS detected it 4 hr later. The transient had a deep upper limit of 20.92 from about 6 days before the merger, and its association with a host at z[s] = 0.0297 translated to an absolute magnitude of −15.987. The strong Balmer P Cygni features in our DBSP spectrum, taken the same night as the initial detection, clearly indicated that the transient was an SN (Karambelkar et al. 2019a).

B.9. S191205ah

We summarize the candidate counterparts to S191205ah in Table 8 and follow-up photometry in Table 16. Next, we discuss why we conclude that each one is unrelated.

Table 16. Follow-up Photometry for S191205ah Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF19acxowrrAT2019wib2,458,850.0554P60 r 18.910.1699.0
ZTF19acxowrrAT2019wib2,458,852.7504P60 i 99.099.020.00
ZTF19acyitgaAT2019wmn2,458,837.8427P60 r 18.210.0799.0

Download table as:  ASCIITypeset image

B.9.1. Spectroscopically Classified

ZTF19acyiflj/AT2019wmy—This transient was discovered at r = 20.09 mag and observed by GTC at a magnitude of r = 19.79 mag hours after the trigger. A faint host is visible in the PS1 images of the field. However, the GTC spectrum showed an SN Ia at a redshift of z[s] = 0.081 (Hu et al. 2019a).

ZTF19acxowrr/AT2019wib—The first detection of this transient was ∼4 days after the GW event at r = 19.054 ± 0.13 mag. It rose over the first ∼15 days, during which several spectra were taken. The first classification came from GTC (Hu et al. 2019c): an SN II at a redshift of z[s] = 0.05.

ZTF19acyitga/AT2019wmn—This transient was located in a galaxy at a redshift of z[s] = 0.071 and first detected at r = 19.26 mag. We obtained an LT spectrum of ZTF19acyitga 14 days after the discovery that showed it was an SN Ia.

B.9.2. Slow Photometric Evolution

ZTF19acxpnvd/AT2019wkv—This transient was reported in Andreoni et al. (2019b) after its discovery at r = 19.4 mag. The transient was located in the outskirts of a galaxy located at a photometric SDSS redshift of z[p] ≲ 0.03, and it was ruled out due to the slow evolution shown after peaking, with αg  = 0.06.

ZTF19acxoywk/AT2019wix—Similarly, this transient was reported in Andreoni et al. (2019b) with a discovery magnitude of r = 19.75 mag. It was located in the outer regions of a galaxy with a spectroscopic redshift of z[s] = 0.05; however, the evolution of this transient was only αg  = −0.15.

ZTF19acxoyra/AT2019wid—This slow-evolving transient was highlighted in Andreoni et al. (2019b) after being discovered at r = 19.20 mag in the nucleus of a galaxy at z[s] = 0.09. However, it had an almost flat evolution after reaching its peak (αg  = 0.05).

ZTF19acxpwlh/AT2019wiy—This transient was located in a galaxy at an SDSS photometric redshift of z[p] = 0.12. Discovered at g = 19.84, it showed an almost flat evolution over the days after reaching its peak (αr  = 0.07).

B.10. S191213g

We summarize the candidate counterparts to S191213g in Table 9 and the follow-up photometry in Table 17. Next, we discuss why we conclude that each one is unrelated.

Table 17. Follow-up Photometry for S191213g Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF19acykzskSN2019wqj2,458,831.8323P60 r 19.060.0820.34
ZTF19acykzskSN2019wqj2,458,831.928LOT g 19.370.1099.0
ZTF19acykzskSN2019wqj2,458,831.931LOT r 19.110.1699.0
ZTF19acykzskSN2019wqj2,458,831.935LOT i 19.100.1199.0
ZTF19acykzskSN2019wqj2,458,832.223LOT g 19.510.1199.0
ZTF19acykzskSN2019wqj2,458,832.231LOT r 19.100.1499.0
ZTF19acykzskSN2019wqj2,458,832.233LOT i 19.060.2499.0
ZTF19acykzskSN2019wqj2,458,832.2910UVOT v 99.099.017.2
ZTF19acykzskSN2019wqj2,458,832.2910UVOT b 99.099.017.8
ZTF19acykzskSN2019wqj2,458,832.2910UVOT u 99.099.017.5
ZTF19acykzskSN2019wqj2,458,832.2910UVOT w199.099.017.5
ZTF19acykzskSN2019wqj2,458,832.2910UVOT m299.099.018.0
ZTF19acykzskSN2019wqj2,458,832.2910UVOT w299.099.018.1
ZTF19acymixuAT2019wrr2,458,832.2910UVOT v 99.099.019.5
ZTF19acymixuAT2019wrr2,458,832.2910UVOT b 20.100.499.0
ZTF19acymixuAT2019wrr2,458,832.2910UVOT u 99.099.019.7
ZTF19acymixuAT2019wrr2,458,832.2910UVOT w199.099.019.7
ZTF19acymixuAT2019wrr2,458,832.2910UVOT m299.099.019.7
ZTF19acymixuAT2019wrr2,458,832.2910UVOT w299.099.020.3
ZTF19acymaruAT2019wnh2,458,831.9682LCOGT1m g 19.830.0421.00
ZTF19acymaruAT2019wnh2,458,831.9706LCOGT1m i 20.230.1521.00
ZTF19acymaruAT2019wnh2,458,831.9755LCOGT1m r 20.110.0521.00
ZTF19acyfohaAT2019wkl2,458,831.7544P60 r 17.290.0519.19
ZTF19acyldunAT2019wrt2,458,853.7823P60 i 18.990.1019.87
ZTF19acyldunAT2019wrt2,458,832.2910UVOT v 99.099.017.9
ZTF19acyldunAT2019wrt2,458,832.2910UVOT b 18.830.1399.0
ZTF19acyldunAT2019wrt2,458,832.2910UVOT u 18.180.1299.0
ZTF19acyldunAT2019wrt2,458,832.2910UVOT w117.620.1199.0
ZTF19acyldunAT2019wrt2,458,832.2910UVOT m217.710.1399.0
ZTF19acyldunAT2019wrt2,458,832.2910UVOT w218.190.1299.0

Download table as:  ASCIITypeset image

B.10.1. Spectroscopically Classified

ZTF19acykzsk/SN2019wqj—This transient was discovered at g = 19.25 mag in a galaxy at z[s] = 0.021. It was not detected in the ultraviolet by the Swift telescope (Oates et al. 2019). The spectrum taken with the SPRAT on the LT (Perley & Copperwheat 2019b) and the GMOS-N mounted on the Gemini-North 8 m telescope (Fremling et al. 2019) showed prominent hydrogen lines and was classified as an SN II. This was later confirmed by a GTC spectrum that showed similar features (Elias-Rosa et al. 2019). Furthermore, this transient had PS1 detections ∼1 day after the event (Smith et al. 2019). Part of the evolution of this transient was followed up by the LOT (Tan et al. 2019).

ZTF19acymaru/AT2019wnh—This transient was discovered at r = 20.03 mag and highlighted in Andreoni et al. (2019a). The ZTF reference image did not show a visible host. Finally, the GTC spectrum revealed an SN Ia at redshift z[s] = 0.167 (Castro-Tirado et al. 2019a).

ZTF19acykzsp/AT2019wne—This candidate was first highlighted in Andreoni et al. (2019a), as it was discovered at r = 20.18 mag. The LT/SPRAT spectrum showed an SN Ia at maximum light at z[s] = 0.16 (Perley & Copperwheat 2019b).

ZTF19acyfoha/AT2019wkl—Similarly, ZTF19acyfoha was reported in Andreoni et al. (2019a) at g = 17.49 mag. It was located in one of the arms of a spiral galaxy with a CLU redshift of z[p] = 0.04. The candidate was observed with the SEDM at the P60, and its spectra showed clear features of an SN Ia at z[s] = 0.044.

ZTF19acymcwv/AT2019wni—This transient was discovered at r = 20.24 mag and reported in Andreoni et al. (2019a). The candidate is in the outskirts of an elliptical galaxy, and a spectrum taken with WHT revealed an SN Ia at z[s] = 0.09 (Brennan et al. 2019).

ZTF19acymixu/AT2019wrr—This candidate was first reported in Stein et al. (2019d), as it was discovered at r = 19.87 mag on top of a faint diffuse source. After ∼1.6 days, observations with Swift showed a source at b = 20.1 mag. However, it was later classified as an SN Ia at z[s] = 0.14 with a spectrum taken with the DBSP at the P200.

ZTF19acylvus/AT2019wnk—This transient was discovered at r = 19.60 mag, sitting on top of a faint galaxy without a known redshift. It was classified by the GTC as an SN Ia at z[s] = 0.1 (Castro-Tirado et al. 2019a).

ZTF19acymcna/AT2019wnn—This transient was detected at r = 20.74 mag in the nucleus of an elliptical galaxy. The GTC spectrum showed broad hydrogen features at z = 0.2, consistent with an AGN.

ZTF19acyldun/AT2019wrt—This candidate was reported with an initial magnitude of g = 19.8. The follow-up with the Swift telescope shown an active source in the ultraviolet (Oates et al. 2019). The observations performed by GTC discovered a source at z[s] = 0.057 with narrow Balmer lines consistent with a luminous blue variable (LBV; Castro-Tirado et al. 2019a), as it was also detected in 2012 by PS1. However, the source brightened to a peak absolute magnitude of ≈−18 mag, and we revise its classification to be an SN IIn. It additionally faded at a rate much slower than our α = 0.3 mag evolution threshold, with a coefficient of αr  = 0.09.

B.10.2. Slow Photometric Evolution

ZTF19acykyzj/AT2019wrg—This candidate was discovered at g = 20.55 and reported in Stein et al. (2019d). It was located in the outskirts of a spiral galaxy at unknown redshift; however, its slow magnitude evolution (αr  = −0.03) makes this transient not relevant.

ZTF19acymapa/AT2019wro—This source was detected at g = 20.31 and reported in Stein et al. (2019d). To calculate the evolution of this object, we have only used the first 2 nights of data, as there are no more data on this transient. Using this Δt, we obtain a slow-evolving transient with αr  = −0.06. Additionally, we note that the first two data points make a color consistent with gr = 0.

ZTF19acymaxu/AT2019wrp—This candidate was highlighted in Stein et al. (2019d) at r = 18.70 mag. It is on top of a faint PS1 source, and its slow magnitude evolution of αr  = 0.03 allows us to rule it out.

ZTF19acymlhi/AT2019wrs—The first detection of this candidate was of r = 19.54 mag, and its initial color was consistent with gr = 0 mag. Similar to ZTF19acymapa, the baseline used in this case was of Δt = 2 days, and the evolution showed a slow rise of αr  = −0.17.

B.10.3. Artifacts

ZTF19acykwsd/AT2019wnl—This transient was highlighted as an orphan source with two detections in different bands: r = 19.42 and g = 19.39 mag. We proceeded to obtain an LT/SPRAT spectrum; however, the source was not present in the acquisition image. Further investigation showed more sources around ZTF19acykwsd consistent with cross-talk.

B.10.4. Stellar Sources

ZTF19acykyqu/AT2019wre—This transient was detected at g = 21.13 mag and has a second detection 3.5 hr later at r = 20.86 mag. There are no more ZTF data on this object; however, there is a faint point source underneath the transient and a PS1-DR2 detection ∼1 month before the GW event. We then consider ZTF19acykyqu to be related to a stellar background source.

ZTF19acykyrz/AT2019wrf —Similar to ZTF19acykyqu, this source sits on a PS1 source that has a previous variability history. The first PS1-reported detection was in 2010, while the last PS1-reported detection was in 2014. As the ZTF only detected this source twice, at g = 20.97 and r = 20.16 mag, we posit that this candidate is related to the PS1 source underneath.

ZTF19acykzfy/AT2019wrh—This orphan transient was first discovered at g = 20.56 and detected ∼3.5 hr later at r = 20.96 mag. The galactic latitude of ZTF19acykzfy (b = −1573) and a nearby (<3'') detection in the PS1-DR2 catalog back the stellar origin of this transient.

ZTF19acyldum/AT2019wrn—The candidate was first reported by Stein et al. (2019d) with a magnitude of g = 19.78 mag. It was later detected twice: 3 hr later at r = 19.82 mag and 5 hr later at g = 19.84 mag. However, there is a PS1-DR2 detection within 1'' in 2010 and a faint source in the ZTF reference images. Therefore, we posit this candidate as a stellar variable and thus unrelated.

B.11. S200105ae and S200115j

For candidates identified within the sky map of S200105ae and S200115j, see Anand et al. (2020).

B.12. S200213t

We summarize the candidate counterparts to S200213t in Table 10 and the follow-up photometry in Table 18. Next, we discuss why we conclude that each one is unrelated. All of the transients described for this event (S200213t) were reported in Kasliwal et al. (2020).

Table 18. Follow-up Photometry for S200213t Candidates

NameIAU NameDateTelescopeFilter m (AB) σm mlim
ZTF20aamvqxlAT2020ciy2,458,893.3371LT i 20.170.1521.61
ZTF20aamvqxlAT2020ciy2,458,893.3406LT g 99.099.019.54
ZTF20aamvoxxAT2020cjg2,458,893.3733LT i 20.290.2121.30
ZTF20aamvoxxAT2020cjg2,458,893.3751LT r 21.470.1922.49
ZTF20aamvoxxAT2020cjg2,458,893.3768LT g 20.260.0323.36
ZTF20aamvtipAT2020cje2,458,893.3457LT i 20.680.0722.73
ZTF20aamvtipAT2020cje2,458,893.3475LT r 20.730.1122.52
ZTF20aamvtipAT2020cje2,458,893.3493LT g 20.800.0623.14
ZTF20aamvmzjAT2020cja2,458,893.3559LT g 20.450.0523.10
ZTF20aamvmzjAT2020cja2,458,906.7200LCO2m g 20.790.0920.91
ZTF20aamvmzjAT2020cja2,458,906.7350LCO2m r 20.320.0921.30
ZTF20aamvmzjAT2020cja2,458,893.9607LOT g 20.370.1099.0
ZTF20aamvmzjAT2020cja2,458,893.9607LOT r 20.580.1499.0
ZTF20aamvmzjAT2020cja2,458,893.9607LOT i 21.020.5199.0
ZTF20aamvoehAT2020cjc2,458,893.3559LT g 20.450.0523.10
ZTF20aamvoehAT2020cjc2,458,906.7200LCO2m g 20.790.0920.91
ZTF20aamvoehAT2020cjc2,458,906.7350LCO2m r 20.320.0921.30
ZTF20aanakwbAT2020cls2,458,893.9607LOT g 99.099.018.9
ZTF20aanakwbAT2020cls2,458,893.9607LOT r 21.120.3299.0
ZTF20aanakwbAT2020cls2,458,893.9607LOT i 20.970.3799.0
ZTF20aanaltdAT2020clt2,458,893.9607LOT g 21.470.2499.0
ZTF20aanaltdAT2020clt2,458,893.9607LOT r 19.340.0499.0
ZTF20aanaltdAT2020clt2,458,893.9607LOT i 19.980.1299.0
ZTF20aanakskAT2020clu2,458,893.9607LOT g 20.800.1499.0
ZTF20aanakskAT2020clu2,458,893.9607LOT r 20.790.1599.0
ZTF20aanakskAT2020clu2,458,893.9607LOT i 21.190.4799.0
ZTF20aanaoyzAT2020clw2,458,893.9607LOT g 21.460.4299.0
ZTF20aanaoyzAT2020clw2,458,893.9607LOT r 21.090.2299.0
ZTF20aanaoyzAT2020clw2,458,893.9607LOT i 20.750.3799.0
ZTF20aanakesAT2020cly2,458,894.5992APO g 99.099.023.50
ZTF20aanakesAT2020cly2,458,894.6012APO i 99.099.021.50
ZTF20aanakesAT2020cly2,458,894.6031APO r 99.099.023.00

Download table as:  ASCIITypeset image

B.12.1. Spectroscopically Classified

ZTF20aamvqxl/AT2020ciy—This transient was first reported in Kasliwal et al. (2020), as it was discovered at g = 20.45 mag, in the outskirts of a potential host. With the spectra taken with GTC, Valeev et al. (2020) classified the candidate as an SN Ia at z[s] = 0.1.

ZTF20aamvnth/AT2020cjb—Similarly, this candidate was first reported in Kasliwal et al. (2020); however, its potential host was a faint and diffuse galaxy visible in the PS1 image of the field. A spectrum from GTC classified this candidate as an SN II at z[s] = 0.061 (Castro-Tirado et al. 2020).

ZTF20aamvoxx/AT2020cjg—This transient was first observed at g = 19.99 mag, close to the nucleus of an elliptical galaxy. Data taken with GTC classified this candidate as an SN Ia at z[s] = 0.097 (Valeev et al. 2020).

ZTF20aamvtip/AT2020cje—The first detection of ZTF20aamvtip was at g = 20.7 mag and faded 0.2 mag in the r band after a day. The SDSS photometric redshift of the faint host was z[p] = 0.225. The GTC spectra classified it as an SN Ia at z[s] = 0.15 (Valeev et al. 2020).

ZTF20aamvnat/AT2020ciz—This transient was discovered at g = 18.93 mag, and, while originally thought orphan, a faint red counterpart in the PS1 and ZTF reference image suggested a stellar origin. Additionally, it is located at b = −562, backing up the stellar hypothesis. Finally, GTC spectra showed strong hydrogen lines at z[s] = 0, consistent with a galactic CV (Castro-Tirado et al. 2020).

ZTF20aamvodd/AT2020cjf —Similarly, this transient sits at b = −953 and has a faint red PS1 counterpart. It was later classified as a stellar flare at z[s] = 0.0 (Castro-Tirado et al. 2020) due to its Hα features.

ZTF20aamvoeh/AT2020cjc—This transient was discovered at g = 20.56 mag on top of an elliptical galaxy. We classified the candidate as an SN Ia at z[s] = 0.14 using the spectrum taken with the DBSP at the P200 telescope.

ZTF20aanaltd/AT2020clt—This transient was first reported in Andreoni et al. (2020c), as it was discovered at g = 20.81 mag in the outskirts of a faint red galaxy. The spectrum from the LRIS at the Keck observatory revealed an SN Ia at z[s] = 0.2 (De 2020).

ZTF20aanaoyz/AT2020clw—This transient was discovered at g = 21.50 mag on top of a faint PS1 elongated source. It was classified by GTC as an SN Ia at redshift z[s] = 0.276 (Hu et al. 2020).

ZTF20aamvpvx/AT2020clx—The first observation of this transient was at g = 20.30 mag in the nucleus of an elliptical galaxy. The GTC spectrum showed an SN II at redshift z[s] = 0.074 with prominent hydrogen features (De 2020).

ZTF20aanakcd/AT2020cmr—This candidate was discovered in the outskirts of an elongated, bright elliptical galaxy at g = 20.70 mag. The spectrum taken with the DBSP at the P200 classified it as an SN IIn at z[s] = 0.077 (Andreoni et al. 2020a).

ZTF20aanamcs/AT2020crc—This object was discovered close to the nucleus of an edge-on galaxy at g = 21.25 mag and z[s] = 0.093 and subsequently classified as an SN II (De 2020).

ZTF20aanakge/AT2020crd—This candidate was detected as an orphan at g = 20.64 mag. The spectrum taken with OSIRIS at the GTC classified it as an SN Ia at z[s] = 0.1272 (Hu et al. 2020).

B.12.2. Stellar

ZTF20aanaksk/AT2020clu—This candidate was first reported at g = 20.48 mag as an orphan transient. We rule out ZTF20aanaksk, as it has two previous detections in 2010 in the PS1-DR2 catalog, and we posit that it is related to a faint star in the background.

ZTF20aanakes/AT2020cly—This candidate was first detected at g = 21.11 mag and with a color consistent with g − r = 0. Follow-up with ARCTIC and GTC left only upper limits for this fast transient (Bellm & Graham 2020; Hu et al. 2020). However, there is an archival detection in the PS1-DR2 catalog 15 from the ZTF source. Thus, we reject this candidate.

B.12.3. Slow Photometric Evolution

ZTF20aamvmzj/AT2020cja—This transient sits at b = −1043; however, it does not seem to have a PS1 or ZTF counterpart, as with the previous stellar sources. The spectra taken with Keck I+LRIS and P200 only showed a featureless blue continuum (De 2020). It was first observed (Oates et al. 2020b) by the UVOT (Roming et al. 2005) at Swift 6.7 days after the merger, and it was only detected in the u band at u = 19.05 mag. It was later followed up but not detected in any bandpass (Oates et al. 2020a). Nonetheless, the magnitude evolution of the transient was otherwise flat, and it slowly faded over time with αr  = 0.04.

ZTF20aanaqhe/AT2020cre—This transient was detected at g = 20.88 mag on an elliptical galaxy at a photometric redshift of z[p] = 0.16. Its slow rise of αg  = −0.08 was inconsistent with the rise of a fast transient.

ZTF20aanakwb/AT2020cls—This transient was first reported in Andreoni et al. (2020c) at g = 21.03 mag, offset from a bright Gaia point source (g = 15.27 mag). This transient was detected by the LOT 12 hr later at an r-band magnitude consistent with no evolution. The initial color gr is consistent with 0 mag. In the ZTF reference image, there is a faint point source, which indicates stellar activity.

B.12.4. Outside the GW Map

ZTF20aanallx/AT2020clv—This transient was first reported in Andreoni et al. (2020c) at g = 21.11 mag and discovered at a galactic latitude of b = −1143. It is offset from an elliptical galaxy; however, it falls in a fairly crowded region. The rejection criterion we used for this transient is the fact that it is not within the 95% credible level of the latest LALInference map for S200213t.

Footnotes

Please wait… references are loading.
10.3847/1538-4357/abc335