DESAlert: Enabling Real-Time Transient Follow-Up with Dark Energy Survey Data

Abstract

The Dark Energy Survey is undertaking an observational programme imaging 1/4 of the southern hemisphere sky with unprecedented photometric accuracy. In the process of observing millions of faint stars and galaxies to constrain the parameters of the dark energy equation of state, the Dark Energy Survey will obtain pre-discovery images of the regions surrounding an estimated 100 gamma-ray bursts over 5 yr. Once gamma-ray bursts are detected by, e.g., the Swift satellite, the DES data will be extremely useful for follow-up observations by the transient astronomy community. We describe a recently-commissioned suite of software that listens continuously for automated notices of gamma-ray burst activity, collates information from archival DES data, and disseminates relevant data products back to the community in near-real-time. Of particular importance are the opportunities that non-public DES data provide for relative photometry of the optical counterparts of gamma-ray bursts, as well as for identifying key characteristics (e.g., photometric redshifts) of potential gamma-ray burst host galaxies. We provide the functional details of the DESAlert software, and its data products, and we show sample results from the application of DESAlert to numerous previously detected gamma-ray bursts, including the possible identification of several heretofore unknown gamma-ray burst hosts.

1 INTRODUCTION

The Dark Energy Survey (DES) is an observational programme covering 5 000 deg² of the southern sky, utilising the DECam instrument (Flaugher et al., 2015) on the Blanco 4-m telescope at Cerro Tololo Interamerican Observatory, from 2013 August to 2018 February (Abbott et al., 2005). Over the 525 nights of the survey, the DES will observe in five filters broadly similar to the SDSS griz filter set (Gunn et al., 1998), but with some important differences—particularly, higher quantum efficiency at near-infrared wavelengths and the additional Y filter (see Figure 1). DES will reach a photometric accuracy of 1–2% for its two interleaved surveys—the wide-field survey covering the full footprint and the supernova survey covering smaller regions with increased cadence (Diehl et al., 2014)—and it will have significant overlap with other wide-area surveys, such as the Sloan Digital Sky Survey’s Stripe 82 (Abazajian et al., 2009), the Vista Hemisphere Survey (McMahon et al., 2013), and the South Pole Telescope Survey (Ruhl et al., 2004). The four Key Science programmes of the DES comprise observations of SNe Ia, large-scale galaxy clustering, galaxy clusters, and weak gravitational lensing; together these four probes will be used to measure the dark energy equation of state with unprecedented precision. The DES data have many uses beyond these primary science goals, however. In this work, we describe a service to provide data products to the transient observational community, particularly related to gamma-ray bursts located within the DES footprint.

Figure 1. Throughput as a function of wavelength of the DECam optical train, including the various filters the DES uses. These throughputs are calculated relative to the use of no filter at 9 000 ${\text{\AA}}$ .

Once a region of the sky has been observed by the DES, those observations will be useful whenever a transient (e.g., a gamma-ray burst) is detected in the same region. The DESAlert system is modelled upon the SkyAlert system (Williams et al., 2009), and it bears similarities to the SDSS transient notification system (Cool et al., 2006), though it focusses exclusively on data produced by the DES, and (at least initially) it relies on a single source for triggers. When a VOEvent notice (Seaman et al., 2011) is disseminated based on data from the Burst Alert Telescope (BAT) or X-Ray Telescope (XRT) aboard the Swift satellite (Barthelmy et al., 1999), the DESAlert system parses the notice for temporal and positional information, and then searches the DES data archives to find all observations of that region. DESAlert then provides finder images of the region derived from DES data, as well as a subset of data derived from DES observations of all nearby stars and galaxies. The finder images show other objects near the GRB, whilst the catalogue of stars provides nearby standards for the purpose of immediate relative photometry. Meanwhile, the galaxy catalogue provides critical information on potential host galaxies—especially magnitude and photometric redshift—for the given GRB. All of these data products will be of use to those who need to make decisions regarding the allocation of scarce resources for follow-up observations of these GRBs. For example, if a potential host has an extremely low (or extremely high) redshift, observers may decide that the GRB warrants further study; thus, they would begin follow-up observations as soon as possible. Alternately, if a host galaxy has unusual colours (as described by the multi-band DES observations), that may be indicative of unusual metallicity or dust content, again prompting observers to allocate observational resources to follow-up the detection of these transients.

By the conclusion of Year 2 in 2015 February, DES had observed nearly all of its survey footprint, with multi-epoch imagery covering the vast majority of that area—see Figure 2. Year 3 saw the completion of coverage of the entire footprint, with subsequent data-taking increasing the number of observed epochs (and thus the effective co-add survey depth) at each position within the footprint. Given the area covered, and assuming randomly distributed GRBs detected by Swift at a rate of ~ 100 yr⁻¹, we expect 10–20 GRBs annually to have DES pre-discovery images that are amenable to analysis and publication via the DESAlert algorithm. We encourage all interested observers to take advantage of these data products provided to the astronomical community.

Figure 2. The DES footprint, with current coverage in the i band shown. Grey is the full survey area, whilst areas covered by 1, 2, 3, 4, or 5+ observations are coloured red, orange, light blue, dark blue, and green, respectively.

2 THE DESALERT ALGORITHM

The DESAlert algorithm is shown schematically in Figure 3. Though it is similar in effect to other VOEvent-focussed software such as dakota or comet (Swinbank, 2014), in order to maintain minimal dependency on external code, it does not rely on these software packages—it does, however, makes use of the voeventlib libraries (Williams et al., 2012). The functional code for DESAlert is written in python and sql, and will be made available online via the Astrophysics Source Code Library (Allen et al., 2012). It encapsulates all functions necessary to complete the following steps:

• • Listen for VOEvent notices.

• • Select events confirmed to be GRBs by Swift.

• • Parse temporal and position data from notices.

• • Query the DES database for objects and images in a pre-determined region surrounding the GRB.

• • Extract relevant archival DES data for stars and galaxies.

• • Derive data products from extracted data.

• • Publish DESAlert data products as VOEvent notices, as well as to the DESAlert webpage.

Figure 3. The DESAlert algorithm flowchart.

First, the software opens a socket connection and receives (XML-formatted) messages from the VOEvent server as a series of packets, built up byte-by-byte until the full message is received. Error checking ensures that malformed (or improperly received) messages are deleted before the algorithm returns to listen mode. The XML is then parsed to determine the type of message (e.g., imalive, test, or observation). The first of these is necessary for the socket connection to be maintained at the client end, and it results in an identical reply from the client (imalive) so that the socket connection is likewise maintained at the server end. All other types except observation are discarded. Observations, however, have relevant data for each GRB extracted, including GRB position (RA, Dec), burst time, and detecting instrument. In order to ensure near-real-time response from DESAlert to initial GRB detections (almost always by the BAT instrument), we process the initial notice for each GRB. Typically, subsequent VOEvent notices from Swift’s XRT and/or UVOT instruments refine the position (or position uncertainty) of the GRB; in that case, we process the first such subsequent notice in the same fashion as the initial notice, with new and improved information superceding the old. In general, the XRT or UVOT position is sufficiently accurate (with uncertainties of only a few arcseconds) that processing of further notices is not required, so they are discarded.

Based on the extracted GRB data, the python code then calls a custom-made jython-based command-line database interface to query the DES archival catalogue of sources in order to find any stars or galaxies within a box ±60 arcsec in RA and Dec of the BAT-determined GRB position, or within a ±30 arcsec box for XRT-determined position. These objects have previously been extracted from the processed (and co-added) DES Multi-Extension FITS images, and have had a great many parameters determined by the Data Management pipeline (Desai et al., 2012) running SourceExtractor (Bertin & Arnouts, 1996), including magnitudes (and uncertainties) for every observed filter, as well as object classification (either star or galaxy). Once the appropriate data are acquired from the DES database they are then stored, via sql Insert commands, in a local database connected to the machine running the DESAlert python code, and are made available to the DESAlert in several ways, as detailed in Section 3. A second query of the DES database finds all g, r, and i images containing the GRB position, from which the nearby objects have been extracted.

Whilst access to this type of data via publicly available online catalogues may be routine for GRB follow-up efforts, DESAlert has the advantage of accessing recent (i.e., proprietary) DES data, which includes objects with better than 2% photometric accuracy down to magnitudes fainter than g = 25. This is significantly fainter than the limits of other catalogues, e.g., the Digitized Sky Survey or 2MASS (Skrutskie at al., 2006), often used for this purpose. The DESAlert magnitude limits also compare favorably to those of GROND (Greiner et al., 2008), whilst the expected photometric accuracy of DES is better, and DES also makes use of Y-band imagery.

3 DESALERT DATA PRODUCTS

Once the software implementing the DESAlert algorithm has selected the relevant image segments and composed its catalogue of nearby objects, it disseminates the information of potential relevance to those seeking to follow-up the GRB detection with further observations. The primary data products produced by DESAlert are based on pre-discovery images of the regions around Swift-detected GRBs. The initial products are (XML-formatted) VOEvent notices, listing:

• • basic GRB parameters, including position, time, and discovering instrument;

• • closest stars to the GRB, including positions and magnitudes;

• • closest galaxies to the GRB, including positions, magnitudes, photometric redshifts, and chance alignment probabilities;

• • links to the finder images (in .fz and .jpg formats);

• • links to the DESAlert webpage containing a database with additional information for all objects near the GRB.

Finder images provided by DESAlert are processed and co-added DES images, each of which covers an area on the sky of approximately 0.75° on a side—although depending on the position of the GRB and its associated uncertainty, several images may be provided to completely cover the nominal search area. These images are provided in g, r, and i filters, when available. Links to the original images for each filter are published in the VOEvent notice, and also provided on the DESAlert webpage ¹ .

In order to faciliate relative photometric measurements of the optical counterparts of GRBs, the VOEvent notices provide magnitudes (and uncertainties) in each filter in a range of magnitudes (typically 16–26, depending on filter, with 1–2% photometric accuracy) for several of the nearest stars within the search box centred on the GRB position. Faint stars are far more likely to be positioned closest to any given GRB (and thus included in the XML notice), but information for all stars in the full region is stored in a similar format in the ancillary data available on the DESAlert website.

Likely of greatest interest to those desiring to follow up GRB observations are the DES pre-discovery catalogues of potential GRB host galaxies. The VOEvent notices provide positions, magnitudes (and uncertainties), photometric redshift information (when available), and chance alignment probabilities for the nearest galaxies within the search box centred on the GRB position. Information for all galaxies in this same region is stored in a similar format in the ancillary data available on the DESAlert website. For the subset of galaxies with no photometric redshift determination, we estimate the redshift ‘on the fly’ with an empirical method based upon their relative gri magnitudes (Lopes, 2007). We only report physically realistic (i.e., positive) calculated values in the DESAlert data products (failures of the estimator are assigned a value of ‘-9999’). Because of the limited applicability of this empirical method, we stress that these values are approximations that will be supplanted by more precise determinations from the DES Data Management pipeline as they become available.

Host galaxies of long GRBs are expected to be precisely co-located with the GRB, whilst short GRBs may be several arcseconds distant from their original host. If no galaxy is found within 10 arcsec (for XRT-determined positions), the DESAlert VOEvent notice instead reports the 10σ galaxy detection limit derived (Rykoff, Rozo, & Keisler, 2016) from the Year 1 co-added observations – g, r, i = 23.4±0.2, 23.1±0.2, 22.5±0.2, respectively, over the vast majority of the footprint (though not at the edges where there is less overlap amongst observations). A galaxy undetected even down to these limits (especially as the Survey progresses and the limits are extended even fainter) may indicate a high-redshift GRB (and host)—a particularly intriguing target for follow-up observations. Meanwhile, the DESAlert database still includes all objects found within the full search area.

4 TESTING THE DESALERT ALGORITHM

In addition to being submitted to a ‘code review’ by an experienced software engineer, each step of the DESAlert code outlined above has been individually tested, whilst end-to-end tests of the software show that all variations in expected VOEvent inputs are handled properly and output correct data products, even in rare and subtlely challenging cases (e.g., when a GRB is very close to RA=0.0, objects are returned with both RA > 0 and RA < 360). Worth noting also for desalert users are ‘edge’ cases where a GRB is near the border of the DES footprint (cf. Figure 2). Obviously, in this case, DESAlert can only return objects observed by DES, so the output object list may not be a true reflection of all objects that would have been contained within the search box. Therefore, a warning of potential incompleteness in the object catalogue is included with the VOEvent notice.

By the conclusion of Year 1 in 2014 February, DES had observed of order 2 500 deg² across the southern sky. A variety of tests were performed with the DESAlert algorithm using both the Year 1 and Science Verification (Year 0) data (Diehl et al., 2014). First, we simulated VOEvent notices with systematically varying positions throughout the DES footprint—though of course the real-time nature of DESAlert was not exercised in this way, we nevertheless could determine in a statistical way the expected impact of DESAlert. Of the 45 simulated notices input to DESAlert, 23 were found to have archival DES data matching the locations, each of which had of order 500 objects (stars or galaxies) within 0.1° of the nominal GRB position. This yield is consistent with statistical expectations from a survey region that is 50% covered; with the data from Year 1 to Year 3 (and the start of Year 4) now populating the DES database, the future yield for DESAlert should be significantly higher. Next, to test the real-time processing capabilities of DESAlert, a Swift VOEvent notice of a newly discovered GRB was received and processed, with the software taking approximately 1 min to execute the full algorithm—parsing the notice, querying the relevant DES databases, building the VOEvent notice, and ‘submitting’ it (albeit to an internal recipient rather than the public VOEvent network).

5 RESULTS FROM THE APPLICATION OF DESALERT TO PAST BURSTS

To test the effectiveness of DESAlert specifically in finding GRB host galaxies, we compare positions of DESAlert galaxies with a selection of GRBs previously detected by Swift, along with a number of GRBs detected by BeppoSAX (Boella et al., 1997) and the satellites of the InterPlanetary Network (Hurley, 1998) such as HETE-II (Ricker et al., 2002). Many (though not all) of these bursts have spectroscopically confirmed host galaxies drawn from The Optically Unbiased GRB Host (TOUGH) Survey (Hjorth et al., 2012; Jakobsson et al., 2012), as well as GHostS, the GRB Host Studies (Savaglio, Glazebrook, & Le Borgne, 2006). Of the 45 GRBs with XRT or other precise positions for which desalert searches returned nearby objects with photometric redshifts, 16 were deemed sufficiently close (within 5 arcsec) to a galaxy to warrant more detailed examination. These are GRBs 000210, 050219B, 060614A, 061007A, 071227A, 080514B, 080916A, 081109A, 090827A, 091018A, 110206A, 120701A, 140413A, 140928A, 151111A, and 160422A.

Of these 16, seven have spectroscopically confirmed redshifts, whilst nine do not. The galaxy closest to GRB000210 (only 0.21 arcsec away—smaller than the pixel scale of DECam) has a photometric redshift derived by DES of $z_{\text{phot}}$ = 0.844 (a difference of 0.3% from the spectroscopic redshift of $z_{\text{spec}}=0.846$ ). Furthermore, though the filter response curves are different, DES photometry is consistent with previously reported observations of the host galaxy (Christensen, Hjorth, & Gorosabel 2004). Next, the galaxy closest to GRB081109A (2.93 arcsec away—well within the 4.8 arcsec uncertainty reported by XRT) has a photometric redshift derived by DES of $z_{\text{phot}}$ = 0.906 (a difference of 8.0% from the spectroscopic redshift of $z_{\text{spec}}=0.979$ ). DES photometry is consistent with the upper limits on host magnitude from Swift UVOT (Kuin, 2008), the REM Telescope (D’Avanzo, 2008) and the Faulkes Telescope-South (Guidorzi, 2008), though all have significantly brighter (more than one magnitude) limits than the DES observations. Third, the galaxy closest to GRB091018A (2.16 arcsec away—close, but outside the reported 0.6 arcsec position uncertainty from XRT) has a photometric redshift derived by DES of $z_{\text{phot}}=1.01$ (a difference of 3.9% from the spectroscopic redshift of $z_{\text{spec}}=0.971$ ). Once again, DES photometry matches well with observations of the host galaxy by GROND, Gemini South/GMOS, and Faulkes Telescope-South (Wiersema et al., 2012). The galaxies closest to the other four GRBs have photometric redshifts that do not reflect the spectroscopic redshifts as accurately (differences of 20% to nearly 50%). See Table 1 for details of all of these candidate host galaxies, as well as the galaxies closest to the GRBs without spectroscopically confirmed redshifts.

Table 1. Parameters of GRB-possible host galaxy matches, including GRB ID, galaxy position, galaxy magnitudes, angular separation from GRB, chance alignment probability, photometric redshift, and spectroscopic redshift.

To determine the general chance alignment of these galaxies with the GRB positions as determined by BAT, we start by finding the total number of galaxies in 80 arcsec × 80 arcsec searchboxes around a large subsample of all GRBs that were tested with DESAlert. Of those searches that returned nearby objects (whether with photo-z’s or not), there were 454 galaxies in the regions around 65 GRBs, totaling 416 000 arcsec²—approximately one galaxy per 910 arcsec²—see Figure 4. The probability of a chance alignment (P $_{\text{chance}}$ ) within a single 3.97 arcsec × 3.97 arcsec box (corresponding to the largest angular separation for any of the potential matches) is simply the ratio of the two areas; that is, P $_{\text{chance}}$ =1.72%. Of course, more than a single search was performed; to determine the chance probability of no matches in 45 searches, we calculate P ₄₅ = [1−P $_{\text{chance}}$ ]⁴⁵ = 0.458. The chance probability of one or more matches for a single GRB, then, is 1 − P ₄₅ = 0.542, whilst the chance probability of 16 independent matches is P ₁₆ = (0.542)¹⁶ = 5.47 × 10⁻⁵. That is, the probability that at least one of the 16 matches is the true host of the corresponding GRB is 99.9945%.

Figure 4. (Left) Number of galaxies as a function of magnitude returned by DESAlert from 80 arcsec × 80 arcsec search boxes around 65 GRBs with BAT positions. (Right) The cumulative number of galaxies equal to (or brighter than) each given magnitude. The total number of objects classified as galaxies within these 416 000 arcsec² is 454, resulting in (on average) approximately one galaxy per 910 arcsec².

We also performed a more refined chance alignment analysis with a subsample of 38 GRBs with XRT positions, taking into account the individual galaxies’ magnitudes and separations from the nominal GRB positions. The total area searched was 34 200 arcsec², within which 89 galaxies were found with magnitudes 20 < g < 26 and angular separations < 30 arcsec. We calculate that an angular separation of 0.216 arcsec for a $g<25{\text{th}}$ mag galaxy (cf. GRB00210) has a chance probability of only 0.011%. Similarly, angular separations of 2.93 and 2.16 arcsec for g $<24{\text{th}}$ mag galaxies (cf. GRBs 081109A and 091018A) have a chance probability of 1.78 and 0.968%, respectively, though none of these probabilities factor in the entire ensemble of searches and matches. Figure 5 shows the cumulative chance alignment probability as a function of angular separation and galaxy magnitude. For those wishing to make decisions regarding allocation of valuable follow-up observational resources, suitable cut-offs in probability space can be straightforwardly derived from this information—specifically, we note that any bright ( $g<22{\text{nd}}$ mag) galaxy has a very low probability of chance alignment at any separation up to at least 20 arcsec, whilst any galaxy has a very low probability of being within 5 arcsec, regardless of magnitude. We also note that these probabilities are, if anything, underestimates of the significance of alignments, since the positions used in the analysis are, by construction, correlated with GRBs (and thus with the actual host galaxies), so any arbitrary point on the sky is less likely to have a galaxy nearby than these positions.

Figure 5. Probability of chance alignment of galaxies within the specified angular separation from the nominal GRB position and brighter than the specified magnitude, derived from $30\,\text{arcsec} \times 30\,\text{arcsec}$ search boxes around 38 GRBs. The total number of objects classified as galaxies within these 34 200 arcsec² is 89, resulting in (on average) approximately one galaxy per 384 arcsec².

Given the low probabilities associated with the observed galaxy alignments, the correspondence between the spectroscopic and photometric redshifts, and the similarity of the DES and non-DES photometry, we claim that DESAlert has successfully found the host for GRB000210, and has with high probability found the hosts of GRB081109A and GRB091018A. Though in the absence of spectroscopic redshift information, we cannot say with certainty that the additional galaxy matches are indeed the hosts of GRBs 050219B, 080514B, 090827A, 110206A, 120701A, 140413A, 140928A, 151111A, or 160422A, the low probabilities of chance alignment alone provide intriguing evidence pointing in that direction. Most importantly, we show that DESAlert can provide ideal candidates for real-time follow-up observations that could confirm or refute the status of proposed GRB host galaxies.

After completing the search of archival bursts, we tested the DESAlert algorithm with bursts detected by Swift during the Year 1 observations of DES. In Appendices A and B, we present an example of the data products related to a single burst (GRB131105A) that are provided to the community by DESAlert—specifically, the VOEvent XML notice and Finder Image, respectively. Table 2 shows a subset of the relevant data for selected stars and galaxies near this GRB as well. Table entries include object position, grizY magnitudes, the ${spread}\_{model}$ value, object separation from the nominal GRB positon (in arcseconds), object classification, chance alignment probability, photometric redshift, and object number as defined internally by DESAlert (where the same number indicates additional observational epochs of the same object). ${Spread}\_{model}$ is a neural-network based star/galaxy classifier within SourceExtractor; values greater than 0.003 correspond to galaxies (Desai et al., 2012). We calculate the mean of the ${spread}\_{model}$ values for all filters, with each weighted by the inverse square of the uncertainty in the observations for that filter, yielding a value that relies most heavily upon the most accurate observation, but still incorporates all available data. As with other GRBs we tested, the photometric redshifts are calculated following the method described above in Section 3—for those observations with physically realistic values (i.e., $z_{\text{phot}}$ > 0), the values derived from repeated observations of the same object are broadly consistent (generally within ±10–20% of one another). All stars and galaxies in the region around the GRB are stored in a similar fashion in the ancillary data available on the DESAlert website.

Table 2. Parameters of selected galaxies and stars near GRB131105A, including position, magnitudes, star/galaxy classification ( ${Spread}\_{Model}$ ) value, angular separation from GRB, star/galaxy classification, chance alignment probability, photometric redshift, and DESAlert object ID (useful particularly for identifying duplicate observations of the same object).

6 FUTURE DEVELOPMENT OF DESALERT

Though DESAlert is fully functional and has made several confirmed (and proposed) matches to GRB hosts, we will continue to improve the functionality of DESAlert through future code releases. Dubbed DESAlert++, the next iteration of the DESAlert algorithm will incorporate several new aspects. In particular, we are investigating alternate search methods to including transients with larger position uncertainties, such as Fermi-detected GRBs with position uncertainties close to 1° (Atwood et al., 2009). One particularly promising category of transients for inclusion in DESAlert++ is Fast Radio Bursts (FRBs, Champion et al., 2015). Though their positions are not well known (for example, the beam size of the Parkes radio telescope that has detected numerous FRBs is 14 arcmin in diameter), their redshift can be significantly constrained—for example, Petroff et al. (2015) have determined that z < 0.5 for FRB 140514. Despite the probability of many galaxies being observed by DES in a search box more than 10 arcmin across, photometric redshift matches could positively identify optical counterparts (or hosts) of FRBs, or at the very least facilitate statistical approaches to identifying likely sources (similar to the method used above to identify multiple potential new GRB host galaxies).

Next, multi-messenger transient detections (e.g., gravitational wave observations) stemming from the Astrophysical Multimessenger Observatory Network (Smith et al., 2013) provide yet another potentially interesting avenue of further development of DESAlert. Finally, we are exploring the possibility of including resolved stellar transients such as disappearing red supergiants (Kochanek et al., 2008) or galactic stellar flares—in such cases, nearby stars (rather than galaxies) become the interesting targets for which the transient follow-up community can utilise the data products released by DESAlert.

7 CONCLUSIONS

DESAlert is an algorithm implemented in python and sql to receive automated notices of GRB parameters from VOEvent Notification triggers, and to provide the astronomical community with finder images as well as catalogues of nearby stars and galaxies (with relevant quantities such as positions, magnitudes, and photometric redshifts). The details of the algorithm have been laid out in the previous Sections, and a sample image and catalogue shown to familiarise readers with the DESAlert data products. Based on tests using historical GRBs, we confirm the effectiveness of DESAlert by finding multiple previously discovered GRB hosts (matching in both position and redshift, and consistent with independent photometric observations), and further by detecting several potential GRB hosts (matching in position, but with no spectroscopic redshift to confirm the DES-derived photometric redshift).

During the 5-yr lifetime of the DES, we expect to provide data products for of order 100 Swift-detected GRBs—though the DESAlert system is expected to function well beyond the formal lifetime of the DES itself. Extensions to DESAlert (dubbed DESAlert++) are currently being explored based upon other GRB-detecting instruments such as Fermi (or based on the incorporation of other transients such as FRBs into the DESAlert algorithm). To estimate the annual rate of GRBs from all sources likely to be within the DES footprint, we searched the SkyAlert database for unique GRB positions from all sources from one year; of the 230 bursts in the database, 34 (roughly 3 per month) fall within the DES footprint and could potentially trigger DESAlert++.

We encourage all observers interested in follow-up observations of transient astrophysical phenomena such as GRBs to avail themselves of the VOEvent notices and web-based data archive provided by DESAlert.