GW170104 and me

On 4 January 2017, Advanced LIGO made a new detection of gravitational waves. The signal, which we call GW170104 [bonus note], came from the coalescence of two black holes, which inspiralled together (making that characteristic chirp) and then merged to form a single black hole.

On 4 January 2017, I was just getting up off the sofa when my phone buzzed. My new year’s resolution was to go for a walk every day, and I wanted to make use of the little available sunlight. However, my phone informed me that PyCBC (one or our search algorithms for signals from coalescing binaries) had identified an interesting event. I sat back down. I was on the rota to analyse interesting signals to infer their properties, and I was pretty sure that people would be eager to see results. They were. I didn’t leave the sofa for the rest of the day, bringing my new year’s resolution to a premature end.

Since 4 January, my time has been dominated by working on GW170104 (you might have noticed a lack of blog posts). Below I’ll share some of my war stories from life on the front line of gravitational-wave astronomy, and then go through some of the science we’ve learnt. (Feel free to skip straight to the science, recounting the story was more therapy for me).

Normalised spectrograms for GW170104

Time–frequency plots for GW170104 as measured by Hanford (top) and Livingston (bottom). The signal is clearly visible as the upward sweeping chirp. The loudest frequency is something between E3 and G♯3 on a piano, and it tail off somewhere between D♯4/E♭4 and F♯4/G♭4. Part of Fig. 1 of the GW170104 Discovery Paper.

The story

In the second observing run, the Parameter Estimation group have divided up responsibility for analysing signals into two week shifts. For each rota shift, there is an expert and a rookie. I had assumed that the first slot of 2017 would be a quiet time. The detectors were offline over the holidays, due back online on 4 January, but the instrumentalists would probably find some extra tinkering they’d want to do, so it’d probably slip a day, and then the weather would be bad, so we’d probably not collect much data anyway… I was wrong. Very wrong. The detectors came back online on time, and there was a beautifully clean detection on day one.

My partner for the rota was Aaron Zimmerman. 4 January was his first day running parameter estimation on live signals. I think I would’ve run and hidden underneath my duvet in his case (I almost did anyway, and I lived through the madness of our first detection GW150914), but he rose to the occasion. We had first results after just a few hours, and managed to send out a preliminary sky localization to our astronomer partners on 6 January. I think this was especially impressive as there were some difficulties with the initial calibration of the data. This isn’t a problem for the detection pipelines, but does impact the parameters which we infer, particularly the sky location. The Calibration group worked quickly, and produced two updates to the calibration. We therefore had three different sets of results (one per calibration) by 6 January [bonus note]!

Producing the final results for the paper was slightly more relaxed. Aaron and I conscripted volunteers to help run all the various permutations of the analysis we wanted to double-check our results [bonus note].

Estimated waveforms from different models for GW170104

Recovered gravitational waveforms from analysis of GW170104. The broader orange band shows our estimate for the waveform without assuming a particular source (wavelet). The narrow blue bands show results if we assume it is a binary black hole (BBH) as predicted by general relativity. The two match nicely, showing no evidence for any extra features not included in the binary black hole models. Figure 4 of the GW170104 Discovery Paper.

I started working on GW170104 through my parameter estimation duties, and continued with paper writing.

Ahead of the second observing run, we decided to assemble a team to rapidly write up any interesting binary detections, and I was recruited for this (I think partially because I’m not too bad at writing and partially because I was in the office next to John Veitch, one of the chairs of the Compact Binary Coalescence group,so he can come and check that I wasn’t just goofing off eating doughnuts). We soon decided that we should write a paper about GW170104, and you can decide whether or not we succeeded in doing this rapidly…

Being on the paper writing team has given me huge respect for the teams who led the GW150914 and GW151226 papers. It is undoubtedly one of the most difficult things I’ve ever done. It is extremely hard to absorb negative remarks about your work continuously for months [bonus note]—of course people don’t normally send comments about things that they like, but that doesn’t cheer you up when you’re staring at an inbox full of problems that need fixing. Getting a collaboration of 1000 people to agree on a paper is like herding cats while being a small duckling.

On of the first challenges for the paper writing team was deciding what was interesting about GW170104. It was another binary black hole coalescence—aren’t people getting bored of them by now? The signal was quieter than GW150914, so it wasn’t as remarkable. However, its properties were broadly similar. It was suggested that perhaps we should title the paper “GW170104: The most boring gravitational-wave detection”.

One potentially interesting aspect was that GW170104 probably comes from greater distance than GW150914 or GW151226 (but perhaps not LVT151012) [bonus note]. This might make it a good candidate for testing for dispersion of gravitational waves.

Dispersion occurs when different frequencies of gravitational waves travel at different speeds. A similar thing happens for light when travelling through some materials, which leads to prisms splitting light into a spectrum (and hence the creation of Pink Floyd album covers). Gravitational waves don’t suffered dispersion in general relativity, but do in some modified theories of gravity.

It should be easier to spot dispersion in signals which have travelled a greater distance, as the different frequencies have had more time to separate out. Hence, GW170104 looks pretty exciting. However, being further away also makes the signal quieter, and so there is more uncertainty in measurements and it is more difficult to tell if there is any dispersion. Dispersion is also easier to spot if you have a larger spread of frequencies, as then there can be more spreading between the highest and lowest frequencies. When you throw distance, loudness and frequency range into the mix, GW170104 doesn’t always come out on top, depending upon the particular model for dispersion: sometimes GW150914’s loudness wins, other times GW151226’s broader frequency range wins. GW170104 isn’t too special here either.

Even though GW170104 didn’t look too exciting, we started work on a paper, thinking that we would just have a short letter describing our observations. The Compact Binary Coalescence group decided that we only wanted a single paper, and we wouldn’t bother with companion papers as we did for GW150914. As we started work, and dug further into our results, we realised that actually there was rather a lot that we could say.

I guess the moral of the story is that even though you might be overshadowed by the achievements of your siblings, it doesn’t mean that you’re not awesome. There might not be one outstanding feature of GW170104, but there are lots of little things that make it interesting. We are still at the beginning of understanding the properties of binary black holes, and each new detection adds a little more to our picture.

I think GW170104 is rather neat, and I hope you do too.

As we delved into the details of our results, we realised there was actually a lot of things that we could say about GW170104, especially when considered with our previous observations. We ended up having to move some of the technical details and results to Supplemental Material. With hindsight, perhaps it would have been better to have a companion paper or two. However, I rather like how packed with science this paper is.

The paper, which Physical Review Letters have kindly accommodated, despite its length, might not be as polished a classic as the GW150914 Discovery Paper, but I think they are trying to do different things. I rarely ever refer to the GW150914 Discovery Paper for results (more commonly I use it for references), whereas I think I’ll open up the GW170104 Discovery Paper frequently to look up numbers.

Although perhaps not right away, I’d quite like some time off first. The weather’s much better now, perfect for walking…

Looking east across Lake Annecy, France

Success! The view across Lac d’Annecy. Taken on a stroll after the Gravitational Wave Physics and Astronomy Workshop, the weekend following the publication of the paper.

The science

Advanced LIGO’s first observing run was hugely successful. Running from 12 September 2015 until 19 January 2016, there were two clear gravitational-wave detections, GW1501914 and GW151226, as well as a less certain candidate signal LVT151012. All three (assuming that they are astrophysical signals) correspond to the coalescence of binary black holes.

The second observing run started 30 November 2016. Following the first observing run’s detections, we expected more binary black hole detections. On 4 January, after we had collected almost 6 days’ worth of coincident data from the two LIGO instruments [bonus note], there was a detection.

The searches

The signal was first spotted by an online analysis. Our offline analysis of the data (using refined calibration and extra information about data quality) showed that the signal, GW170104, is highly significant. For both GstLAL and PyCBC, search algorithms which use templates to search for binary signals, the false alarm rate is estimated to be about 1 per 70,000 years.

The signal is also found in unmodelled (burst) searches, which look for generic, short gravitational wave signals. Since these are looking for more general signals than just binary coalescences, the significance associated with GW170104 isn’t as great, and coherent WaveBurst estimates a false alarm rate of 1 per 20,000 years. This is still pretty good! Reconstructions of the waveform from unmodelled analyses also match the form expected for binary black hole signals.

The search false alarm rates are the rate at which you’d expect something this signal-like (or more signal-like) due to random chance, if you data only contained noise and no signals. Using our knowledge of the search pipelines, and folding in some assumptions about the properties of binary black holes, we can calculate a probability that GW170104 is a real astrophysical signal. This comes out to be greater than 1 - (3\times10^5) = 0.99997.

The source

As for the previous gravitational wave detections, GW170104 comes from a binary black hole coalescence. The initial black holes were 31.2^{+8.4}_{-6.0} M_\odot and 19.4^{+5.3}_{-5.9} M_\odot (where 1 M_\odot is the mass of our Sun), and the final black hole was 48.7^{+5.7}_{-4.6} M_\odot. The quoted values are the median values and the error bars denote the central 90% probable range. The plot below shows the probability distribution for the masses; GW170104 neatly nestles in amongst the other events.

Binary black hole masses

Estimated masses for the two black holes in the binary m_1 \geq m_2. The two-dimensional shows the probability distribution for GW170104 as well as 50% and 90% contours for all events. The one-dimensional plot shows results using different waveform models. The dotted lines mark the edge of our 90% probability intervals. Figure 2 of the GW170104 Discovery Paper.

GW150914 was the first time that we had observed stellar-mass black holes with masses greater than around 25 M_\odot. GW170104 has similar masses, showing that our first detection was not a fluke, but there really is a population of black holes with masses stretching up into this range.

Black holes have two important properties: mass and spin. We have good measurements on the masses of the two initial black holes, but not the spins. The sensitivity of the form of the gravitational wave to spins can be described by two effective spin parameters, which are mass-weighted combinations of the individual spins.

  • The effective inspiral spin parameter \chi_\mathrm{eff} qualifies the impact of the spins on the rate of inspiral, and where the binary plunges together to merge. It ranges from +1, meaning both black holes are spinning as fast as possible and rotate in the same direction as the orbital motion, to −1, both black holes spinning as fast as possible but in the opposite direction to the way that the binary is orbiting. A value of 0 for \chi_\mathrm{eff} could mean that the black holes are not spinning, that their rotation axes are in the orbital plane (instead of aligned with the orbital angular momentum), or that one black hole is aligned with the orbital motion and the other is antialigned, so that their effects cancel out.
  • The effective precession spin parameter \chi_\mathrm{p} qualifies the amount of precession, the way that the orbital plane and black hole spins wobble when they are not aligned. It is 0 for no precession, and 1 for maximal precession.

We can place some constraints on \chi_\mathrm{eff}, but can say nothing about \chi_\mathrm{p}. The inferred value of the effective inspiral spin parameter is -0.12^{+0.21}_{-0.30}. Therefore, we disfavour large spins aligned with the orbital angular momentum, but are consistent with small aligned spins, misaligned spins, or spins antialigned with the angular momentum. The value is similar to that for GW150914, which also had a near-zero, but slightly negative \chi_\mathrm{eff} of -0.06^{+0.14}_{-0.14}.

Effective inspiral and precession spin parameters

Estimated effective inspiral spin parameter \chi_\mathrm{eff} and effective precession spin \chi_\mathrm{p} parameter. The two-dimensional shows the probability distribution for GW170104 as well as 50% and 90% contours. The one-dimensional plot shows results using different waveform models, as well as the prior probability distribution. The dotted lines mark the edge of our 90% probability intervals. We learn basically nothing about precession. Part of Figure 3 of the GW170104 Discovery Paper.

Converting the information about \chi_\mathrm{eff}, the lack of information about \chi_\mathrm{p}, and our measurement of the ratio of the two black hole masses, into probability distributions for the component spins gives the plots below [bonus note]. We disfavour (but don’t exclude) spins aligned with the orbital angular momentum, but can’t say much else.

Orientation and magnitudes of the two spins

Estimated orientation and magnitude of the two component spins. The distribution for the more massive black hole is on the left, and for the smaller black hole on the right. The probability is binned into areas which have uniform prior probabilities, so if we had learnt nothing, the plot would be uniform. Part of Figure 3 of the GW170104 Discovery Paper.

One of the comments we had on a draft of the paper was that we weren’t making any definite statements about the spins—we would have if we could, but we can’t for GW170104, at least for the spins of the two inspiralling black holes. We can be more definite about the spin of the final black hole. If two similar mass black holes spiral together, the angular momentum from the orbit is enough to give a spin of around 0.7. The spins of the component black holes are less significant, and can make it a bit higher of lower. We infer a final spin of 0.64^{+0.09}_{-0.20}; there is a tail of lower spin values on account of the possibility that the two component black holes could be roughly antialigned with the orbital angular momentum.

Final black hole mass and spin

Estimated mass M_\mathrm{f} and spina_\mathrm{f} for the final black hole. The two-dimensional shows the probability distribution for GW170104 as well as 50% and 90% contours. The one-dimensional plot shows results using different waveform models. The dotted lines mark the edge of our 90% probability intervals. Figure 6 of the GW170104 Supplemental Material (Figure 11 of the arXiv version).

If you’re interested in parameter describing GW170104, make sure to check out the big table in the Supplemental Material. I am a fan of tables [bonus note].

Merger rates

Adding the first 11 days of coincident data from the second observing run (including the detection of GW170104) to the results from the first observing run, we find merger rates consistent with those from the first observing run.

To calculate the merger rates, we need to assume a distribution of black hole masses, and we use two simple models. One uses a power law distribution for the primary (larger) black hole and a uniform distribution for the mass ratio; the other uses a distribution uniform in the logarithm of the masses (both primary and secondary). The true distribution should lie somewhere between the two. The power law rate density has been updated from 31^{+42}_{-21}\mathrm{Gpc^{-3}\,yr^{-1}} to 32^{+33}_{-20}\mathrm{Gpc^{-3}\,yr^{-1}}, and the uniform in log rate density goes from 97^{+135}_{-67}~\mathrm{Gpc^{-3}\,yr^{-1}} to 103^{+110}_{-63}~\mathrm{Gpc^{-3}\,yr^{-1}}. The median values stay about the same, but the additional data have shrunk the uncertainties a little.

Astrophysics

The discoveries from the first observing run showed that binary black holes exist and merge. The question is now how exactly they form? There are several suggested channels, and it could be there is actually a mixture of different formation mechanisms in action. It will probably require a large number of detections before we can make confident statements about the the probable formation mechanisms; GW170104 is another step towards that goal.

There are two main predicted channels of binary formation:

  • Isolated binary evolution, where a binary star system lives its life together with both stars collapsing to black holes at the end. To get the black holes close enough to merge, it is usually assumed that the stars go through a common envelope phase, where one star puffs up so that the gravity of its companion can steal enough material that they lie in a shared envelope. The drag from orbiting inside this then shrinks the orbit.
  • Dynamical evolution where black holes form in dense clusters and a binary is created by dynamical interactions between black holes (or stars) which get close enough to each other.

It’s a little artificial to separate the two, as there’s not really such a thing as an isolated binary: most stars form in clusters, even if they’re not particularly large. There are a variety of different modifications to the two main channels, such as having a third companion which drives the inner binary to merge, embedding the binary is a dense disc (as found in galactic centres), or dynamically assembling primordial black holes (formed by density perturbations in the early universe) instead of black holes formed through stellar collapse.

All the channels can predict black holes around the masses of GW170104 (which is not surprising given that they are similar to the masses of GW150914).

The updated rates are broadly consistent with most channels too. The tightening of the uncertainty of the rates means that the lower bound is now a little higher. This means some of the channels are now in tension with the inferred rates. Some of the more exotic channels—requiring a third companion (Silsbee & Tremain 2017; Antonini, Toonen & Hamers 2017) or embedded in a dense disc (Bartos et al. 2016; Stone, Metzger & Haiman 2016; Antonini & Rasio 2016)—can’t explain the full rate, but I don’t think it was ever expected that they could, they are bonus formation mechanisms. However, some of the dynamical models are also now looking like they could predict a rate that is a bit low (Rodriguez et al. 2016; Mapelli 2016; Askar et al. 2017; Park et al. 2017). Assuming that this result holds, I think this may mean that some of the model parameters need tweaking (there are more optimistic predictions for the merger rates from clusters which are still perfectly consistent), that this channel doesn’t contribute all the merging binaries, or both.

The spins might help us understand formation mechanisms. Traditionally, it has been assumed that isolated binary evolution gives spins aligned with the orbital angular momentum. The progenitor stars were probably more or less aligned with the orbital angular momentum, and tides, mass transfer and drag from the common envelope would serve to realign spins if they became misaligned. Rodriguez et al. (2016) gives a great discussion of this. Dynamically formed binaries have no correlation between spin directions, and so we would expect an isotropic distribution of spins. Hence it sounds quite simple: misaligned spins indicates dynamical formation (although we can’t tell if the black holes are primordial or stellar), and aligned spins indicates isolated binary evolution. The difficulty is the traditional assumption for isolated binary evolution potentially ignores a number of effects which could be important. When a star collapses down to a black hole, there may be a supernova explosion. There is an explosion of matter and neutrinos and these can give the black hole a kick. The kick could change the orbital plane, and so misalign the spin. Even if the kick is not that big, if it is off-centre, it could torque the black hole, causing it to rotate and so misalign the spin that way. There is some evidence that this can happen with neutron stars, as one of the pulsars in the double pulsar system shows signs of this. There could also be some instability that changes the angular momentum during the collapse of the star, possibly with different layers rotating in different ways [bonus note]. The spin of the black hole would then depend on how many layers get swallowed. This is an area of research that needs to be investigated further, and I hope the prospect of gravitational wave measurements spurs this on.

For GW170104, we know the spins are not large and aligned with the orbital angular momentum. This might argue against one variation of isolated binary evolution, chemically homogeneous evolution, where the progenitor stars are tidally locked (and so rotate aligned with the orbital angular momentum and each other). Since the stars are rapidly spinning and aligned, you would expect the final black holes to be too, if the stars completely collapse down as is usually assumed. If the stars don’t completely collapse down though, it might still be possible that GW170104 fits with this model. Aside from this, GW170104 is consistent with all the other channels.

Effective inspiral spin parameters

Estimated effective inspiral spin parameter \chi_\mathrm{eff} for all events. To indicate how much (or little) we’ve learnt, the prior probability distribution for GW170104 is shown (the other priors are similar).All of the events have |\chi_\mathrm{eff}| < 0.35 at 90% probability. Figure 5 of the GW170104 Supplemental Material (Figure 10 of the arXiv version). This is one of my favourite plots [bonus note].

If we start looking at the population of events, we do start to notice something about the spins. All of the inferred values of \chi_\mathrm{eff} are close to zero. Only GW151226 is inconsistent with zero. These values could be explained if spins are typically misaligned (with the orbital angular momentum or each other) or if the spins are typically small (or both). We know that black holes spins can be large from observations of X-ray binaries, so it would be odd if they are small for binary black holes. Therefore, we have a tentative hint that spins are misaligned. We can’t say why the spins are misaligned, but it is intriguing. With more observations, we’ll be able to confirm if it is the case that spins are typically misaligned, and be able to start pinning down the distribution of spin magnitudes and orientations (as well as the mass distribution). It will probably take a while to be able to say anything definite though, as we’ll probably need about 100 detections.

Tests of general relativity

As well as giving us an insight into the properties of black holes, gravitational waves are the perfect tools for testing general relativity. If there are any corrections to general relativity, you’d expect them to be most noticeable under the most extreme conditions, where gravity is strong and spacetime is rapidly changing, exactly as in a binary black hole coalescence.

For GW170104 we repeated tests previously performed. Again, we found no evidence of deviations.

We added extra terms to to the waveform and constrained their potential magnitudes. The results are pretty much identical to at the end of the first observing run (consistent with zero and hence general relativity). GW170104 doesn’t add much extra information, as GW150914 typically gives the best constraints on terms that modify the post-inspiral part of the waveform (as it is louder), while GW151226 gives the best constraint on the terms which modify the inspiral (as it has the longest inspiral).

We also chopped the waveform at a frequency around that of the innermost stable orbit of the remnant black hole, which is about where the transition from inspiral to merger and ringdown occurs, to check if the low frequency and high frequency portions of the waveform give consistent estimates for the final mass and spin. They do.

We have also done something slightly new, and tested for dispersion of gravitational waves. We did something similar for GW150914 by putting a limit on the mass of the graviton. Giving the graviton mass is one way of adding dispersion, but we consider other possible forms too. In all cases, results are consistent with there being no dispersion. While we haven’t discovered anything new, we can update our gravitational wave constraint on the graviton mass of less than 7.7 \times 10^{-23}~\mathrm{eV}/c^2.

The search for counterparts

We don’t discuss observations made by our astronomer partners in the paper (they are not our results). A number (28 at the time of submission) of observations were made, and I expect that there will be a series of papers detailing these coming soon. So far papers have appeared from:

  • AGILE—hard X-ray and gamma-ray follow-up. They didn’t find any gamma-ray signals, but did identify a weak potential X-ray signal occurring about 0.46 s before GW170104. It’s a little odd to have a signal this long before the merger. The team calculate a probability for such a coincident to happen by chance, and find quite a small probability, so it might be interesting to follow this up more, but it’s probably just a coincidence (especially considering how many people did follow-up the event).
  • AstroSat-CZTI and GROWTH—a collaboration of observations across a range of wavelengths. They don’t find any hard X-ray counterparts. They do follow up on a bright optical transient ATLASaeu, suggested as a counterpart to GW170104, and conclude that this is a likely counterpart of long, soft gamma-ray burst GRB170105A.
  • ATLAS and Pan-STARRS—optical follow-up. They identified a bright optical transient 23 hours after GW170104, ATLAS17aeu. This could be a counterpart to GRB170105A. It seems unlikely that there is any mechanism that could allow for a day’s delay between the gravitational wave emission and an electromagnetic signal. However, the team calculate a small probability (few percent) of finding such a coincidence in sky position and time, so perhaps it is worth pondering. (I wouldn’t put any money on it though).
  • Fermi (GBM and LAT)—gamma-ray follow-up. They covered an impressive fraction of the sky localization, but didn’t find anything.
  • The intermediate Palomar Transient Factory—an optical survey. While searching, they discovered iPTF17cw, a broad-line type Ic supernova which is unrelated to GW170104 but interesting as it an unusual find.

If you are interested in what has been reported so far (no compelling counterpart candidates yet to my knowledge), there is an archive of GCN Circulars sent about GW170104.

Summary

Advanced LIGO has made its first detection of the second observing run. This is a further binary black hole coalescence. GW170104 has taught us that:

  • The discoveries of the first observing run were not a fluke. There really is a population of stellar mass black holes with masses above 25 M_\odot out there, and we can study them with gravitational waves.
  • Binary black hole spins may be typically misaligned or small. This is not certain yet, but it is certainly worth investigating potential mechanisms that could cause misalignment.
  • General relativity still works, even after considering our new tests.
  • If someone asks you to write a discovery paper, run. Run and do not look back.

Title: GW170104: Observation of a 50-solar-mass binary black hole coalescence at redshift 0.2
Journal:
 Physical Review Letters; 118(22):221101(17); 2017 (Supplemental Material)
arXiv: 1706.01812 [gr-qc]
Data release: LIGO Open Science Center
Science summary: 
 GW170104: Observation of a 50-solar-mass binary black hole coalescence at redshift 0.2

Bonus notes

Naming

Gravitational wave signals (at least the short ones, which are all that we have so far), are named by their detection date. GW170104 was discovered 2017 January 4. This isn’t too catchy, but is at least better than the ID number in our database of triggers (G268556) which is used in corresponding with our astronomer partners before we work out if the “GW” title is justified.

Previous detections have attracted nicknames, but none has stuck for GW170104. Archisman Ghosh suggested the Perihelion Event, as it was detected a few hours before the Earth reached its annual point closest to the Sun. I like this name, its rather poetic.

More recently, Alex Nitz realised that we should have called GW170104 the Enterprise-D Event, as the USS Enterprise’s registry number was NCC-1701. For those who like Star Trek: the Next Generation, I hope you have fun discussing whether GW170104 is the third or fourth (counting LVT151012) detection: “There are four detections!

The 6 January sky map

I would like to thank the wi-fi of Chiltern Railways for their role in producing the preliminary sky map. I had arranged to visit London for the weekend (because my rota slot was likely to be quiet… ), and was frantically working on the way down to check results so they could be sent out. I’d also like to thank John Veitch for putting together the final map while I was stuck on the Underground.

Binary black hole waveforms

The parameter estimation analysis works by matching a template waveform to the data to see how well it matches. The results are therefore sensitive to your waveform model, and whether they include all the relevant bits of physics.

In the first observing run, we always used two different families of waveforms, to see what impact potential errors in the waveforms could have. The results we presented in discovery papers used two quick-to-calculate waveforms. These include the effects of the black holes’ spins in different ways

  • SEOBNRv2 has spins either aligned or antialigned with the orbital angular momentum. Therefore, there is no precession (wobbling of orientation, like that of a spinning top) of the system.
  • IMRPhenomPv2 includes an approximate description of precession, packaging up the most important information about precession into a single parameter \chi_\mathrm{p}.

For GW150914, we also performed a follow-up analysis using a much more expensive waveform SEOBNRv3 which more fully includes the effect of both spins on precession. These results weren’t ready at the time of the announcement, because the waveform is laborious to run.

For GW170104, there were discussions that using a spin-aligned waveform was old hat, and that we should really only use the two precessing models. Hence, we started on the endeavour of producing SEOBNRv3 results. Fortunately, the code has been sped up a little, although it is still not quick to run. I am extremely grateful to Scott Coughlin (one of the folks behind Gravity Spy), Andrea Taracchini and Stas Babak for taking charge of producing results in time for the paper, in what was a Herculean effort.

I spent a few sleepless nights, trying to calculate if the analysis was converging quickly enough to make our target submission deadline, but it did work out in the end. Still, don’t necessarily expect we’ll do this for a all future detections.

Since the waveforms have rather scary technical names, in the paper we refer to IMRPhenomPv2 as the effective precession model and SEOBNRv3 as the full precession model.

On distance

Distance measurements for gravitational wave sources have significant uncertainties. The distance is difficult to measure as it determined from the signal amplitude, but this is also influences by the binary’s inclination. A signal could either be close and edge on or far and face on-face off.

Distance and inclination

Estimated luminosity distance D_\mathrm{L} and binary inclination angle \theta_{JN}. The two-dimensional shows the probability distribution for GW170104 as well as 50% and 90% contours. The one-dimensional plot shows results using different waveform models. The dotted lines mark the edge of our 90% probability intervals. Figure 4 of the GW170104 Supplemental Material (Figure 9 of the arXiv version).

The uncertainty on the distance rather awkwardly means that we can’t definitely say that GW170104 came from a further source than GW150914 or GW151226, but it’s a reasonable bet. The 90% credible intervals on the distances are 250–570 Mpc for GW150194, 250–660 Mpc for GW151226, 490–1330 Mpc for GW170104 and 500–1500 Mpc for LVT151012.

Translating from a luminosity distance to a travel time (gravitational waves do travel at the speed of light, our tests of dispersion are consistent wit that!), the GW170104 black holes merged somewhere between 1.3 and 3.0 billion years ago. This is around the time that multicellular life first evolved on Earth, and means that black holes have been colliding longer than life on Earth has been reproducing sexually.

Time line

A first draft of the paper (version 2; version 1 was a copy-and-paste of the Boxing Day Discovery Paper) was circulated to the Compact Binary Coalescence and Burst groups for comments on 4 March. This was still a rough version, and we wanted to check that we had a good outline of the paper. The main feedback was that we should include more about the astrophysical side of things. I think the final paper has a better balance, possibly erring on the side of going into too much detail on some of the more subtle points (but I think that’s better than glossing over them).

A first proper draft (version 3) was released to the entire Collaboration on 12 March in the middle of our Collaboration meeting in Pasadena. We gave an oral presentation the next day (I doubt many people had read the paper by then). Collaboration papers are usually allowed two weeks for people to comment, and we followed the same procedure here. That was not a fun time, as there was a constant trickle of comments. I remember waking up each morning and trying to guess how many emails would be in my inbox–I normally low-balled this.

I wasn’t too happy with version 3, it was still rather rough. The members of the Paper Writing Team had been furiously working on our individual tasks, but hadn’t had time to look at the whole. I was much happier with the next draft (version 4). It took some work to get this together, following up on all the comments and trying to address concerns was a challenge. It was especially difficult as we got a series of private comments, and trying to find a consensus probably made us look like the bad guys on all sides. We released version 4 on 14 April for a week of comments.

The next step was approval by the LIGO and Virgo executive bodies on 24 April. We prepared version 5 for this. By this point, I had lost track of which sentences I had written, which I had merely typed, and which were from other people completely. There were a few minor changes, mostly adding technical caveats to keep everyone happy (although they do rather complicate the flow of the text).

The paper was circulated to the Collaboration for a final week of comments on 26 April. Most comments now were about typos and presentation. However, some people will continue to make the same comment every time, regardless of how many times you explain why you are doing something different. The end was in sight!

The paper was submitted to Physical Review Letters on 9 May. I was hoping that the referees would take a while, but the reports were waiting in my inbox on Monday morning.

The referee reports weren’t too bad. Referee A had some general comments, Referee B had some good and detailed comments on the astrophysics, and Referee C gave the paper a thorough reading and had some good suggestions for clarifying the text. By this point, I have been staring at the paper so long that some outside perspective was welcome. I was hoping that we’d have a more thorough review of the testing general relativity results, but we had Bob Wald as one of our Collaboration Paper reviewers (the analysis, results and paper are all reviewed internally), so I think we had already been held to a high standard, and there wasn’t much left to say.

We put together responses to the reports. There were surprisingly few comments from the Collaboration at this point. I guess that everyone was getting tired. The paper was resubmitted and accepted on 20 May.

One of the suggestions of Referee A was to include some plots showing the results of the searches. People weren’t too keen on showing these initially, but after much badgering they were convinced, and it was decided to put these plots in the Supplemental Material which wouldn’t delay the paper as long as we got the material submitted by 26 May. This seemed like plenty of time, but it turned out to be rather frantic at the end (although not due to the new plots). The video below is an accurate representation of us trying to submit the final version.

I have an email which contains the line “Many Bothans died to bring us this information” from 1 hour and 18 minutes before the final deadline.

After this, things were looking pretty good. We had returned the proofs of the main paper (I had a fun evening double checking the author list. Yes, all of them). We were now on version 11 of the paper.

Of course, there’s always one last thing. On 31 May, the evening before publication, Salvo Vitale spotted a typo. Nothing serious, but annoying. The team at Physical Review Letters were fantastic, and took care of it immediately!

There’ll still be one more typo, there always is…

Looking back, it is clear that the principal bottle-neck in publishing the results is getting the Collaboration to converge on the paper. I’m not sure how we can overcome this… Actually, I have some ideas, but none that wouldn’t involve some form of doomsday device.

Detector status

The sensitivities of the LIGO Hanford and Livinston detectors are around the same as they were in the first observing run. After the success of the first observing run, the second observing run is the difficult follow up album. Livingston has got a little better, while Hanford is a little worse. This is because the Livingston team concentrate on improving low frequency sensitivity whereas the Hanford team focused on improving high frequency sensitivity. The Hanford team increased the laser power, but this introduces some new complications. The instruments are extremely complicated machines, and improving sensitivity is hard work.

The current plan is to have a long commissioning break after the end of this run. The low frequency tweaks from Livingston will be transferred to Hanford, and both sites will work on bringing down other sources of noise.

While the sensitivity hasn’t improved as much as we might have hoped, the calibration of the detectors has! In the first observing run, the calibration uncertainty for the first set of published results was about 10% in amplitude and 10 degrees in phase. Now, uncertainty is better than 5% in amplitude and 3 degrees in phase, and people are discussing getting this down further.

Spin evolution

As the binary inspirals, the orientation of the spins will evolve as they precess about. We always quote measurements of the spins at a point in the inspiral corresponding to a gravitational wave frequency of 20 Hz. This is most convenient for our analysis, but you can calculate the spins at other points. However, the resulting probability distributions are pretty similar at other frequencies. This is because the probability distributions are primarily determined by the combination of three things: (i) our prior assumption of a uniform distribution of spin orientations, (ii) our measurement of the effective inspiral spin, and (iii) our measurement of the mass ratio. A uniform distribution stays uniform as spins evolve, so this is unaffected, the effective inspiral spin is approximately conserved during inspiral, so this doesn’t change much, and the mass ratio is constant. The overall picture is therefore qualitatively similar at different moments during the inspiral.

Footnotes

I love footnotes. It was challenging for me to resist having any in the paper.

Gravity waves

It is possible that internal gravity waves (that is oscillations of the material making up the star, where the restoring force is gravity, not gravitational waves, which are ripples in spacetime), can transport angular momentum from the core of a star to its outer envelope, meaning that the two could rotate in different directions (Rogers, Lin & Lau 2012). I don’t think anyone has studied this yet for the progenitors of binary black holes, but it would be really cool if gravity waves set the properties of gravitational wave sources.

I really don’t want to proof read the paper which explains this though.

Colour scheme

For our plots, we use a consistent colour coding for our events. GW150914 is blue; LVT151012 is green; GW151226 is red–orange, and GW170104 is purple. The colour scheme is designed to be colour blind friendly (although adopting different line styles would perhaps be more distinguishable), and is implemented in Python in the Seaborn package as colorblind. Katerina Chatziioannou, who made most of the plots showing parameter estimation results is not a fan of the colour combinations, but put a lot of patient effort into polishing up the plots anyway.

GW150914—The papers II

GW150914, The Event to its friends, was our first direct observation of gravitational waves. To accompany the detection announcement, the LIGO Scientific & Virgo Collaboration put together a suite of companion papers, each looking at a different aspect of the detection and its implications. Some of the work we wanted to do was not finished at the time of the announcement; in this post I’ll go through the papers we have produced since the announcement.

The papers

I’ve listed the papers below in an order that makes sense to me when considering them together. Each started off as an investigation to check that we really understood the signal and were confident that the inferences made about the source were correct. We had preliminary results for each at the time of the announcement. Since then, the papers have evolved to fill different niches [bonus points note].

13. The Basic Physics Paper

Title: The basic physics of the binary black hole merger GW150914
arXiv:
 1608.01940 [gr-qc]
Journal:
 Annalen der Physik529(1–2):1600209(17); 2017

The Event was loud enough to spot by eye after some simple filtering (provided that you knew where to look). You can therefore figure out some things about the source with back-of-the-envelope calculations. In particular, you can convince yourself that the source must be two black holes. This paper explains these calculations at a level suitable for a keen high-school or undergraduate physics student.

More details: The Basic Physics Paper summary

14. The Precession Paper

Title: Improved analysis of GW150914 using a fully spin-precessing waveform model
arXiv:
 1606.01210 [gr-qc]
Journal:
 Physical Review X; 6(4):041014(19); 2016

To properly measure the properties of GW150914’s source, you need to compare the data to predicted gravitational-wave signals. In the Parameter Estimation Paper, we did this using two different waveform models. These models include lots of features binary black hole mergers, but not quite everything. In particular, they don’t include all the effects of precession (the wibbling of the orbit because of the black holes spins). In this paper, we analyse the signal using a model that includes all the precession effects. We find results which are consistent with our initial ones.

More details: The Precession Paper summary

15. The Systematics Paper

Title: Effects of waveform model systematics on the interpretation of GW150914
arXiv:
 1611.07531 [gr-qc]
Journal: 
Classical & Quantum Gravity; 34(10):104002(48); 2017

To check how well our waveform models can measure the properties of the source, we repeat the parameter-estimation analysis on some synthetic signals. These fake signals are calculated using numerical relativity, and so should include all the relevant pieces of physics (even those missing from our models). This paper checks to see if there are any systematic errors in results for a signal like GW150914. It looks like we’re OK, but this won’t always be the case.

More details: The Systematics Paper summary

16. The Numerical Relativity Comparison Paper

Title: Directly comparing GW150914 with numerical solutions of Einstein’s equations for binary black hole coalescence
arXiv:
 1606.01262 [gr-qc]
Journal:
 Physical Review D; 94(6):064035(30); 2016

Since GW150914 was so short, we can actually compare the data directly to waveforms calculated using numerical relativity. We only have a handful of numerical relativity simulations, but these are enough to give an estimate of the properties of the source. This paper reports the results of this investigation. Unsurprisingly, given all the other checks we’ve done, we find that the results are consistent with our earlier analysis.

If you’re interested in numerical relativity, this paper also gives a nice brief introduction to the field.

More details: The Numerical Relativity Comparison Paper summary

The Basic Physics Paper

Synopsis: Basic Physics Paper
Read this if: You are teaching a class on gravitational waves
Favourite part: This is published in Annalen der Physik, the same journal that Einstein published some of his monumental work on both special and general relativity

It’s fun to play with LIGO data. The LIGO Open Science Center (LOSC), has put together a selection of tutorials to show you some of the basics of analysing signals. I wouldn’t blame you if you went of to try them now, instead of reading the rest of this post. Even though it would mean that no-one read this sentence. Purple monkey dishwasher.

The LOSC tutorials show you how to make your own version of some of the famous plots from the detection announcement. This paper explains how to go from these, using the minimum of theory, to some inferences about the signal’s source: most significantly that it must be the merger of two black holes.

GW150914 is a chirp. It sweeps up from low frequency to high. This is what you would expect of a binary system emitting gravitational waves. The gravitational waves carry away energy and angular momentum, causing the binary’s orbit to shrink. This means that the orbital period gets shorter, and the orbital frequency higher. The gravitational wave frequency is twice the orbital frequency (for circular orbits), so this goes up too.

The rate of change of the frequency depends upon the system’s mass. To first approximation, it is determined by the chirp mass,

\displaystyle \mathcal{M} = \frac{(m_1 m_2)^{3/5}}{(m_1 + m_2)^{1/5}},

where m_1 and m_2 are the masses of the two components of the binary. By looking at the signal (go on, try the LOSC tutorials), we can estimate the gravitational wave frequency f_\mathrm{GW} at different times, and so track how it changes. You can rewrite the equation for the rate of change of the gravitational wave frequency \dot{f}_\mathrm{GW}, to give an expression for the chirp mass

\displaystyle \mathcal{M} = \frac{c^3}{G}\left(\frac{5}{96} \pi^{-8/3} f_\mathrm{GW}^{-11/3} \dot{f}_\mathrm{GW}\right)^{3/5}.

Here c and G are the speed of light and the gravitational constant, which usually pop up in general relativity equations. If you use this formula (perhaps fitting for the trend f_\mathrm{GW}) you can get an estimate for the chirp mass. By fiddling with your fit, you’ll see there is some uncertainty, but you should end up with a value around 30 M_\odot [bonus note].

Next, let’s look at the peak gravitational wave frequency (where the signal is loudest). This should be when the binary finally merges. The peak is at about 150~\mathrm{Hz}. The orbital frequency is half this, so f_\mathrm{orb} \approx 75~\mathrm{Hz}. The orbital separation R is related to the frequency by

\displaystyle R = \left[\frac{GM}{(2\pi f_\mathrm{orb})^2}\right]^{1/3},

where M = m_1 + m_2 is the binary’s total mass. This formula is only strictly true in Newtonian gravity, and not in full general relativity, but it’s still a reasonable approximation. We can estimate a value for the total mass from our chirp mass; if we assume the two components are about the same mass, then M = 2^{6/5} \mathcal{M} \approx 70 M_\odot. We now want to compare the binary’s separation to the size of black hole with the same mass. A typical size for a black hole is given by the Schwarzschild radius

\displaystyle R_\mathrm{S} = \frac{2GM}{c^2}.

If we divide the binary separation by the Schwarzschild radius we get the compactness \mathcal{R} = R/R_\mathrm{S} \approx 1.7. A compactness of \sim 1 could only happen for black holes. We could maybe get a binary made of two neutron stars to have a compactness of \sim2, but the system is too heavy to contain two neutron stars (which have a maximum mass of about 3 M_\odot). The system is so compact, it must contain black holes!

What I especially like about the compactness is that it is unaffected by cosmological redshifting. The expansion of the Universe will stretch the gravitational wave, such that the frequency gets lower. This impacts our estimates for the true orbital frequency and the masses, but these cancel out in the compactness. There’s no arguing that we have a highly relativistic system.

You might now be wondering what if we don’t assume the binary is equal mass (you’ll find it becomes even more compact), or if we factor in black hole spin, or orbital eccentricity, or that the binary will lose mass as the gravitational waves carry away energy? The paper looks at these and shows that there is some wiggle room, but the signal really constrains you to have black holes. This conclusion is almost as inescapable as a black hole itself.

There are a few things which annoy me about this paper—I think it could have been more polished; “Virgo” is improperly capitalised on the author line, and some of the figures are needlessly shabby. However, I think it is a fantastic idea to put together an introductory paper like this which can be used to show students how you can deduce some properties of GW150914’s source with some simple data analysis. I’m happy to be part of a Collaboration that values communicating our science to all levels of expertise, not just writing papers for specialists!

During my undergraduate degree, there was only a single lecture on gravitational waves [bonus note]. I expect the topic will become more popular now. If you’re putting together such a course and are looking for some simple exercises, this paper might come in handy! Or if you’re a student looking for some project work this might be a good starting reference—bonus points if you put together some better looking graphs for your write-up.

If this paper has whetted your appetite for understanding how different properties of the source system leave an imprint in the gravitational wave signal, I’d recommend looking at the Parameter Estimation Paper for more.

The Precession Paper

Synopsis: Precession Paper
Read this if: You want our most detailed analysis of the spins of GW150914’s black holes
Favourite part: We might have previously over-estimated our systematic error

The Basic Physics Paper explained how you could work out some properties of GW150914’s source with simple calculations. These calculations are rather rough, and lead to estimates with large uncertainties. To do things properly, you need templates for the gravitational wave signal. This is what we did in the Parameter Estimation Paper.

In our original analysis, we used two different waveforms:

  • The first we referred to as EOBNR, short for the lengthy technical name SEOBNRv2_ROM_DoubleSpin. In short: This includes the spins of the two black holes, but assumes they are aligned such that there’s no precession. In detail: The waveform is calculated by using effective-one-body dynamics (EOB), an approximation for the binary’s motion calculated by transforming the relevant equations into those for a single object. The S at the start stands for spin: the waveform includes the effects of both black holes having spins which are aligned (or antialigned) with the orbital angular momentum. Since the spins are aligned, there’s no precession. The EOB waveforms are tweaked (or calibrated, if you prefer) by comparing them to numerical relativity (NR) waveforms, in particular to get the merger and ringdown portions of the waveform right. While it is easier to solve the EOB equations than full NR simulations, they still take a while. To speed things up, we use a reduced-order model (ROM), a surrogate model constructed to match the waveforms, so we can go straight from system parameters to the waveform, skipping calculating the dynamics of the binary.
  • The second we refer to as IMRPhenom, short for the technical IMRPhenomPv2. In short: This waveform includes the effects of precession using a simple approximation that captures the most important effects. In detail: The IMR stands for inspiral–merger–ringdown, the three phases of the waveform (which are included in in the EOBNR model too). Phenom is short for phenomenological: the waveform model is constructed by tuning some (arbitrary, but cunningly chosen) functions to match waveforms calculated using a mix of EOB, NR and post-Newtonian theory. This is done for black holes with (anti)aligned spins to first produce the IMRPhenomD model. This is then twisted up, to include the dominant effects of precession to make IMRPhenomPv2. This bit is done by combining the two spins together to create a single parameter, which we call \chi_\mathrm{p}, which determines the amount of precession. Since we are combining the two spins into one number, we lose a bit of the richness of the full dynamics, but we get the main part.

The EOBNR and IMRPhenom models are created by different groups using different methods, so they are useful checks of each other. If there is an error in our waveforms, it would lead to systematic errors in our estimated paramters

In this paper, we use another waveform model, a precessing EOBNR waveform, technically known as SEOBNRv3. This model includes all the effects of precession, not just the simple model of the IMRPhenom model. However, it is also computationally expensive, meaning that the analysis takes a long time (we don’t have a ROM to speed things up, as we do for the other EOBNR waveform)—each waveform takes over 20 times as long to calculate as the IMRPhenom model [bonus note].

Our results show that all three waveforms give similar results. The precessing EOBNR results are generally more like the IMRPhenom results than the non-precessing EOBNR results are. The plot below compares results from the different waveforms [bonus note].

Comparison of results from non-precessing EOBNR, precessing IMRPhenom and precessing EOBNR waveforms

Comparison of parameter estimates for GW150914 using different waveform models. The bars show the 90% credible intervals, the dark bars show the uncertainty on the 5%, 50% and 95% quantiles from the finite number of posterior samples. The top bar is for the non-precessing EOBNR model, the middle is for the precessing IMRPhenom model, and the bottom is for the fully precessing EOBNR model. Figure 1 of the Precession Paper; see Figure 9 for a comparison of averaged EOBNR and IMRPhenom results, which we have used for our overall results.

We had used the difference between the EOBNR and IMRPhenom results to estimate potential systematic error from waveform modelling. Since the two precessing models are generally in better agreement, we have may have been too pessimistic here.

The main difference in results is that our new refined analysis gives tighter constraints on the spins. From the plot above you can see that the uncertainty for the spin magnitudes of the heavier black hole a_1, the lighter black hole a_2 and the final black hole (resulting from the coalescence) a_\mathrm{f}, are slightly narrower. This makes sense, as including the extra imprint from the full effects of precession gives us a bit more information about the spins. The plots below show the constraints on the spins from the two precessing waveforms: the distributions are more condensed with the new results.

Black hole spins estimated using precessing IMRPhenom and EOBNR waveforms

Comparison of orientations and magnitudes of the two component spins. The spin is perfectly aligned with the orbital angular momentum if the angle is 0. The left disk shows results using the precessing IMRPhenom model, the right using the precessing EOBNR model. In each, the distribution for the more massive black hole is on the left, and for the smaller black hole on the right. Adapted from Figure 5 of the Parameter Estimation Paper and Figure 4 of the Precession Paper.

In conclusion, this analysis had shown that included the full effects of precession do give slightly better estimates of the black hole spins. However, it is safe to trust the IMRPhenom results.

If you are looking for the best parameter estimates for GW150914, these results are better than the original results in the Parameter Estimation Paper. However, I would prefer the results in the O1 Binary Black Hole Paper, even though this doesn’t use the fully precessing EOBNR waveform, because we do use an updated calibration of the detector data. Neither the choice of waveform or the calibration make much of an impact on the results, so for most uses it shouldn’t matter too much.

The Systematics Paper

Synopsis: Systematics Paper
Read this if: You want to know how parameter estimation could fare for future detections
Favourite part: There’s no need to panic yet

The Precession Paper highlighted how important it is to have good waveform templates. If there is an error in our templates, either because of modelling or because we are missing some physics, then our estimated parameters could be wrong—we would have a source of systematic error.

We know our waveform models aren’t perfect, so there must be some systematic error, the question is how much? From our analysis so far (such as the good agreement between different waveforms in the Precession Paper), we think that systematic error is less significant than the statistical uncertainty which is a consequence of noise in the detectors. In this paper, we try to quantify systematic error for GW150914-like systems.

To asses systematic errors, we analyse waveforms calculated by numerical relativity simulations into data around the time of GW150914. Numerical relativity exactly solves Einstein’s field equations (which govern general relativity), so results of these simulations give the most accurate predictions for the form of gravitational waves. As we know the true parameters for the injected waveforms, we can compare these to the results of our parameter estimation analysis to check for biases.

We use waveforms computed by two different codes: the Spectral Einstein Code (SpEC) and the Bifunctional Adaptive Mesh (BAM) code. (Don’t the names make them sound like such fun?) Most waveforms are injected into noise-free data, so that we know that any offset in estimated parameters is dues to the waveforms and not detector noise; however, we also tried a few injections into real data from around the time of GW150914. The signals are analysed using our standard set-up as used in the Parameter Estimation Paper (a couple of injections are also included in the Precession Paper, where they are analysed with the fully precessing EOBNR waveform to illustrate its accuracy).

The results show that in most cases, systematic errors from our waveform models are small. However, systematic errors can be significant for some orientations of precessing binaries. If we are looking at the orbital plane edge on, then there can be errors in the distance, the mass ratio and the spins, as illustrated below [bonus note]. Thankfully, edge-on binaries are quieter than face-on binaries, and so should make up only a small fraction of detected sources (GW150914 is most probably face off). Furthermore, biases are only significant for some polarization angles (an angle which describes the orientation of the detectors relative to the stretch/squash of the gravitational wave polarizations). Factoring this in, a rough estimate is that about 0.3% of detected signals would fall into the unlucky region where waveform biases are important.

Inclination dependence of parameter recovery

Parameter estimation results for two different GW150914-like numerical relativity waveforms for different inclinations and polarization angles. An inclination of 0^\circ means the binary is face on, 180^\circ means it face off, and an inclination around 90^\circ is edge on. The bands show the recovered 90% credible interval; the dark lines the median values, and the dotted lines show the true values. The (grey) polarization angle \psi = 82^\circ was chosen so that the detectors are approximately insensitive to the h_+ polarization. Figure 4 of the Systematics Paper.

While it seems that we don’t have to worry about waveform error for GW150914, this doesn’t mean we can relax. Other systems may show up different aspects of waveform models. For example, our approximants only include the dominant modes (spherical harmonic decompositions of the gravitational waves). Higher-order modes have more of an impact in systems where the two black holes are unequal masses, or where the binary has a higher total mass, so that the merger and ringdown parts of the waveform are more important. We need to continue work on developing improved waveform models (or at least, including our uncertainty about them in our analysis), and remember to check for biases in our results!

The Numerical Relativity Comparison Paper

Synopsis: Numerical Relativity Comparison Paper
Read this if: You are really suspicious of our waveform models, or really like long tables or numerical data
Favourite part: We might one day have enough numerical relativity waveforms to do full parameter estimation with them

In the Precession Paper we discussed how important it was to have accurate waveforms; in the Systematics Paper we analysed numerical relativity waveforms to check the accuracy of our results. Since we do have numerical relativity waveforms, you might be wondering why we don’t just use these in our analysis? In this paper, we give it a go.

Our standard parameter-estimation code (LALInference) randomly hops around parameter space, for each set of parameters we generate a new waveform and see how this matches the data. This is an efficient way of exploring the parameter space. Numerical relativity waveforms are too computationally expensive to generate one each time we hop. We need a different approach.

The alternative, is to use existing waveforms, and see how each of them match. Each simulation gives the gravitational waves for a particular mass ratio and combination of spins, we can scale the waves to examine different total masses, and it is easy to consider what the waves would look like if measured at a different position (distance, inclination or sky location). Therefore, we can actually cover a fair range of possible parameters with a given set of simulations.

To keep things quick, the code averages over positions, this means we don’t currently get an estimate on the redshift, and so all the masses are given as measured in the detector frame and not as the intrinsic masses of the source.

The number of numerical relativity simulations is still quite sparse, so to get nice credible regions, a simple Gaussian fit is used for the likelihood. I’m not convinced that this capture all the detail of the true likelihood, but it should suffice for a broad estimate of the width of the distributions.

The results of this analysis generally agree with those from our standard analysis. This is a relief, but not surprising given all the other checks that we have done! It hints that we might be able to get slightly better measurements of the spins and mass ratios if we used more accurate waveforms in our standard analysis, but the overall conclusions are  sound.

I’ve been asked if since these results use numerical relativity waveforms, they are the best to use? My answer is no. As well as potential error from the sparse sampling of simulations, there are several small things to be wary of.

  • We only have short numerical relativity waveforms. This means that the analysis only goes down to a frequency of 30~\mathrm{Hz} and ignores earlier cycles. The standard analysis includes data down to 20~\mathrm{Hz}, and this extra data does give you a little information about precession. (The limit of the simulation length also means you shouldn’t expect this type of analysis for the longer LVT151012 or GW151226 any time soon).
  • This analysis doesn’t include the effects of calibration uncertainty. There is some uncertainty in how to convert from the measured signal at the detectors’ output to the physical strain of the gravitational wave. Our standard analysis fold this in, but that isn’t done here. The estimates of the spin can be affected by miscalibration. (This paper also uses the earlier calibration, rather than the improved calibration of the O1 Binary Black Hole Paper).
  • Despite numerical relativity simulations producing waveforms which include all higher modes, not all of them are actually used in the analysis. More are included than in the standard analysis, so this will probably make negligible difference.

Finally, I wanted to mention one more detail, as I think it is not widely appreciated. The gravitational wave likelihood is given by an inner product

\displaystyle L \propto \exp \left[- \int_{-\infty}^{\infty}  \mathrm{d}f  \frac{|s(f) - h(f)|^2}{S_n(f)}  \right],

where s(f) is the signal, h(f) is our waveform template and S_n(f) is the noise spectral density (PSD). These are the three things we need to know to get the right answer. This paper, together with the Precession Paper and the Systematics Paper, has been looking at error from our waveform models h(f). Uncertainty from the calibration of s(f) is included in the standard analysis, so we know how to factor this in (and people are currently working on more sophisticated models for calibration error). This leaves the noise PSD S_n(f)

The noise PSD varies all the time, so it needs to be estimated from the data. If you use a different stretch of data, you’ll get a different estimate, and this will impact your results. Ideally, you would want to estimate from the time span that includes the signal itself, but that’s tricky as there’s a signal in the way. The analysis in this paper calculates the noise power spectral density using a different time span and a different method than our standard analysis; therefore, we expect some small difference in the estimated parameters. This might be comparable to (or even bigger than) the difference from switching waveforms! We see from the similarity of results that this cannot be a big effect, but it means that you shouldn’t obsess over small differences, thinking that they could be due to waveform differences, when they could just come from estimation of the noise PSD.

Lots of work is currently going into making sure that the numerator term |s(f) - h(f)|^2 is accurate. I think that the denominator S_n(f) needs attention too. Since we have been kept rather busy, including uncertainty in PSD estimation will have to wait for a future set papers.

Bonus notes

Finches

100 bonus points to anyone who folds up the papers to make beaks suitable for eating different foods.

The right answer

Our current best estimate for the chirp mass (from the O1 Binary Black Hole Paper) would be 30.6^{+1.9}_{-1.6} M_\odot. You need proper templates for the gravitational wave signal to calculate this. If you factor in the the gravitational wave gets redshifted (shifted to lower frequency by the expansion of the Universe), then the true chirp mass of the source system is 28.1^{+1.8}_{-1.5} M_\odot.

Formative experiences

My one undergraduate lecture on gravitational waves was the penultimate lecture of the fourth-year general relativity course. I missed this lecture, as I had a PhD interview (at the University of Birmingham). Perhaps if I had sat through it, my research career would have been different?

Good things come…

The computational expense of a waveform is important, as when we are doing parameter estimation, we calculate lots (tens of millions) of waveforms for different parameters to see how they match the data. Before O1, the task of using SEOBNRv3 for parameter estimation seemed quixotic. The first detection, however, was enticing enough to give it a try. It was a truly heroic effort by Vivien Raymond and team that produced these results—I am slightly suspicious the Vivien might actually be a wizard.

GW150914 is a short signal, meaning it is relatively quick to analyse. Still, it required us using all the tricks at our disposal to get results in a reasonable time. When it came time to submit final results for the Discovery Paper, we had just about 1,000 samples from the posterior probability distribution for the precessing EOBNR waveform. For comparison, we had over 45,000 sample for the non-precessing EOBNR waveform. 1,000 samples isn’t enough to accurately map out the probability distributions, so we decided to wait and collect more samples. The preliminary results showed that things looked similar, so there wouldn’t be a big difference in the science we could do. For the Precession Paper, we finally collected 2,700 samples. This is still a relatively small number, so we carefully checked the uncertainty in our results due to the finite number of samples.

The Precession Paper has shown that it is possible to use the precessing EOBNR for parameter estimation, but don’t expect it to become the norm, at least until we have a faster implementation of it. Vivien is only human, and I’m sure his family would like to see him occasionally.

Parameter key

In case you are wondering what all the symbols in the results plots stand for, here are their usual definitions. First up, the various masses

  • m_1—the mass of the heavier black hole, sometimes called the primary black hole;
  • m_2—the mass of the lighter black hole, sometimes called the secondary black hole;
  • M—the total mass of the binary, M = m_1 + m_2;
  • M_\mathrm{f}—the mass of the final black hole (after merger);
  • \mathcal{M}—the chirp mass, the combination of the two component masses which sets how the binary inspirals together;
  • q—the mass ratio, q = m_1/m_2 \leq 1. Confusingly, numerical relativists often use the opposite  convention q = m_2/m_1 \geq 1 (which is why the Numerical Relativity Comparison Paper discusses results in terms of 1/q: we can keep the standard definition, but all the numbers are numerical relativist friendly).

A superscript “source” is sometimes used to distinguish the actual physical masses of the source from those measured by the detector which have been affected by cosmological redshift. The measured detector-frame mass is m = (1 + z) m^\mathrm{source}, where m^\mathrm{source} is the true, redshift-corrected source-frame mass and z is the redshift. The mass ratio q is independent of the redshift. On the topic of redshift, we have

  • z—the cosmological redshift (z = 0 would be now);
  • D_\mathrm{L}—the luminosity distance.

The luminosity distance sets the amplitude of the signal, as does the orientation which we often describe using

  • \iota—the inclination, the angle between the line of sight and the orbital angular momentum (\boldsymbol{L}). This is zero for a face-on binary.
  • \theta_{JN}—the angle between the line of sight (\boldsymbol{N}) and the total angular momentum of the binary (\boldsymbol{J}); this is approximately equal to the inclination, but is easier to use for precessing binaries.

As well as masses, black holes have spins

  • a_1—the (dimensionless) spin magnitude of the heavier black hole, which is between 0 (no spin) and 1 (maximum spin);
  • a_2—the (dimensionless) spin magnitude of the lighter black hole;
  • a_\mathrm{f}—the (dimensionless) spin magnitude of the final black hole;
  • \chi_\mathrm{eff}—the effective inspiral spin parameter, a combinations of the two component spins which has the largest impact on the rate of inspiral (think of it as the spin equivalent of the chirp mass);
  • \chi_\mathrm{p}—the effective precession spin parameter, a combination of spins which indicate the dominant effects of precession, it’s 0 for no precession and 1 for maximal precession;
  • \theta_{LS_1}—the primary tilt angle, the angle between the orbital angular momentum and the heavier black holes spin (\boldsymbol{S_1}). This is zero for aligned spin.
  • \theta_{LS_2}—the secondary tilt angle, the angle between the orbital angular momentum and the lighter black holes spin (\boldsymbol{S_2}).
  • \phi_{12}—the angle between the projections of the two spins on the orbital plane.

The orientation angles change in precessing binaries (when the spins are not perfectly aligned or antialigned with the orbital angular momentum), so we quote values at a reference time corresponding to when the gravitational wave frequency is 20~\mathrm{Hz}. Finally (for the plots shown here)

  • \psi—the polarization angle, this is zero when the detector arms are parallel to the h_+ polarization’s stretch/squash axis.

For more detailed definitions, check out the Parameter Estimation Paper or the LALInference Paper.

The Boxing Day Event

Advanced LIGO’s first observing run (O1) got off to an auspicious start with the detection of GW150914 (The Event to its friends). O1 was originally planned to be three months long (September to December), but after the first discovery, there were discussions about extending the run. No major upgrades to the detectors were going to be done over the holidays anyway, so it was decided that we might as well leave them running until January.

By the time the Christmas holidays came around, I was looking forward to some time off. And, of course, lots of good food and the Doctor Who Christmas Special. The work on the first detection had been exhausting, and the Collaboration reached the collective decision that we should all take some time off [bonus note]. Not a creature was stirring, not even a mouse.

On Boxing Day, there was a sudden flurry of emails. This could only mean one thing. We had another detection! Merry GW151226 [bonus note]!

A Christmas gift

I assume someone left out milk and cookies at the observatories. A not too subtle hint from Nutsinee Kijbunchoo’s comic in the LIGO Magazine.

I will always be amazed how lucky we were detecting GW150914. This could have been easily missed if we were just a little later starting observing. If that had happened, we might not have considered extended O1, and would have missed GW151226 too!

GW151226 is another signal from a binary black hole coalescence. This wasn’t too surprising at the time, as we had estimated such signals should be pretty common. It did, however, cause a slight wrinkle in discussions of what to do in the papers about the discovery of GW150914. Should we mention that we had another potential candidate? Should we wait until we had analysed the whole of O1 fully? Should we pack it all in and have another slice of cake? In the end we decided that we shouldn’t delay the first announcement, and we definitely shouldn’t rush the analysis of the full data set. Therefore, we went ahead with the original plan of just writing about the first month of observations and giving slightly awkward answers, mumbling about still having data to analyse, when asked if we had seen anything else [bonus note]. I’m not sure how many people outside the Collaboration suspected.

The science

What have we learnt from analysing GW151226, and what have we learnt from the whole of O1? We’ve split our results into two papers.

0. The Boxing Day Discovery Paper

Title: GW151226: Observation of gravitational waves from a 22-solar-mass binary black hole
arXiv: 1606.04855 [gr-qc]
Journal: Physical Review Letters116(24):241103(14)
LIGO science summary: GW151226: Observation of gravitational waves from a 22 solar-mass binary black hole (by Hannah Middleton and Carl-Johan Haster)

This paper presents the discovery of GW151226 and some of the key information about it. GW151226 is not as loud as GW150914, you can’t spot it by eye in the data, but it still stands out in our search. This is a clear detection! It is another binary black hole system, but it is a lower mass system than GW150914 (hence the paper’s title—it’s a shame they couldn’t put in the error bars though).

This paper summarises the highlights of the discovery, so below, I’ll explain these without going into too much technical detail.

More details: The Boxing Day Discovery Paper summary

1. The O1 Binary Black Hole Paper

Title: Binary black hole mergers in the first Advanced LIGO observing run
arXiv: 1606.04856 [gr-qc]
Journal: Physical Review X6(4):041015(36)

This paper brings together (almost) everything we’ve learnt about binary black holes from O1. It discusses GW150915, LVT151012 and GW151226, and what we are starting to piece together about stellar-mass binary black holes from this small family of gravitational-wave events.

For the announcement of GW150914, we put together 12 companion papers to go out with the detection announcement. This paper takes on that role. It is Robin, Dr Watson, Hermione and Samwise Gamgee combined. There’s a lot of delicious science packed into this paper (searches, parameter estimation, tests of general relativity, merger rate estimation, and astrophysical implications). In my summary below, I’ll delve into what we have done and what our results mean.

More details: The O1 Binary Black Hole Paper summary

If you are interested in our science results, you can find data releases accompanying the events at the LIGO Open Science Center. These pages also include some wonderful tutorials to play with.

The Boxing Day Discovery Paper

Synopsis: Boxing Day Discovery Paper
Read this if: You are excited about the discovery of GW151226
Favourite part: We’ve done it again!

The signal

GW151226 is not as loud as GW150914, you can’t spot it by eye in the data. Therefore, this paper spends a little more time than GW150914’s Discovery Paper talking about the ingredients for our searches.

GW151226 was found by two pipelines which specifically look for compact binary coalescences: the inspiral and merger of neutron stars or black holes. We have templates for what we think these signals should look like, and we filter the data against a large bank of these to see what matches [bonus note].

For the search to work, we do need accurate templates. Figuring out what the waveforms for binary black coalescence should look like is a difficult job, and has taken almost as long as figuring out how to build the detectors!

The signal arrived at Earth 03:38:53 GMT on 26 December 2015 and was first identified by a search pipeline within 70 seconds. We didn’t have a rapid templated search online at the time of GW150914, but decided it would be a good idea afterwards. This allowed us to send out an alert to our astronomer partners so they could look for any counterparts (I don’t think any have been found [bonus note]).

The unmodelled searches (those which don’t use templates, but just coherent signals in both detectors) which first found GW150914 didn’t find GW151226. This isn’t too surprising, as they are less sensitive. You can think of the templated searches as looking for Wally (or Waldo if you’re North American), using the knowledge that he’s wearing glasses, and a red and white stripped bobble hat, but the unmodelled searches are looking for him just knowing that he’s the person that’s on on every page.

GW151226 is the second most significant event in the search for binary black holes after The Event. Its significance is not quite off the charts, but is great enough that we have a hard time calculating exactly how significant it is. Our two search pipelines give estimates of the p-value (the probability you’d see something at least this signal-like if you only had noise in your detectors) of < 10^{-7} and 3.5 \times 10^{-6}, which are pretty good!

The source

To figure out the properties of the source, we ran our parameter-estimation analysis.

GW151226 comes from a black hole binary with masses of 14.2^{+8.3}_{-3.7} M_\odot and 7.5^{+2.3}_{-2.3} M_\odot [bonus note], where M_\odot is the mass of our Sun (about 330,000 times the mass of the Earth). The error bars indicate our 90% probability ranges on the parameters. These black holes are less massive than the source of GW150914 (the more massive black hole is similar to the less massive black hole of LVT151012). However, the masses are still above what we believe is the maximum possible mass of a neutron star (around 3 M_\odot). The masses are similar to those observed for black holes in X-ray binaries, so perhaps these black holes are all part of the same extended family.

A plot showing the probability distributions for the masses is shown below. It makes me happy. Since GW151226 is lower mass than GW150914, we see more of the inspiral, the portion of the signal where the two black holes are spiralling towards each other. This means that we measure the chirp mass, a particular combination of the two masses really well. It is this which gives the lovely banana shape to the distribution. Even though I don’t really like bananas, it’s satisfying to see this behaviour as this is what we have been expecting too see!

Binary black hole masses

Estimated masses for the two black holes in the binary of the Boxing Day Event. The dotted lines mark the edge of our 90% probability intervals. The different coloured curves show different models: they agree which again made me happy! The two-dimensional distribution follows a curve of constant chirp mass. The sharp cut-off at the top-left is because m_1^\mathrm{source} is defined to be bigger than m_2^\mathrm{source}. Figure 3 of The Boxing Day Discovery Paper.

The two black holes merge to form a final black hole of 20.8^{+6.1}_{-1.7} M_\odot [bonus note].

If you add up the initial binary masses and compare this to the final mass, you’ll notice that something is missing. Across the entire coalescence, gravitational waves carry away 1.0^{+0.1}_{-0.2} M_\odot c^2 \simeq 1.8^{+0.2}_{-0.4} \times 10^{47}~\mathrm{J} of energy (where c is the speed of light, which is used to convert masses to energies). This isn’t quite as impressive as the energy of GW150914, but it would take the Sun 1000 times the age of the Universe to output that much energy.

The mass measurements from GW151226 are cool, but what’re really exciting are the spin measurements. Spin, as you might guess, is a measure of how much angular momentum a black hole has. We define it to go from zero (not spinning) to one (spinning as much as is possible). A black hole is fully described by its mass and spin. The black hole masses are most important in defining what a gravitational wave looks like, but the imprint of spin is more subtle. Therefore its more difficult to get a good measurement of the spins than the masses.

For GW150915 and LVT151012, we get a little bit of information on the spins. We can conclude that the spins are probably not large, or at least they are not large and aligned with the orbit of the binary. However, we can’t say for certain that we’ve seen any evidence that the black holes are spinning. For GW151226, al least one of the black holes (although we can’t say which) has to be spinning [bonus note].

The plot below shows the probability distribution for the two spins of the binary black holes. This shows the both the magnitude of the spin and the direction that of the spin (if the tilt is zero the black hole and the binary’s orbit both go around in the same way). You can see we can’t say much about the spin of the lower mass black hole, but we have a good idea about the spin of the more massive black hole (the more extreme the mass ratio, the less important the spin of lower mass black is, making it more difficult to measure). Hopefully we’ll learn more about spins in future detections as these could tell us something about how these black holes formed.

Orientation and magnitudes of the two spins

Estimated orientation and magnitude of the two component spins. Calculated with our precessing waveform model. The distribution for the more massive black hole is on the left, and for the smaller black hole on the right. Part of Figure 4 of The Boxing Day Discovery Paper.

There’s still a lot to learn about binary black holes, and future detections will help with this. More information about what we can squeeze out of our current results are given in the O1 Binary Black Hole Paper.

The O1 Binary Black Hole Paper

Synopsis: O1 Binary Black Hole Paper
Read this if: You want to know everything we’ve learnt about binary black holes
Favourite part: The awesome table of parameters at the end

This paper contains too much science to tackle all at once, so I’ve split it up into more bite-sized pieces, roughly following the flow of the paper. First we discuss how we find signals. Then we discuss the parameters inferred from the signals. This is done assuming that general relativity is correct, so we check for any deviations from predictions in the next section. After that, we consider the rate of mergers and what we expect for the population of binary black holes from our detections. Finally, we discuss our results in the context of wider astrophysics.

Searches

Looking for signals hidden amongst the data is the first thing to do. This paper only talks about the template search for binary black holes: other search results (including the results for binaries including neutron stars) we will reported elsewhere.

The binary black hole search was previously described in the Compact Binary Coalescence Paper. We have two pipelines which look for binary black holes using templates: PyCBC and GstLAL. These look for signals which are found in both detectors (within 15 ms of each other) which match waveforms in the template bank. A few specifics of these have been tweaked since the start of O1, but these don’t really change any of the results. An overview of the details for both pipelines are given in Appendix A of the paper.

The big difference from Compact Binary Coalescence Paper is the data. We are now analysing the whole of O1, and we are using an improved version of the calibration (although this really doesn’t affect the search). Search results are given in Section II. We have one new detection: GW151226.

Search results and GW150914, GW151226 and LVT151012

Search results for PyCBC (left) and GstLAL (right). The histograms show the number of candidate events (orange squares) compare to the background. The further an orange square is to the right of the lines, the more significant it is. Different backgrounds are shown including and excluding GW150914 (top row) and GW151226 (bottom row). Figure 3 from the O1 Binary Black Hole Paper.

The plots above show the search results. Candidates are ranked by a detection statistic (a signal-to-noise ratio modified by a self-consistency check \hat{\rho}_c for PyCBC, and a ratio of likelihood for the signal and noise hypotheses \ln \mathcal{L} for GstLAL). A larger detection statistic means something is more signal-like and we assess the significance by comparing with the background of noise events. The further above the background curve an event is, the more significant it is. We have three events that stand out.

Number 1 is GW150914. Its significance has increased a little from the first analysis, as we can now compare it against more background data. If we accept that GW150914 is real, we should remove it from the estimation of the background: this gives us the purple background in the top row, and the black curve in the bottom row.

GW151226 is the second event. It clearly stands out when zooming in for the second row of plots. Identifying GW150914 as a signal greatly improves GW151226’s significance.

The final event is LVT151012. Its significance hasn’t changed much since the initial analysis, and is still below our threshold for detection. I’m rather fond of it, as I do love an underdog.

Parameter estimation

To figure out the properties of all three events, we do parameter estimation. This was previously described in the Parameter Estimation Paper. Our results for GW150914 and LVT151012 have been updated as we have reran with the newer calibration of the data. The new calibration has less uncertainty, which improves the precision of our results, although this is really only significant for the sky localization. Technical details of the analysis are given in Appendix B and results are discussed in Section IV. You may recognise the writing style of these sections.

The probability distributions for the masses are shown below. There is quite a spectrum, from the low mass GW151226, which is consistent with measurements of black holes in X-ray binaries, up to GW150914, which contains the biggest stellar-mass black holes ever observed.

All binary black hole masses

Estimated masses for the two binary black holes for each of the events in O1. The contours mark the 50% and 90% credible regions. The grey area is excluded from our convention that m_1^\mathrm{source} \geq m_2^\mathrm{source}. Part of Figure 4 of the O1 Binary Black Hole Paper.

The distributions for the lower mass GW151226 and LVT151012 follow the curves of constant chirp mass. The uncertainty is greater for LVT151012 as it is a quieter (lower SNR) signal. GW150914 looks a little different, as the merger and ringdown portions of the waveform are more important. These place tighter constraints on the total mass, explaining the shape of the distribution.

Another difference between the lower mass inspiral-dominated signals and the higher mass GW150915 can be seen in the plot below. The shows the probability distributions for the mass ratio q = m_2^\mathrm{source}/m_1^\mathrm{source} and the effective spin parameter \chi_\mathrm{eff}, which is a mass-weighted combination of the spins aligned with the orbital angular momentum. Both play similar parts in determining the evolution of the inspiral, so there are stretching degeneracies for GW151226 and LVT151012, but this isn’t the case for GW150914.

All mass ratios and effective spins

Estimated mass ratios q and effective spins \chi_\mathrm{eff} for each of the events in O1. The contours mark the 50% and 90% credible regions. Part of Figure 4 of the O1 Binary Black Hole Paper.

If you look carefully at the distribution of \chi_\mathrm{eff} for GW151226, you can see that it doesn’t extend down to zero. You cannot have a non-zero \chi_\mathrm{eff} unless at least one of the black holes is spinning, so this clearly shows the evidence for spin.

The final masses of the remnant black holes are shown below. Each is around 5% less than the total mass of the binary which merged to form it, with the rest radiated away as gravitational waves.

All final masses and spins

Estimated masses M_\mathrm{f}^\mathrm{source} and spins a_\mathrm{f} of the remnant black holes for each of the events in O1. The contours mark the 50% and 90% credible regions. Part of Figure 4 of the O1 Binary Black Hole Paper.

The plot also shows the final spins. These are much better constrained than the component spins as they are largely determined by the angular momentum of the binary as it merged. This is why the spins are all quite similar. To calculate the final spin, we use an updated formula compared to the one in the Parameter Estimation Paper. This now includes the effect of the components’ spin which isn’t aligned with the angular momentum. This doesn’t make much difference for GW150914 or LVT151012, but the change is slightly more for GW151226, as it seems to have more significant component spins.

The luminosity distance for the sources is shown below. We have large uncertainties because the luminosity distance is degenerate with the inclination. For GW151226 and LVT151012 this does result in some beautiful butterfly-like distance–inclination plots. For GW150914, the butterfly only has the face-off inclination wing (probably as consequence of the signal being louder and the location of the source on the sky). The luminosity distances for GW150914 and GW151226 are similar. This may seem odd, because GW151226 is a quieter signal, but that is because it is also lower mass (and so intrinsically quieter).

All luminosity distances

Probability distributions for the luminosity distance of the source of each of the three events in O1. Part of Figure 4 of the O1 Binary Black Hole Paper.

Sky localization is largely determined by the time delay between the two observatories. This is one of the reasons that having a third detector, like Virgo, is an awesome idea. The plot below shows the localization relative to the Earth. You can see that each event has a localization that is part of a ring which is set by the time delay. GW150914 and GW151226 were seen by Livingston first (apparently there is some gloating about this), and LVT151012 was seen by Hanford first.

Sky localization relative to Earth.

Estimated sky localization relative to the Earth for each of the events in O1. The contours mark the 50% and 90% credible regions. H+ and L+ mark the locations of the two observatories. Part of Figure 5 of the O1 Binary Black Hole Paper.

Both GW151226 and LVT151012 are nearly overhead. This isn’t too surprising, as this is where the detectors are most sensitive, and so where we expect to make the most detections.

The improvement in the calibration of the data is most evident in the sky localization. For GW150914, the reduction in calibration uncertainty improves the localization by a factor of ~2–3! For LVT151012 it doesn’t make much difference because of its location and because it is a much quieter signal.

The map below shows the localization on the sky (actually where in Universe the signal came from). The maps have rearranged themselves because of the Earth’s rotation (each event was observed at a different sidereal time).

Sky localization in equatorial coordinates

Estimated sky localization (in right ascension and declination) for each of the events in O1. The contours mark the 50% and 90% credible regions. Part of Figure 5 of the O1 Binary Black Hole Paper.

We’re nowhere near localising sources to single galaxies, so we may never know exactly where these signals originated from.

Tests of general relativity

The Testing General Relativity Paper reported several results which compared GW150914 with the predictions of general relativity. Either happily or sadly, depending upon your point of view, it passed them all. In Section V of the paper, we now add GW151226 into the mix. (We don’t add LVT151012 as it’s too quiet to be much use).

A couple of the tests for GW150914 looked at the post-inspiral part of the waveform, looking at the consistency of mass and spin estimates, and trying to match the rigdown frequency. Since GW151226 is lower mass, we can’t extract any meaningful information from the post-inspiral portion of the waveform, and so it’s not worth repeating these tests.

However, the fact that GW151226 has such a lovely inspiral means that we can place some constraints on post-Newtonian parameters. We have lots and lots of cycles, so we are sensitive to any small deviations that arise during inspiral.

The plot below shows constraints on deviations for a set of different waveform parameters. A deviation of zero indicates the value in general relativity. The first four boxes (for parameters referred to as \varphi_i in the Testing General Relativity Paper) are parameters that affect the inspiral. The final box on the right is for parameters which impact the merger and ringdown. The top row shows results for GW150914, these are updated results using the improved calibrated data. The second row shows results for GW151226, and the bottom row shows what happens when you combine the two.

O1 testing general relativity bounds

Probability distributions for waveform parameters. The top row shows bounds from just GW150914, the second from just GW151226, and the third from combining the two. A deviation of zero is consistent with general relativity. Figure 6 from the O1 Binary Black hole Paper.

All the results are happily about zero. There were a few outliers for GW150914, but these are pulled back in by GW151226. We see that GW151226 dominates the constraints on the inspiral parameters, but GW150914 is more important for the merger–ringdown \alpha_i parameters.

Again, Einstein’s theory passes the test. There is no sign of inconsistency (yet). It’s clear that adding more results greatly improves our sensitivity to these parameters, so these tests will continue put general relativity through tougher and tougher tests.

Rates

We have a small number of events, around 2.9 in total, so any estimates of how often binary black holes merge will be uncertain. Of course, just because something is tricky, it doesn’t mean we won’t give it a go! The Rates Paper discussed estimates after the first 16 days of coincident data, when we had just 1.9 events. Appendix C gives technical details and Section VI discusses results.

The whole of O1 is about 52 days’ worth of coincident data. It’s therefore about 3 times as long as the initial stretch. in that time we’ve observed about 3/2 times as many events. Therefore, you might expect that the event rate is about 1/2 of our original estimates. If you did, get yourself a cookie, as you are indeed about right!

To calculate the rates we need to assume something about the population of binary black holes. We use three fiducial distributions:

  1. We assume that binary black holes are either like GW150914, LVT151012 or GW151226. This event-based rate is different from the previous one as it now includes an extra class for GW151226.
  2. A flat-in-the-logarithm-of-masses distribution, which we expect gives a sensible lower bound on the rate.
  3. A power law slope for the larger black hole of -2.35, which we expect gives a sensible upper bound on the rate.

We find that the rates are 1. 54^{+111}_{-40}~\mathrm{Gpc^{-3}\,yr^{-1}}, 2. 30^{+46}_{-21}~\mathrm{Gpc^{-3}\,yr^{-1}}, and 3. 97^{+149}_{-68}~\mathrm{Gpc^{-3}\,yr^{-1}}. As expected, the first rate is nestled between the other two.

Despite the rates being lower, there’s still a good chance we could see 10 events by the end of O2 (although that will depend on the sensitivity of the detectors).

A new results that is included in with the rates, is a simple fit for the distribution of black hole masses [bonus note]. The method is described in Appendix D. It’s just a repeated application of Bayes’ theorem to go from the masses we measured from the detected sources, to the distribution of masses of the entire population.

We assume that the mass of the larger black hole is distributed according to a power law with index \alpha, and that the less massive black hole has a mass uniformly distributed in mass ratio, down to a minimum black hole mass of 5 M_\odot. The cut-off, is the edge of a speculated mass gap between neutron stars and black holes.

We find that \alpha = 2.5^{+1.5}_{-1.6}. This has significant uncertainty, so we can’t say too much yet. This is a slightly steeper slope than used for the power-law rate (although entirely consistent with it), which would nudge the rates a little lower. The slope does fit in with fits to the distribution of masses in X-ray binaries. I’m excited to see how O2 will change our understanding of the distribution.

Astrophysical implications

With the announcement of GW150914, the Astrophysics Paper reviewed predictions for binary black holes in light of the discovery. The high masses of GW150914 indicated a low metallicity environment, perhaps no more than half of solar metallicity. However, we couldn’t tell if GW150914 came from isolated binary evolution (two stars which have lived and died together) or a dynamical interaction (probably in a globular cluster).

Since then, various studies have been performed looking at both binary evolution (Eldridge & Stanway 2016; Belczynski et al. 2016de Mink & Mandel 2016Hartwig et al. 2016; Inayoshi et al. 2016; Lipunov et al. 2016) and dynamical interactions (O’Leary, Meiron & Kocsis 2016; Mapelli 2016; Rodriguez et al. 2016), even considering binaries around supermassive black holes (Bartos et al. 2016; Stone, Metzger & Haiman 2016). We don’t have enough information to tell the two pathways apart. GW151226 gives some new information. Everything is reviewed briefly in Section VII.

GW151226 and LVT151012 are lower mass systems, and so don’t need to come from as low a metallicity environment as GW150914 (although they still could). Both are also consistent with either binary evolution or dynamical interactions. However, the low masses of GW151226 mean that it probably does not come from one particular binary formation scenario, chemically homogeneous evolution, and it is less likely to come from dynamical interactions.

Building up a population of sources, and getting better measurements of spins and mass ratios will help tease formation mechanisms apart. That will take a while, but perhaps it will be helped if we can do multi-band gravitational-wave astronomy with eLISA.

This section also updates predictions from the Stochastic Paper for the gravitational-wave background from binary black holes. There’s a small change from an energy density of \Omega_\mathrm{GW} = 1.1^{+2.7}_{-0.9} \times 10^{-9} at a frequency of 25 Hz to \Omega_\mathrm{GW} = 1.2^{+1.9}_{-0.9} \times 10^{-9}. This might be measurable after a few years at design sensitivity.

Conclusion

We are living in the future. We may not have hoverboards, but the era of gravitational-wave astronomy is here. Not in 20 years, not in the next decade, not in five more years, now. LIGO has not just opened a new window, it’s smashed the window and jumped through it just before the explosion blasts the side off the building. It’s so exciting that I can’t even get my metaphors straight. The introductory paragraphs of papers on gravitational-wave astronomy will never be the same again.

Although we were lucky to discover GW150914, it wasn’t just a fluke. Binary black coalescences aren’t that rare and we should be detecting more. Lots more. You know that scene in a movie where the heroes have defeated a wave of enemies and then the camera pans back to show the approaching hoard that stretches to the horizon? That’s where we are now. O2 is coming. The second observing run, will start later this year, and we expect we’ll be adding many entries to our list of binary black holes.

We’re just getting started with LIGO and Virgo. There’ll be lots more science to come.

If you made it this far, you deserve a biscuit. A fancy one too, not just a digestive.

Or, if you’re hungry for more, here are some blogs from my LIGO colleagues

  • Daniel Williams (a PhD student at University of Glasgow)
  • Matt Pitkin (who is hunting for continuous gravitational waves)
  • Shane Larson (who is also investigating mutli-band gravitational-wave astronomy)
  • Amber Sturver (who works at the Livingston Observatory)

My group at Birmingham also made some short reaction videos (I’m too embarrassed to watch mine).

Bonus notes

Christmas cease-fire

In the run-up to the holidays, there were lots of emails that contained phrases like “will have to wait until people get back from holidays” or “can’t reply as the group are travelling and have family commitments”. No-one ever said that they were taking a holiday, but just that it was happening in general, so we’d all have to wait for a couple of weeks. No-one ever argued with this, because, of course, while you were waiting for other people to do things, there was nothing you could do, and so you might as well take some time off. And you had been working really hard, so perhaps an evening off and an extra slice of cake was deserved…

Rather guiltily, I must confess to ignoring the first few emails on Boxing Day. (Although I saw them, I didn’t read them for reasons of plausible deniability). I thought it was important that my laptop could have Boxing Day off. Thankfully, others in the Collaboration were more energetic and got things going straight-away.

Naming

Gravitational-wave candidates (or at least the short ones from merging binary black holes which we have detected so far), start off life named by a number in our database. This event started life out as G211117. After checks and further analysis, to make sure we can’t identify any environmental effects which could have caused the detector to misbehave, candidates are renamed. Those which are significant enough to be claimed as a detection get the Gravitational Wave (GW) prefix. Those we are less certain of get the LIGO–Virgo Trigger (LVT) prefix. The rest of the name is the date in Coordinated Universal Time (UTC). The new detection is GW151226.

Informally though, it is the Boxing Day Event. I’m rather impressed that this stuck as the Collaboration is largely US based: it was still Christmas Day in the US when the detection was made, and Americans don’t celebrate Boxing Day anyway.

Other searches

We are now publishing the results of the O1 search for binary black holes with a template bank which goes up to total observed binary masses of 100 M_\odot. Therefore we still have to do the same about searches for anything else. The results from searches for other compact binaries should appear soon (binary neutron star and neutron star–black hole upper limits). It may be a while before we have results looking for continuous waves.

Matched filtering

The compact binary coalescence search uses matched filtering to hunt for gravitational waves. This is a well established technique in signal processing. You have a template signal, and you see how this correlates with the data. We use the detectors’ sensitivity to filter the data, so that we give more weight to bits which match where we are sensitive, and little weight to matches where we have little sensitivity.

I imagine matched filtering as similar to how I identify a piece of music: I hear a pattern of notes and try to compare to things I know. Dum-dum-dum-daah? Beethoven’s Fifth.

Filtering against a large number of templates takes a lot of computational power, so we need to be cunning as to which templates we include. We don’t want to miss anything, so we need enough templates to cover all possibilities, but signals from similar systems can look almost identical, so we just need one representative template included in the bank. Think of trying to pick out Under Pressure, you could easily do this with a template for Ice Ice Baby, and you don’t need both Mr Brightside and Ode to Joy.

It doesn’t matter if the search doesn’t pick out a template that perfectly fits the properties of the source, as this is what parameter estimation is for.

The figure below shows how effective matched filtering can be.

  • The top row shows the data from the two interferometers. It’s been cleaned up a little bit for the plot (to keep the experimentalists happy), but you can see that the noise in the detectors is seemingly much bigger than the best match template (shown in black, the same for both detectors).
  • The second row shows the accumulation of signal-to-noise ratio (SNR). If you correlate the data with the template, you see that it matches the template, and keeps matching the template. This is the important part, although, at any moment it looks like there’s just random wibbles in the detector, when you compare with a template you find that there is actually a signal which evolves in a particular way. The SNR increases until the signal stops (because the black holes have merged). It is a little lower in the Livinston detector as this was slightly less sensitive around the time of the Boxing Day Event.
  • The third row shows how much total SNR you would get if you moved the best match template around in time. There’s a clear peak. This is trying to show that the way the signal changes is important, and you wouldn’t get a high SNR when the signal isn’t there (you would normally expect it to be about 1).
  • The final row shows the amount of energy at a particular frequency at a particular time. Compact binary coalescences have a characteristic chirp, so you would expect a sweep from lower frequencies up to higher frequencies. You can just about make it out in these plots, but it’s not obvious as for GW150914. This again shows the value of matched filtering, but it also shows that there’s no other weird glitchy stuff going on in the detectors at the time.
The effectiveness of matched filtering for GW151226

Observation of The Boxing Day Event in LIGO Hanford and LIGO Livingston. The top row shows filtered data and best match template. The second row shows how this template accumulates signal-to-noise ratio. The third row shows signal-to-noise ratio of this template at different end times. The fourth row shows a spectrogram of the data. Figure 1 of the Boxing Day Discovery Paper.

Electromagnetic follow-up

Reports by electromagnetic astronomers on their searches for counterparts so far are:

No counterparts have been claimed, which isn’t surprising for a binary black hole coalescence.

Rounding

In various places, the mass of the smaller black hole is given as 8 M_\odot. The median should really round to 7 M_\odot as to three significant figures it is 7.48 M_\odot. This really confused everyone though, as with rounding you’d have a binary with components of masses 14 M_\odot and 7 M_\odot and total mass 22 M_\odot. Rounding is a pain! Fortunately, 8 M_\odot lies well within the uncertainty: the 90% range is 5.2\text{--}9.8 M_\odot.

Black holes are massive

I tried to find a way to convert the mass of the final black hole into every day scales. Unfortunately, the thing is so unbelievably massive, it just doesn’t work: it’s no use relating it to elephants or bowling balls. However, I did have some fun looking up numbers. Currently, it costs about £2 to buy a 180 gram bar of Cadbury’s Bourneville. Therefore, to buy an equivalent amount of dark chocolate would require everyone on Earth to save up for about 600 millions times the age of the Universe (assuming GDP stays constant). By this point, I’m sure the chocolate will be past its best, so it’s almost certainly a big waste of time.

Maximum minimum spin

One of the statistics people really seemed to latch on to for the Boxing Day Event was that at least one of the binary black holes had to have a spin of greater than 0.2 with 99% probability. It’s a nice number for showing that we have a preference for some spin, but it can be a bit tricky to interpret. If we knew absolutely nothing about the spins, then we would have a uniform distribution on both spins. There’d be a 10% chance that the spin of the more massive black hole is less than 0.1, and a 10% chance that the spin of the other black hole is less than 0.1. Hence, there’s a 99% probability that there is at least one black hole with spin greater than 0.1, even though we have no evidence that the black holes are spinning (or not). Really, you need to look at the full probability distributions for the spins, and not just the summary statistics, to get an idea of what’s going on.

Just one more thing…

The fit for the black hole mass distribution was the last thing to go in the paper. It was a bit frantic to get everything reviewed in time. In the last week, there were a couple of loud exclamations from the office next to mine, occupied by John Veitch, who as one of the CBC chairs has to keep everything and everyone organised. (I’m not quite sure how John still has so much of his hair). It seems that we just can’t stop doing science. There is a more sophisticated calculation in the works, but the foot was put down that we’re not trying to cram any more into the current papers.

Prospects for observing and localizing gravitational-wave transients with Advanced LIGO and Advanced Virgo

The week beginning February 8th was a big one for the LIGO and Virgo Collaborations. You might remember something about a few papers on the merger of a couple of black holes; however, those weren’t the only papers we published that week. In fact, they aren’t even (currently) the most cited

Prospects for Observing and Localizing Gravitational-Wave Transients with Advanced LIGO and Advanced Virgo is known within the Collaboration as the Observing Scenarios Document. It has a couple of interesting aspects

  • Its content is a mix of a schedule for detector commissioning and an explanation of data analysis. It is a rare paper that spans both the instrumental and data-analysis sides of the Collaboration.
  • It is a living review: it is intended to be periodically updated as we get new information.

There is also one further point of interest for me: I was heavily involved in producing this latest version.

In this post I’m going to give an outline of the paper’s content, but delve a little deeper into the story of how this paper made it to print.

The Observing Scenarios

The paper is divided up into four sections.

  1. It opens, as is traditional, with the introduction. This has no mentions of windows, which is a good start.
  2. Section 2 is the instrumental bit. Here we give a possible timeline for the commissioning of the LIGO and Virgo detectors and a plausible schedule for our observing runs.
  3. Next we talk about data analysis for transient (short) gravitational waves. We discuss detection and then sky localization.
  4. Finally, we bring everything together to give an estimate of how well we expect to be able to locate the sources of gravitational-wave signals as time goes on.

Packaged up, the paper is useful if you want to know when LIGO and Virgo might be observing or if you want to know how we locate the source of a signal on the sky. The aim was to provide a guide for those interested in multimessenger astronomy—astronomy where you rely on multiple types of signals like electromagnetic radiation (light, radio, X-rays, etc.), gravitational waves, neutrinos or cosmic rays.

The development of the detectors’ sensitivity is shown below. It takes many years of tweaking and optimising to reach design sensitivity, but we don’t wait until then to do some science. It’s just as important to practise running the instruments and analysing the data as it is to improve the sensitivity. Therefore, we have a series of observing runs at progressively higher sensitivity. Our first observing run (O1), featured just the two LIGO detectors, which were towards the better end of the expected sensitivity.

Possible advanced detector sensitivity

Plausible evolution of the Advanced LIGO and Advanced Virgo detectors with time. The lower the sensitivity curve, the further away we can detect sources. The distances quoted is range we could see binary neutrons stars (BNSs) to. The BNS-optimized curve is a proposal to tweak the detectors for finding BNSs. Fig. 1 of the Observing Scenarios Document.

It’s difficult to predict exactly how the detectors will progress (we’re doing many things for the first time ever), but the plot above shows our current best plan.

I’ll not go into any more details about the science in the paper as I’ve already used up my best ideas writing the LIGO science summary.

If you’re particularly interested in sky localization, you might like to check out the data releases for studies using (simulated) binary neutron star and burst signals. The binary neutron star analysis is similar to that we do for any compact binary coalescence (the merger of a binary containing neutron stars or black holes), and the burst analysis works more generally as it doesn’t require a template for the expected signal.

The path to publication

Now, this is the story of how a Collaboration paper got published. I’d like to take a minute to tell you how I became responsible for updating the Observing Scenarios…

In the beginning

The Observing Scenarios has its origins long before I joined the Collaboration. The first version of the document I can find is from July 2012. Amongst the labyrinth of internal wiki pages we have, the earliest reference I’ve uncovered was from August 2012 (the plan was to have a mature draft by September). The aim was to give a road map for the advanced-detector era, so the wider astronomical community would know what to expect.

I imagine it took a huge effort to bring together all the necessary experts from across the Collaboration to sit down and write the document.

Any document detailing our plans would need to be updated regularly as we get a better understanding of our progress on commissioning the detectors (and perhaps understanding what signals we will see). Fortunately, there is a journal that can cope with just that: Living Reviews in Relativity. Living Reviews is designed so that authors can update their articles so that they never become (too) out-of-date.

A version was submitted to Living Reviews early in 2013, around the same time as a version was posted to the arXiv. We had referee reports (from two referees), and were preparing to resubmit. Unfortunately, Living Reviews suspended operations before we could. However, work continued.

Updating sky localization

I joined the LIGO Scientific Collaboration when I started at the University of Birmingham in October 2013. I soon became involved in a variety of activities of the Parameter Estimation group (my boss, Alberto Vecchio, is the chair of the group).

Sky localization was a particularly active area as we prepared for the first runs of Advanced LIGO. The original version of the Observing Scenarios Document used a simple approximate means of estimating sky localization, using just timing triangulation (it didn’t even give numbers for when we only had two detectors running). We knew we could do better.

We had all the code developed, but we needed numbers for a realistic population of signals. I was one of the people who helped running the analyses to get these. We had the results by the summer of 2014; we now needed someone to write up the results. I have a distinct recollection of there being silence on our weekly teleconference. Then Alberto asked me if I would do it? I said yes: it would probably only take me a week or two to write a short technical note.

Saying yes is a slippery slope.

That note became Parameter estimation for binary neutron-star coalescences with realistic noise during the Advanced LIGO era, a 24-page paper (it considers more than just sky localization).

Numbers in hand, it was time to update the Observing Scenarios. Even if things were currently on hold with Living Reviews, we could still update the arXiv version. I thought it would be easiest if I put them in, with a little explanation, myself. I compiled a draft and circulated in the Parameter Estimation group. Then it was time to present to the Data Analysis Council.

The Data Analysis Council either sounds like a shadowy organisation orchestrating things from behind the scene, or a place where people bicker over trivial technical issues. In reality it is a little of both. This is the body that should coordinate all the various bits of analysis done by the Collaboration, and they have responsibility for the Observing Scenarios Document. I presented my update on the last call before Christmas 2014. They were generally happy, but said that the sky localization on the burst side needed updating too! There was once again a silence on the call when it came to the question of who would finish off the document. The Observing Scenarios became my responsibility.

(I had though that if I helped out with this Collaboration paper, I could take the next 900 off. This hasn’t worked out.)

The review

With some help from the Burst group (in particular Reed Essick, who had lead their sky localization study), I soon had a new version with fully up-to-date sky localization. This was ready for our March Collaboration meeting. I didn’t go (I was saving my travel budget for the summer), so Alberto presented on my behalf. It was now agreed that the document should go through internal review.

It’s this which I really want to write about. Peer review is central to modern science. New results are always discussed by experts in the community, to try to understand the value of the work; however, peer review is formalised in the refereeing of journal articles, when one or more (usually anonymous) experts examine work before it can be published. There are many ups and down with this… For Collaboration papers, we want to be sure that things are right before we share them publicly. We go through internal peer review. In my opinion this is much more thorough than journal review, and this shows how seriously the Collaboration take their science.

Unfortunately, setting up the review was also where we hit a hurdle—it took until July. I’m not entirely sure why there was a delay: I suspect it was partly because everyone was busy assembling things ahead of O1 and partly because there were various discussions amongst the high-level management about what exactly we should be aiming for. Working as part of a large collaboration can mean that you get to be involved in wonderful science, but it can means lots of bureaucracy and politics. However, in the intervening time, Living Reviews was back in operation.

The review team consisted of five senior people, each of whom had easily five times as much experience as I do, with expertise in each of the areas covered in the document. The chair of the review was Alan Weinstein, head of the Caltech LIGO Laboratory Astrophysics Group, who has an excellent eye for detail. Our aim was to produce the update for the start of O1 in September. (Spolier: We didn’t make it)

The review team discussed things amongst themselves and I got the first comments at the end of August. The consensus was that we should not just update the sky localization, but update everything too (including the structure of the document). This precipitated a flurry of conversations with the people who organise the schedules for the detectors, those who liaise with our partner astronomers on electromagnetic follow-up, and everyone who does sky localization. I was initially depressed that we wouldn’t make our start of O1 deadline; however, then something happened that altered my perspective.

On September 14, four days before the official start of O1, we made a detection. GW150914 would change everything.

First, we could no longer claim that binary neutron stars were expected to be our most common source—instead they became the source we expect would most commonly have an electromagnetic counterpart.

Second, we needed to be careful how we described engineering runs. GW150914 occurred in our final engineering run (ER8). Practically, there was difference between the state of the detector then and in O1. The point of the final engineering run was to get everything running smoothly so all we needed to do at the official start of O1 was open the champagne. However, we couldn’t make any claims about being able to make detections during engineering runs without being krass and letting the cat out of the bag. I’m rather pleased with the sentence

Engineering runs in the commissioning phase allow us to understand our detectors and analyses in an observational mode; these are not intended to produce astrophysical results, but that does not preclude the possibility of this happening.

I don’t know if anyone noticed the implication. (Checking my notes, this was in the September 18 draft, which shows how quickly we realised the possible significance of The Event).

Finally, since the start of observations proved to be interesting, and because the detectors were running so smoothly, it was decided to extend O1 from three months to four so that it would finish in January. No commissioning was going to be done over the holidays, so it wouldn’t affect the schedule. I’m not sure how happy the people who run the detectors were about working over this period, but they agreed to the plan. (No-one asked if we would be happy to run parameter estimation over the holidays).

After half-a-dozen drafts, the review team were finally happy with the document. It was now October 20, and time to proceed to the next step of review: circulation to the Collaboration.

Collaboration papers go through a sequence of stages. First they are circulated to the everyone for comments. This can be pointing out typos, suggesting references or asking questions about the analysis. This lasts two weeks. During this time, the results must also be presented on a Collaboration-wide teleconference. After comments are addressed, the paper is sent for examination Executive Committees of the LIGO and Virgo Collaborations. After approval from them (and the review team check any changes), the paper is circulated to the Collaboration again for any last comments and checking of the author list. At the same time it is sent to the Gravitational Wave International Committee, a group of all the collaborations interested in gravitational waves. This final stage is a week. Then you can you can submit the paper.

Peer review for the journal doesn’t seem to arduous in comparison does it?

Since things were rather busy with all the analysis of GW150914, the Observing Scenario took a little longer than usual to clear all these hoops. I presented to the Collaboration on Friday 13 November. (This was rather unlucky as I was at a workshop in Italy and I had to miss the tour of the underground Laboratori Nazionali del Gran Sasso). After addressing comments from everyone (the Executive Committees do read things carefully), I got the final sign-off to submit December 21. At least we made it before the end of O1.

Good things come…

This may sound like a tale of frustration and delay. However, I hope that it is more than that, and it shows how careful the Collaboration is. The Observing Scenarios is really a review: it doesn’t contain new science. The updated sky localization results are from studies which have appeared in peer-reviewed journals, and are based upon codes that have been separately reviewed. Despite this, every statement was examined and every number checked and rechecked, and every member of the Collaboration had opportunity to examine the results and comment on the document.

I guess this attention to detail isn’t surprising given that our work is based on measuring a change in length of one part in 1,000,000,000,000,000,000,000.

Since this is how we treat review articles, can you imagine how much scrutiny the Discovery Paper had? Everything had at least one extra layer of review, every number had to be signed-off individually by the appropriate review team, and there were so many comments on the paper that the editors had to switch to using a ticketing system we normally use for tracking bugs in our software. This level of oversight helped me to sleep a little more easily: there are six numbers in the abstract alone I could have potentially messed up.

Of course, all this doesn’t mean we can’t make mistakes…

Looking forward

The Living Reviews version was accepted January 22, just after the end of O1. We made had to make a couple of tweaks to correct tenses. The final version appeared February 8, in time to be the last paper of the pre-discovery era.

It is now time to be thinking about the next update! There are certainly a few things on the to-do list (perhaps even some news on LIGO-India). We are having a Collaboration meeting in a couple of weeks’ time, so hopefully I can start talking to people about it then. Perhaps it’ll be done by the start of O2?

arXiv: 1304.0670 [gr-qc]
Journal: Living Reviews In Relativity; 19:1(39); 2016
Science summary: Planning for a Bright Tomorrow: Prospects for Gravitational-wave Astronomy with Advanced LIGO and Advanced Virgo
Bonus fact:
 This is the only paper whose arXiv ID I know by heart [update].

arXiv IDs

Papers whose arXiv numbers I know by heart are: 1304.0670, 1602.03840 (I count to other GW150914 companion papers from here), 1606.04856 and 1706.01812. These might tell you something about my reading habits.

GW150914—The papers

In 2015 I made a resolution to write a blog post for each paper I had published. In 2016 I’ll have to break this because there are too many to keep up with. A suite of papers were prepared to accompany the announcement of the detection of GW150914 [bonus note], and in this post I’ll give an overview of these.

The papers

As well as the Discovery Paper published in Physical Review Letters [bonus note], there are 12 companion papers. All the papers are listed below in order of arXiv posting. My favourite is the Parameter Estimation Paper.

Subsequently, we have produced additional papers on GW150914, describing work that wasn’t finished in time for the announcement.

0. The Discovery Paper

Title: Observation of gravitational waves from a binary black hole merger
arXiv:
 1602.03837 [gr-qc]
Journal:
 Physical Review Letters; 116(6):061102(16); 2016
LIGO science summary:
 Observation of gravitational waves from a binary black hole merger

This is the central paper that announces the observation of gravitational waves. There are three discoveries which are describe here: (i) the direct detection of gravitational waves, (ii) the existence of stellar-mass binary black holes, and (iii) that the black holes and gravitational waves are consistent with Einstein’s theory of general relativity. That’s not too shabby in under 11 pages (if you exclude the author list). Coming 100 years after Einstein first published his prediction of gravitational waves and Schwarzschild published his black hole solution, this is the perfect birthday present.

More details: The Discovery Paper summary

1. The Detector Paper

Title: GW150914: The Advanced LIGO detectors in the era of first discoveries
arXiv:
 1602.03838 [gr-qc]
Journal: Physical Review Letters; 116(13):131103(12); 2016

This paper gives a short summary of how the LIGO detectors work and their configuration in O1 (see the Advanced LIGO paper for the full design). Giant lasers and tiny measurements, the experimentalists do some cool things (even if their paper titles are a little cheesy and they seem to be allergic to error bars).

More details: The Detector Paper summary

2. The Compact Binary Coalescence Paper

Title: GW150914: First results from the search for binary black hole coalescence with Advanced LIGO
arXiv:
 1602.03839 [gr-qc]
Journal: Physical Review D; 93(12):122003(21); 2016

Here we explain how we search for binary black holes and calculate the significance of potential candidates. This is the evidence to back up (i) in the Discovery Paper. We can potentially detect binary black holes in two ways: with searches that use templates, or with searches that look for coherent signals in both detectors without assuming a particular shape. The first type is also used for neutron star–black hole or binary neutron star coalescences, collectively known as compact binary coalescences. This type of search is described here, while the other type is described in the Burst Paper.

This paper describes the compact binary coalescence search pipelines and their results. As well as GW150914 there is also another interesting event, LVT151012. This isn’t significant enough to be claimed as a detection, but it is worth considering in more detail.

More details: The Compact Binary Coalescence Paper summary

3. The Parameter Estimation Paper

Title: Properties of the binary black hole merger GW150914
arXiv:
 1602.03840 [gr-qc]
Journal: Physical Review Letters; 116(24):241102(19); 2016
LIGO science summary: The first measurement of a black hole merger and what it means

If you’re interested in the properties of the binary black hole system, then this is the paper for you! Here we explain how we do parameter estimation and how it is possible to extract masses, spins, location, etc. from the signal. These are the results I’ve been most heavily involved with, so I hope lots of people will find them useful! This is the paper to cite if you’re using our best masses, spins, distance or sky maps. The masses we infer are so large we conclude that the system must contain black holes, which is discovery (ii) reported in the Discovery Paper.

More details: The Parameter Estimation Paper summary

4. The Testing General Relativity Paper

Title: Tests of general relativity with GW150914
arXiv:
 1602.03841 [gr-qc]
Journal: Physical Review Letters; 116(22):221101(19); 2016
LIGO science summary:
 Was Einstein right about strong gravity?

The observation of GW150914 provides a new insight into the behaviour of gravity. We have never before probed such strong gravitational fields or such highly dynamical spacetime. These are the sorts of places you might imagine that we could start to see deviations from the predictions of general relativity. Aside from checking that we understand gravity, we also need to check to see if there is any evidence that our estimated parameters for the system could be off. We find that everything is consistent with general relativity, which is good for Einstein and is also discovery (iii) in the Discovery Paper.

More details: The Testing General Relativity Paper summary

5. The Rates Paper

Title: The rate of binary black hole mergers inferred from Advanced LIGO observations surrounding GW150914
arXiv:
 1602.03842 [astro-ph.HE]1606.03939 [astro-ph.HE]
Journal: Astrophysical Journal Letters; 833(1):L1(8); 2016; Astrophysical Journal Supplement Series; 227(2):14(11); 2016
LIGO science summary: The first measurement of a black hole merger and what it means

Given that we’ve spotted one binary black hole (plus maybe another with LVT151012), how many more are out there and how many more should we expect to find? We answer this here, although there’s a large uncertainty on the estimates since we don’t know (yet) the distribution of masses for binary black holes.

More details: The Rates Paper summary

6. The Burst Paper

Title: Observing gravitational-wave transient GW150914 with minimal assumptions
arXiv: 1602.03843 [gr-qc]
Journal: Physical Review D; 93(12):122004(20); 2016

What can you learn about GW150914 without having to make the assumptions that it corresponds to gravitational waves from a binary black hole merger (as predicted by general relativity)? This paper describes and presents the results of the burst searches. Since the pipeline which first found GW150914 was a burst pipeline, it seems a little unfair that this paper comes after the Compact Binary Coalescence Paper, but I guess the idea is to first present results assuming it is a binary (since these are tightest) and then see how things change if you relax the assumptions. The waveforms reconstructed by the burst models do match the templates for a binary black hole coalescence.

More details: The Burst Paper summary

7. The Detector Characterisation Paper

Title: Characterization of transient noise in Advanced LIGO relevant to gravitational wave signal GW150914
arXiv: 1602.03844 [gr-qc]
Journal: Classical & Quantum Gravity; 33(13):134001(34); 2016
LIGO science summary:
How do we know GW150914 was real? Vetting a Gravitational Wave Signal of Astrophysical Origin
CQG+ post: How do we know LIGO detected gravitational waves? [featuring awesome cartoons]

Could GW150914 be caused by something other than a gravitational wave: are there sources of noise that could mimic a signal, or ways that the detector could be disturbed to produce something that would be mistaken for a detection? This paper looks at these problems and details all the ways we monitor the detectors and the external environment. We can find nothing that can explain GW150914 (and LVT151012) other than either a gravitational wave or a really lucky random noise fluctuation. I think this paper is extremely important to our ability to claim a detection and I’m surprised it’s not number 2 in the list of companion papers. If you want to know how thorough the Collaboration is in monitoring the detectors, this is the paper for you.

More details: The Detector Characterisation Paper summary

8. The Calibration Paper

Title: Calibration of the Advanced LIGO detectors for the discovery of the binary black-hole merger GW150914
arXiv:
 1602.03845 [gr-qc]
Journal: Physical Review D; 95(6):062003(16); 2017
LIGO science summary:
 Calibration of the Advanced LIGO detectors for the discovery of the binary black-hole merger GW150914

Completing the triumvirate of instrumental papers with the Detector Paper and the Detector Characterisation Paper, this paper describes how the LIGO detectors are calibrated. There are some cunning control mechanisms involved in operating the interferometers, and we need to understand these to quantify how they effect what we measure. Building a better model for calibration uncertainties is high on the to-do list for improving parameter estimation, so this is an interesting area to watch for me.

More details: The Calibration Paper summary

9. The Astrophysics Paper

Title: Astrophysical implications of the binary black-hole merger GW150914
arXiv:
 1602.03846 [astro-ph.HE]
Journal: Astrophysical Journal Letters; 818(2):L22(15); 2016
LIGO science summary:
 The first measurement of a black hole merger and what it means

Having estimated source parameters and rate of mergers, what can we say about astrophysics? This paper reviews results related to binary black holes to put our findings in context and also makes statements about what we could hope to learn in the future.

More details: The Astrophysics Paper summary

10. The Stochastic Paper

Title: GW150914: Implications for the stochastic gravitational wave background from binary black holes
arXiv:
 1602.03847 [gr-qc]
Journal: Physical Review Letters; 116(13):131102(12); 2016
LIGO science summary: Background of gravitational waves expected from binary black hole events like GW150914

For every loud signal we detect, we expect that there will be many more quiet ones. This paper considers how many quiet binary black hole signals could add up to form a stochastic background. We may be able to see this background as the detectors are upgraded, so we should start thinking about what to do to identify it and learn from it.

More details: The Stochastic Paper summary

11. The Neutrino Paper

Title: High-energy neutrino follow-up search of gravitational wave event GW150914 with ANTARES and IceCube
arXiv:
 1602.05411 [astro-ph.HE]
Journal: Physical Review D; 93(12):122010(15); 2016
LIGO science summary: Search for neutrinos from merging black holes

We are interested so see if there’s any other signal that coincides with a gravitational wave signal. We wouldn’t expect something to accompany a black hole merger, but it’s good to check. This paper describes the search for high-energy neutrinos. We didn’t find anything, but perhaps we will in the future (perhaps for a binary neutron star merger).

More details: The Neutrino Paper summary

12. The Electromagnetic Follow-up Paper

Title: Localization and broadband follow-up of the gravitational-wave transient GW150914
arXiv: 1602.08492 [astro-ph.HE]; 1604.07864 [astro-ph.HE]
Journal: Astrophysical Journal Letters; 826(1):L13(8); 2016; Astrophysical Journal Supplement Series; 225(1):8(15); 2016

As well as looking for coincident neutrinos, we are also interested in electromagnetic observations (gamma-ray, X-ray, optical, infra-red or radio). We had a large group of observers interesting in following up on gravitational wave triggers, and 25 teams have reported observations. This companion describes the procedure for follow-up observations and discusses sky localisation.

This work split into a main article and a supplement which goes into more technical details.

More details: The Electromagnetic Follow-up Paper summary

The Discovery Paper

Synopsis: Discovery Paper
Read this if: You want an overview of The Event
Favourite part: The entire conclusion:

The LIGO detectors have observed gravitational waves from the merger of two stellar-mass black holes. The detected waveform matches the predictions of general relativity for the inspiral and merger of a pair of black holes and the ringdown of the resulting single black hole. These observations demonstrate the existence of binary stellar-mass black hole systems. This is the first direct detection of gravitational waves and the first observation of a binary black hole merger.

The Discovery Paper gives the key science results and is remarkably well written. It seems a shame to summarise it: you should read it for yourself! (It’s free).

The Detector Paper

Synopsis: Detector Paper
Read this if: You want a brief description of the detector configuration for O1
Favourite part: It’s short!

The LIGO detectors contain lots of cool pieces of physics. This paper briefly outlines them all: the mirror suspensions, the vacuum (the LIGO arms are the largest vacuum envelopes in the world and some of the cleanest), the mirror coatings, the laser optics and the control systems. A full description is given in the Advanced LIGO paper, but the specs there are for design sensitivity (it is also heavy reading). The main difference between the current configuration and that for design sensitivity is the laser power. Currently the circulating power in the arms is 100~\mathrm{kW}, the plan is to go up to 750~\mathrm{kW}. This will reduce shot noise, but raises all sorts of control issues, such as how to avoid parametric instabilities.

Noise curves

The noise amplitude spectral density. The curves for the current observations are shown in red (dark for Hanford, light for Livingston). This is around a factor 3 better than in the final run of initial LIGO (green), but still a factor of 3 off design sensitivity (dark blue). The light blue curve shows the impact of potential future upgrades. The improvement at low frequencies is especially useful for high-mass systems like GW150914. Part of Fig. 1 of the Detector Paper.

The Compact Binary Coalescence Paper

Synopsis: Compact Binary Coalescence Paper
Read this if: You are interested in detection significance or in LVT151012
Favourite part: We might have found a second binary black hole merger

There are two compact binary coalescence searches that look for binary black holes: PyCBC and GstLAL. Both match templates to the data from the detectors to look for anything binary like, they then calculate the probability that such a match would happen by chance due to a random noise fluctuation (the false alarm probability or p-value [unhappy bonus note]). The false alarm probability isn’t the probability that there is a gravitational wave, but gives a good indication of how surprised we should be to find this signal if there wasn’t one. Here we report the results of both pipelines on the first 38.6 days of data (about 17 days where both detectors were working at the same time).

Both searches use the same set of templates to look for binary black holes [bonus note]. They look for where the same template matches the data from both detectors within a time interval consistent with the travel time between the two. However, the two searches rank candidate events and calculate false alarm probabilities using different methods. Basically, both searches use a detection statistic (the quantity used to rank candidates: higher means less likely to be noise), that is based on the signal-to-noise ratio (how loud the signal is) and a goodness-of-fit statistic. They assess the significance of a particular value of this detection statistic by calculating how frequently this would be obtained if there was just random noise (this is done by comparing data from the two detectors when there is not a coincident trigger in both). Consistency between the two searches gives us greater confidence in the results.

PyCBC’s detection statistic is a reweighted signal-to-noise ratio \hat{\rho}_c which takes into account the consistency of the signal in different frequency bands. You can get a large signal-to-noise ratio from a loud glitch, but this doesn’t match the template across a range of frequencies, which is why this test is useful. The consistency is quantified by a reduced chi-squared statistic. This is used, depending on its value, to weight the signal-to-noise ratio. When it is large (indicating inconsistency across frequency bins), the reweighted signal-to-noise ratio becomes smaller.

To calculate the background, PyCBC uses time slides. Data from the two detectors are shifted in time so that any coincidences can’t be due to a real gravitational wave. Seeing how often you get something signal-like then tells you how often you’d expect this to happen due to random noise.

GstLAL calculates the signal-to-noise ratio and a residual after subtracting the template. As a detection statistic, it uses a likelihood ratio \mathcal{L}: the probability of finding the particular values of the signal-to-noise ratio and residual in both detectors for signals (assuming signal sources are uniformly distributed isotropically in space), divided by the probability of finding them for noise.

The background from GstLAL is worked out by looking at the likeliood ratio fro triggers that only appear in one detector. Since there’s no coincident signal in the other, these triggers can’t correspond to a real gravitational wave. Looking at their distribution tells you how frequently such things happen due to noise, and hence how probable it is for both detectors to see something signal-like at the same time.

The results of the searches are shown in the figure below.

Search results for GW150914

Search results for PyCBC (left) and GstLAL (right). The histograms show the number of candidate events (orange squares) compare to the background. The black line includes GW150914 in the background estimate, the purple removes it (assuming that it is a signal). The further an orange square is above the lines, the more significant it is. Particle physicists like to quote significance in terms of \sigma and for some reason we’ve copied them. The second most significant event (around 2\sigma) is LVT151012. Fig. 7 from the Compact Binary Coalescence Paper.

GW150914 is the most significant event in both searches (it is the most significant PyCBC event even considering just single-detector triggers). They both find GW150914 with the same template values. The significance is literally off the charts. PyCBC can only calculate an upper bound on the false alarm probability of < 2 \times 10^{-7}. GstLAL calculates a false alarm probability of 1.4 \times 10^{-11}, but this is reaching the level that we have to worry about the accuracy of assumptions that go into this (that the distribution of noise triggers in uniform across templates—if this is not the case, the false alarm probability could be about 10^3 times larger). Therefore, for our overall result, we stick to the upper bound, which is consistent with both searches. The false alarm probability is so tiny, I don’t think anyone doubts this signal is real.

There is a second event that pops up above the background. This is LVT151012. It is found by both searches. Its signal-to-noise ratio is 9.6, compared with GW150914’s 24, so it is quiet. The false alarm probability from PyCBC is 0.02, and from GstLAL is 0.05, consistent with what we would expect for such a signal. LVT151012 does not reach the standards we would like to claim a detection, but it is still interesting.

Running parameter estimation on LVT151012, as we did for GW150914, gives beautiful results. If it is astrophysical in origin, it is another binary black hole merger. The component masses are lower, m_1^\mathrm{source} = 23^{+18}_{-5} M_\odot and m_2^\mathrm{source} 13^{+4}_{-5} M_\odot (the asymmetric uncertainties come from imposing m_1^\mathrm{source} \geq m_2^\mathrm{source}); the chirp mass is \mathcal{M} = 15^{+1}_{-1} M_\odot. The effective spin, as for GW150914, is close to zero \chi_\mathrm{eff} = 0.0^{+0.3}_{-0.2}. The luminosity distance is D_\mathrm{L} = 1100^{+500}_{-500}~\mathrm{Mpc}, meaning it is about twice as far away as GW150914’s source. I hope we’ll write more about this event in the future; there are some more details in the Rates Paper.

Trust LIGO

Is it random noise or is it a gravitational wave? LVT151012 remains a mystery. This candidate event is discussed in the Compact Binary Coalescence Paper (where it is found), the Rates Paper (which calculates the probability that it is extraterrestrial in origin), and the Detector Characterisation Paper (where known environmental sources fail to explain it).

The Parameter Estimation Paper

Synopsis: Parameter Estimation Paper
Read this if: You want to know the properties of GW150914’s source
Favourite part: We inferred the properties of black holes using measurements of spacetime itself!

The gravitational wave signal encodes all sorts of information about its source. Here, we explain how we extract this information  to produce probability distributions for the source parameters. I wrote about the properties of GW150914 in my previous post, so here I’ll go into a few more technical details.

To measure parameters we match a template waveform to the data from the two instruments. The better the fit, the more likely it is that the source had the particular parameters which were used to generate that particular template. Changing different parameters has different effects on the waveform (for example, changing the distance changes the amplitude, while changing the relative arrival times changes the sky position), so we often talk about different pieces of the waveform containing different pieces of information, even though we fit the whole lot at once.

Waveform explained

The shape of the gravitational wave encodes the properties of the source. This information is what lets us infer parameters. The example signal is GW150914. I made this explainer with Ban Farr and Nutsinee Kijbunchoo for the LIGO Magazine.

The waveform for a binary black hole merger has three fuzzily defined parts: the inspiral (where the two black holes orbit each other), the merger (where the black holes plunge together and form a single black hole) and ringdown (where the final black hole relaxes to its final state). Having waveforms which include all of these stages is a fairly recent development, and we’re still working on efficient ways of including all the effects of the spin of the initial black holes.

We currently have two favourite binary black hole waveforms for parameter estimation:

  • The first we refer to as EOBNR, short for its proper name of SEOBNRv2_ROM_DoubleSpin. This is constructed by using some cunning analytic techniques to calculate the dynamics (known as effective-one-body or EOB) and tuning the results to match numerical relativity (NR) simulations. This waveform only includes the effects of spins aligned with the orbital angular momentum of the binary, so it doesn’t allow us to measure the effects of precession (wobbling around caused by the spins).
  • The second we refer to as IMRPhenom, short for IMRPhenomPv2. This is constructed by fitting to the frequency dependence of EOB and NR waveforms. The dominant effects of precession of included by twisting up the waveform.

We’re currently working on results using a waveform that includes the full effects of spin, but that is extremely slow (it’s about half done now), so those results won’t be out for a while.

The results from the two waveforms agree really well, even though they’ve been created by different teams using different pieces of physics. This was a huge relief when I was first making a comparison of results! (We had been worried about systematic errors from waveform modelling). The consistency of results is partly because our models have improved and partly because the properties of the source are such that the remaining differences aren’t important. We’re quite confident that we’ve most of the parameters are reliably measured!

The component masses are the most important factor for controlling the evolution of the waveform, but we don’t measure the two masses independently.  The evolution of the inspiral is dominated by a combination called the chirp mass, and the merger and ringdown are dominated by the total mass. For lighter mass systems, where we gets lots of inspiral, we measure the chirp mass really well, and for high mass systems, where the merger and ringdown are the loudest parts, we measure the total mass. GW150914 is somewhere in the middle. The probability distribution for the masses are shown below: we can compensate for one of the component masses being smaller if we make the other larger, as this keeps chirp mass and total mass about the same.

Binary black hole masses

Estimated masses for the two black holes in the binary. Results are shown for the EOBNR waveform and the IMRPhenom: both agree well. The Overall results come from averaging the two. The dotted lines mark the edge of our 90% probability intervals. The sharp diagonal line cut-off in the two-dimensional plot is a consequence of requiring m_1^\mathrm{source} \geq m_2^\mathrm{source}.  Fig. 1 from the Parameter Estimation Paper.

To work out these masses, we need to take into account the expansion of the Universe. As the Universe expands, it stretches the wavelength of the gravitational waves. The same happens to light: visible light becomes redder, so the phenomenon is known as redshifting (even for gravitational waves). If you don’t take this into account, the masses you measure are too large. To work out how much redshift there is you need to know the distance to the source. The probability distribution for the distance is shown below, we plot the distance together with the inclination, since both of these affect the amplitude of the waves (the source is quietest when we look at it edge-on from the side, and loudest when seen face-on/off from above/below).

Distance and inclination

Estimated luminosity distance and binary inclination angle. An inclination of \theta_{JN} = 90^\circ means we are looking at the binary (approximately) edge-on. Results are shown for the EOBNR waveform and the IMRPhenom: both agree well. The Overall results come from averaging the two. The dotted lines mark the edge of our 90% probability intervals.  Fig. 2 from the Parameter Estimation Paper.

After the masses, the most important properties for the evolution of the binary are the spins. We don’t measure these too well, but the probability distribution for their magnitudes and orientations from the precessing IMRPhenom model are shown below. Both waveform models agree that the effective spin \chi_\mathrm{eff}, which is a combination of both spins in the direction of the orbital angular momentum) is small. Therefore, either the spins are small or are larger but not aligned (or antialigned) with the orbital angular momentum. The spin of the more massive black hole is the better measured of the two.

Orientation and magnitudes of the two spins

Estimated orientation and magnitude of the two component spins from the precessing IMRPhenom model. The magnitude is between 0 and 1 and is perfectly aligned with the orbital angular momentum if the angle is 0. The distribution for the more massive black hole is on the left, and for the smaller black hole on the right. Part of Fig. 5 from the Parameter Estimation Paper.

The Testing General Relativity Paper

Synopsis: Testing General Relativity Paper
Read this if: You want to know more about the nature of gravity.
Favourite part: Einstein was right! (Or more correctly, we can’t prove he was wrong… yet)

The Testing General Relativity Paper is one of my favourites as it packs a lot of science in. Our first direct detection of gravitational waves and of the merger of two black holes provides a new laboratory to test gravity, and this paper runs through the results of the first few experiments.

Before we start making any claims about general relativity being wrong, we first have to check if there’s any weird noise present. You don’t want to have to rewrite the textbooks just because of an instrumental artifact. After taking out a good guess for the waveform (as predicted by general relativity), we find that the residuals do match what we expect for instrumental noise, so we’re good to continue.

I’ve written about a couple of tests of general relativity in my previous post: the consistency of the inspiral and merger–ringdown parts of the waveform, and the bounds on the mass of the graviton (from evolution of the signal). I’ll cover the others now.

The final part of the signal, where the black hole settles down to its final state (the ringdown), is the place to look to check that the object is a black hole and not some other type of mysterious dark and dense object. It is tricky to measure this part of the signal, but we don’t see anything odd. We can’t yet confirm that the object has all the properties you’d want to pin down that it is exactly a black hole as predicted by general relativity; we’re going to have to wait for a louder signal for this. This test is especially poignant, as Steven Detweiler, who pioneered a lot of the work calculating the ringdown of black holes, died a week before the announcement.

We can allow terms in our waveform (here based on the IMRPhenom model) to vary and see which values best fir the signal. If there is evidence for differences compared with the predictions from general relativity, we would have evidence for needing an alternative. Results for this analysis are shown below for a set of different waveform parameters \hat{p}_i: the \varphi_i parameters determine the inspiral, the \alpha_i parameters determine the merger–ringdown and the \beta_i parameters cover the intermediate regime. If the deviation \delta \hat{p}_i is zero, the value coincides with the value from general relativity. The plot shows what would happen if you allow all the variable to vary at once (the multiple results) and if you tried just that parameter on its own (the single results).

Testing general relativity bounds

Probability distributions for waveform parameters. The single analysis only varies one parameter, the multiple analysis varies all of them, and the J0737-3039 result is the existing bound from the double pulsar. A deviation of zero is consistent with general relativity. Fig. 7 from the Testing General Relativity Paper.

Overall the results look good. Some of the single results are centred away from zero, but we think that this is just a random fluctuate caused by noise (we’ve seen similar behaviour in tests, so don’t panic yet). It’s not surprising the \varphi_3, \varphi_4 and \varphi_{5l} all show this behaviour, as they are sensitive to similar noise features. These measurements are much tighter than from any test we’ve done before, except for the measurement of \varphi_0 which is better measured from the double pulsar (since we have lots and lots of orbits of that measured).

The final test is to look for additional polarizations of gravitational waves. These are predicted in several alternative theories of gravity. Unfortunately, because we only have two detectors which are pretty much aligned we can’t say much, at least without knowing for certain the location of the source. Extra detectors will be useful here!

In conclusion, we have found no evidence to suggest we need to throw away general relativity, but future events will help us to perform new and stronger tests.

The Rates Paper

Synopsis: Rates Paper
Read this if: You want to know how often binary black holes merge (and how many we’ll detect)
Favourite part: There’s a good chance we’ll have ten detections by the end of our second observing run (O2)

Before September 14, we had never seen a binary stellar-mass black hole system. We were therefore rather uncertain about how many we would see. We had predictions based on simulations of the evolution of stars and their dynamical interactions. These said we shouldn’t be too surprised if we saw something in O1, but that we shouldn’t be surprised if we didn’t see anything for many years either. We weren’t really expecting to see a black hole system so soon (the smart money was on a binary neutron star). However, we did find a binary black hole, and this happened right at the start of our observations! What do we now believe about the rate of mergers?

To work out the rate, you first need to count the number of events you have detected and then work out how sensitive you are to the population of signals (how many could you see out of the total).

Counting detections sounds simple: we have GW150914 without a doubt. However, what about all the quieter signals? If you have 100 events each with a 1% probability of being real, then even though you can’t say with certainty that anyone is an actual signal, you would expect one to be so. We want to work out how many events are real and how many are due to noise. Handily, trying to tell apart different populations of things when you’re not certain about individual members is a common problem is astrophysics (where it’s often difficult to go and check what something actually is), so there exists a probabilistic framework for doing this.

Using the expected number of real and noise events for a given detection statistic (as described in the Compact Binary Coalescence Paper), we count the number of detections and as a bonus, get a probability that each event is of astrophysical origin. There are two events with more than a 50% chance of being real: GW150914, where the probability is close to 100%, and LVT151012, where to probability is 84% based on GstLAL and 91% based on PyCBC.

By injecting lots of fake signals into some data and running our detection pipelines, we can work out how sensitive they are (in effect, how far away can they find particular types of sources). For a given number of detections, the more sensitive we are, the lower the actual rate of mergers should be (for lower sensitivity we would miss more, while there’s no hiding for higher sensitivity).

There is one final difficulty in working out the total number of binary black hole mergers: we need to know the distribution of masses, because our sensitivity depends on this. However, we don’t yet know this as we’ve only seen GW150914 and (maybe) LVT151012. Therefore, we try three possibilities to get an idea of what the merger rate could be.

  1. We assume that binary black holes are either like GW150914 or like LVT151012. Given that these are our only possible detections at the moment, this should give a reasonable estimate. A similar approach has been used for estimating the population of binary neutron stars from pulsar observations [bonus note].
  2. We assume that the distribution of masses is flat in the logarithm of the masses. This probably gives more heavy black holes than in reality (and so a lower merger rate)
  3. We assume that black holes follow a power law like the initial masses of stars. This probably gives too many low mass black holes (and so a higher merger rate)

The estimated merger rates (number of binary black hole mergers per volume per time) are then: 1. 83^{+168}_{-63}~\mathrm{Gpc^{-3}\,yr^{-1}}; 2. 61^{+124}_{-48}~\mathrm{Gpc^{-3}\,yr^{-1}}, and 3. 200^{+400}_{-160}~\mathrm{Gpc^{-3}\,yr^{-1}}. There is a huge scatter, but the flat and power-law rates hopefully bound the true value.

We’ll pin down the rate better after a few more detections. How many more should we expect to see? Using the projected sensitivity of the detectors over our coming observing runs, we can work out the probability of making N more detections. This is shown in the plot below. It looks like there’s about about a 10% chance of not seeing anything else in O1, but we’re confident that we’ll have 10 more by the end of O2, and 35 more by the end of O3! I may need to lie down…

Expected number of detections

The percentage chance of making 0, 10, 35 and 70 more detections of binary black holes as time goes on and detector sensitivity improves (based upon our data so far). This is a simplified version of part of Fig. 3 of the Rates Paper taken from the science summary.

The Burst Paper

Synopsis: Burst Paper
Read this if: You want to check what we can do without a waveform template
Favourite part: You don’t need a template to make a detection

When discussing what we can learn from gravitational wave astronomy, you can almost guarantee that someone will say something about discovering the unexpected. Whenever we’ve looked at the sky in a new band of the electromagnetic spectrum, we found something we weren’t looking for: pulsars for radio, gamma-ray burst for gamma-rays, etc. Can we do the same in gravitational wave astronomy? There may well be signals we weren’t anticipating out there, but will we be able to detect them? The burst pipelines have our back here, at least for short signals.

The burst search pipelines, like their compact binary coalescence partners, assign candidate events a detection statistic and then work out a probability associated with being a false alarm caused by noise. The difference is that the burst pipelines try to find a wider range of signals.

There are three burst pipelines described: coherent WaveBurst (cWB), which famously first found GW150914; omicron–LALInferenceBurst (oLIB), and BayesWave, which follows up on cWB triggers.

As you might guess from the name, cWB looks for a coherent signal in both detectors. It looks for excess power (indicating a signal) in a time–frequency plot, and then classifies candidates based upon their structure. There’s one class for blip glitches and resonance lines (see the Detector Characterisation Paper), these are all thrown away as noise; one class for chirp-like signals that increase in frequency with time, this is where GW150914 was found, and one class for everything else. cWB’s detection statistic \eta_c is something like a signal-to-noise ratio constructed based upon the correlated power in the detectors. The value for GW150914 was \eta_c = 20, which is higher than for any other candidate. The false alarm probability (or p-value), folding in all three search classes, is 2\times 10^{-6}, which is pretty tiny, even if not as significant as for the tailored compact binary searches.

The oLIB search has two stages. First it makes a time–frequency plot and looks for power coincident between the two detectors. Likely candidates are then followed up by matching a sine–Gaussian wavelet to the data, using a similar algorithm to the one used for parameter estimation. It’s detection statistic is something like a likelihood ratio for the signal verses noise. It calculates a false alarm probability of about 2\times 10^{-6} too.

BayesWave fits a variable number of sine–Gaussian wavelets to the data. This can model both a signal (when the wavelets are the same for both detectors) and glitches (when the wavelets are independent). This is really clever, but is too computationally expensive to be left running on all the data. Therefore, it follows up on things highlighted by cWB, potentially increasing their significance. It’s detection statistic is the Bayes factor comparing the signal and glitch models. It estimates the false alarm probability to be about 7 \times 10^{-7} (which agrees with the cWB estimate if you only consider chirp-like triggers).

None of the searches find LVT151012. However, as this is a quiet, lower mass binary black hole, I think that this is not necessarily surprising.

cWB and BayesWave also output a reconstruction of the waveform. Reassuringly, this does look like binary black hole coalescence!

Estimated waveforms from different models

Gravitational waveforms from our analyses of GW150914. The wiggly grey line are the data from Hanford (top) and Livinston (bottom); these are analysed coherently. The plots show waveforms whitened by the noise power spectral density. The dark band shows the waveform reconstructed by BayesWave without assuming that the signal is from a binary black hole (BBH). The light bands show the distribution of BBH template waveforms that were found to be most probable from our parameter-estimation analysis. The two techniques give consistent results: the match between the two models is 94^{+2}_{-3}\%. Fig. 6 of the Parameter Estimation Paper.

The paper concludes by performing some simple fits to the reconstructed waveforms. For this, you do have to assume that the signal cane from a binary black hole. They find parameters roughly consistent with those from the full parameter-estimation analysis, which is a nice sanity check of our results.

The Detector Characterisation Paper

Synopsis: Detector Characteristation Paper
Read this if: You’re curious if something other than a gravitational wave could be responsible for GW150914 or LVT151012
Favourite part: Mega lightning bolts can cause correlated noise

The output from the detectors that we analyses for signals is simple. It is a single channel that records the strain. To monitor instrumental behaviour and environmental conditions the detector characterisation team record over 200,000 other channels. These measure everything from the alignment of the optics through ground motion to incidence of cosmic rays. Most of the data taken by LIGO is to monitor things which are not gravitational waves.

This paper examines all the potential sources of noise in the LIGO detectors, how we monitor them to ensure they are not confused for a signal, and the impact they could have on estimating the significance of events in our searches. It is amazingly thorough work.

There are lots of potential noise sources for LIGO. Uncorrelated noise sources happen independently at both sites, therefore they can only be mistaken for a gravitational wave if by chance two occur at the right time. Correlated noise sources effect both detectors, and so could be more confusing for our searches, although there’s no guarantee that they would cause a disturbance that looks anything like a binary black hole merger.

Sources of uncorrelated noise include:

  • Ground motion caused by earthquakes or ocean waves. These create wibbling which can affect the instruments, even though they are well isolated. This is usually at low frequencies (below 0.1~\mathrm{Hz} for earthquakes, although it can be higher if the epicentre is near), unless there is motion in the optics around (which can couple to cause higher frequency noise). There is a network of seismometers to measure earthquakes at both sites. There where two magnitude 2.1 earthquakes within 20 minutes of GW150914 (one off the coast of Alaska, the other south-west of Seattle), but both produced ground motion that is ten times too small to impact the detectors. There was some low frequency noise in Livingston at the time of LVT151012 which is associated with a period of bad ocean waves. however, there is no evidence that these could be converted to the frequency range associated with the signal.
  • People moving around near the detectors can also cause vibrational or acoustic disturbances. People are kept away from the detectors while they are running and accelerometers, microphones and seismometers monitor the environment.
  • Modulation of the lasers at 9~\mathrm{MHz} and 45~\mathrm{MHz} is done to monitor and control several parts of the optics. There is a fault somewhere in the system which means that there is a coupling to the output channel and we get noise across 10~\mathrm{Hz} to 2~\mathrm{kHz}, which is where we look for compact binary coalescences. Rai Weiss suggested shutting down the instruments to fix the source of this and delaying the start of observations—it’s a good job we didn’t. Periods of data where this fault occurs are flagged and not included in the analysis.
  • Blip transients are a short glitch that occurs for unknown reasons. They’re quite mysterious. They are at the right frequency range (30~\mathrm{Hz} to 250~\mathrm{Hz}) to be confused with binary black holes, but don’t have the right frequency evolution. They contribute to the background of noise triggers in the compact binary coalescence searches, but are unlikely to be the cause of GW150914 or LVT151012 since they don’t have the characteristic chirp shape.

    Normalised spectrogram of a blip transient.

    A time–frequency plot of a blip glitch in LIGO-Livingston. Blip glitches are the right frequency range to be confused with binary coalescences, but don’t have the chirp-like structure. Blips are symmetric in time, whereas binary coalescences sweep up in frequency. Fig. 3 of the Detector Characterisation Paper.

Correlated noise can be caused by:

  • Electromagnetic signals which can come from lightning, solar weather or radio communications. This is measured by radio receivers and magnetometers, and its extremely difficult to produce a signal that is strong enough to have any impact of the detectors’ output. There was one strong  (peak current of about 500~\mathrm{kA}) lightning strike in the same second as GW150914 over Burkino Faso. However, the magnetic disturbances were at least a thousand times too small to explain the amplitude of GW150914.
  • Cosmic ray showers can cause electromagnetic radiation and particle showers. The particle flux become negligible after a few kilometres, so it’s unlikely that both Livingston and Hanford would be affected, but just in case there is a cosmic ray detector at Hanford. It has seen nothing suspicious.

All the monitoring channels give us a lot of insight into the behaviour of the instruments. Times which can be identified as having especially bad noise properties (where the noise could influence the measured output), or where the detectors are not working properly, are flagged and not included in the search analyses. Applying these vetoes mean that we can’t claim a detection when we know something else could mimic a gravitational wave signal, but it also helps us clean up our background of noise triggers. This has the impact of increasing the significance of the triggers which remain (since there are fewer false alarms they could be confused with). For example, if we leave the bad period in, the PyCBC false alarm probability for LVT151012 goes up from 0.02 to 0.14. The significance of GW150914 is so great that we don’t really need to worry about the effects of vetoes.

At the time of GW150914 the detectors were running well, the data around the event are clean, and there is nothing in any of the auxiliary channels that record anything which could have caused the event. The only source of a correlated signal which has not been rules out is a gravitational wave from a binary black hole merger. The time–frequency plots of the measured strains are shown below, and its easy to pick out the chirps.

Normalised spectrograms for GW150914

Time–frequency plots for GW150914 as measured by Hanford (left) and Livingston (right). These show the characteristic increase in frequency with time of the chirp of a binary merger. The signal is clearly visible above the noise. Fig. 10 of the Detector Characterisation Paper.

The data around LVT151012 are significantly less stationary than around GW150914. There was an elevated noise transient rate around this time. This is probably due to extra ground motion caused by ocean waves. This low frequency noise is clearly visible in the Livingston time–frequency plot below. There is no evidence that this gets converted to higher frequencies though. None of the detector characterisation results suggest that LVT151012 has was caused by a noise artifact.

Normalised spectrograms for LVT151012

Time–frequency plots for LVT151012 as measured by Hanford (left) and Livingston (right). You can see the characteristic increase in frequency with time of the chirp of a binary merger, but this is mixed in with noise. The scale is reduced compared with for GW150914, which is why noise features appear more prominent. The band at low frequency in Livingston is due to ground motion; this is not present in Hanford. Fig. 13 of the Detector Characterisation Paper.

If you’re curious about the state of the LIGO sites and their array of sensors, you can see more about the physical environment monitors at pem.ligo.org.

The Calibration Paper

Synopsis: Calibration Paper
Read this if: You like control engineering or precision measurement
Favourite part: Not only are the LIGO detectors sensitive enough to feel the push from a beam of light, they are so sensitive that you have to worry about where on the mirrors you push

We want to measure the gravitational wave strain—the change in length across our detectors caused by a passing gravitational wave. What we actually record is the intensity of laser light out the output of our interferometer. (The output should be dark when the strain is zero, and the intensity increases when the interferometer is stretched or squashed). We need a way to convert intensity to strain, and this requires careful calibration of the instruments.

The calibration is complicated by the control systems. The LIGO instruments are incredibly sensitive, and maintaining them in a stable condition requires lots of feedback systems. These can impact how the strain is transduced into the signal readout by the interferometer. A schematic of how what would be the change in the length of the arms without control systems \Delta L_\mathrm{free} is changed into the measured strain h is shown below. The calibration pipeline build models to correct for the effects of the control system to provide an accurate model of the true gravitational wave strain.

Calibration control system schematic

Model for how a differential arm length caused by a gravitational wave \Delta L_\mathrm{free} or a photon calibration signal x_\mathrm{T}^\mathrm{(PC)} is converted into the measured signal h. Fig. 2 from the Calibration Paper.

To measure the different responses of the system, the calibration team make several careful measurements. The primary means is using photon calibration: an auxiliary laser is used to push the mirrors and the response is measured. The spots where the lasers are pointed are carefully chosen to minimise distortion to the mirrors caused by pushing on them. A secondary means is to use actuators which are parts of the suspension system to excite the system.

As a cross-check, we can also use two auxiliary green lasers to measure changes in length using either a frequency modulation or their wavelength. These are similar approaches to those used in initial LIGO. These go give consistent results with the other methods, but they are not as accurate.

Overall, the uncertainty in the calibration of the amplitude of the strain is less than 10\% between 20~\mathrm{Hz} and 1~\mathrm{kHz}, and the uncertainty in phase calibration is less than 10^\circ. These are the values that we use in our parameter-estimation runs. However, the calibration uncertainty actually varies as a function of frequency, with some ranges having much less uncertainty. We’re currently working on implementing a better model for the uncertainty, which may improve our measurements. Fortunately the masses, aren’t too affected by the calibration uncertainty, but sky localization is, so we might get some gain here. We’ll hopefully produce results with updated calibration in the near future.

The Astrophysics Paper

Synopsis: Astrophysics Paper
Read this if: You are interested in how binary black holes form
Favourite part: We might be able to see similar mass binary black holes with eLISA before they merge in the LIGO band [bonus note]

This paper puts our observations of GW150914 in context with regards to existing observations of stellar-mass black holes and theoretical models for binary black hole mergers. Although it doesn’t explicitly mention LVT151012, most of the conclusions would be just as applicable to it’s source, if it is real. I expect there will be rapid development of the field now, but if you want to catch up on some background reading, this paper is the place to start.

The paper contains lots of references to good papers to delve into. It also highlights the main conclusion we can draw in italics, so its easy to skim through if you want a summary. I discussed the main astrophysical conclusions in my previous post. We will know more about binary black holes and their formation when we get more observations, so I think it is a good time to get interested in this area.

The Stochastic Paper

Synopsis: Stochastic Paper
Read this if: You like stochastic backgrounds
Favourite part: We might detect a background in the next decade

A stochastic gravitational wave background could be created by an incoherent superposition of many signals. In pulsar timing, they are looking for a background from many merging supermassive black holes. Could we have a similar thing from stellar-mass black holes? The loudest signals, like GW150914, are resolvable, they stand out from the background. However, for every loud signal, there will be many quiet signals, and the ones below our detection threshold could form a background. Since we’ve found that binary black hole mergers are probably plentiful, the background may be at the high end of previous predictions.

The background from stellar-mass black holes is different than the one from supermassive black holes because the signals are short. While the supermassive black holes produce an almost constant hum throughout your observations, stellar-mass black hole mergers produce short chirps. Instead of having lots of signals that overlap in time, we have a popcorn background, with one arriving on average every 15 minutes. This might allow us to do some different things when it comes to detection, but for now, we just use the standard approach.

This paper calculates the energy density of gravitational waves from binary black holes, excluding the contribution from signals loud enough to be detected. This is done for several different models. The standard (fiducial) model assumes parameters broadly consistent with those of GW150914’s source, plus a particular model for the formation of merging binaries. There are then variations on the the model for formation, considering different time delays between formation and merger, and adding in lower mass systems consistent with LVT151012. All these models are rather crude, but give an idea of potential variations in the background. Hopefully more realistic distributions will be considered in the future. There is some change between models, but this is within the (considerable) statistical uncertainty, so predictions seems robust.

Models for a binary black hole stochastic background

Different models for the stochastic background of binary black holes. This is plotted in terms of energy density. The red band indicates the uncertainty on the fiducial model. The dashed line indicates the sensitivity of the LIGO and Virgo detectors after several years at design sensitivity. Fig. 2 of the Stochastic Paper.

After a couple of years at design sensitivity we may be able to make a confident detection of the stochastic background. The background from binary black holes is more significant than we expected.

If you’re wondering about if we could see other types of backgrounds, such as one of cosmological origin, then the background due to binary black holes could make detection more difficult. In effect, it acts as another source of noise, masking the other background. However, we may be able to distinguish the different backgrounds by measuring their frequency dependencies (we expect them to have different slopes), if they are loud enough.

The Neutrino Paper

Synopsis: Neutrino Paper
Read this if: You really like high energy neutrinos
Favourite part: We’re doing astronomy with neutrinos and gravitational waves—this is multimessenger astronomy without any form of electromagnetic radiation

There are multiple detectors that can look for high energy neutrinos. Currently, LIGO–Virgo Observations are being followed up by searches from ANTARES and IceCube. Both of these are Cherenkov detectors: they look for flashes of light created by fast moving particles, not the neutrinos themselves, but things they’ve interacted with. ANTARES searches the waters of the Mediterranean while IceCube uses the ice of Antarctica.

Within 500 seconds either side of the time of GW150914, ANTARES found no neutrinos and IceCube found three. These results are consistent with background levels (you would expect on average less than one and 4.4 neutrinos over that time from the two respectively). Additionally, none of the IceCube neutrinos are consistent with the sky localization of GW150914 (even though the sky area is pretty big). There is no sign of a neutrino counterpart, which is what we were expecting.

Subsequent non-detections have been reported by KamLAND, the Pierre Auger Observatory and Super-Kamiokande.

The Electromagnetic Follow-up Paper

Synopsis: Electromagnetic Follow-up Paper
Read this if: You are interested in the search for electromagnetic counterparts
Favourite part: So many people were involved in this work that not only do we have to abbreviate the list of authors (Abbott, B.P. et al.), but we should probably abbreviate the list of collaborations too (LIGO Scientific & Virgo Collaboration et al.)

This is the last of the set of companion papers to be released—it took a huge amount of coordinating because of all the teams involved. The paper describes how we released information about GW150914. This should not be typical of how we will do things going forward (i) because we didn’t have all the infrastructure in place on September 14 and (ii) because it was the first time we had something we thought was real.

The first announcement was sent out on September 16, and this contained sky maps from the Burst codes cWB and LIB. In the future, we should be able to send out automated alerts with a few minutes latency.

For the first alert, we didn’t have any results which assumed the the source was a binary, as the searches which issue triggers at low latency were only looking for lower mass systems which would contain a neutron star. I suspect we’ll be reprioritising things going forward. The first information we shared about the potential masses for the source was shared on October 3. Since this was the first detection, everyone was cautious about triple-checking results, which caused the delay. Revised false alarm rates including results from GstLAL and PyCBC were sent out October 20.

The final sky maps were shared January 13. This is when we’d about finished our own reviews and knew that we would be submitting the papers soon [bonus note]. Our best sky map is the one from the Parameter Estimation Paper. You might it expect to be more con straining than the results from the burst pipelines since it uses a proper model for the gravitational waves from a binary black hole. This is the case if we ignore calibration uncertainty (which is not yet included in the burst codes), then the 50% area is 48~\mathrm{deg}^2 and the 90% area is 150~\mathrm{deg^2}. However, including calibration uncertainty, the sky areas are 150~\mathrm{deg^2} and 590~\mathrm{deg^2} at 50% and 90% probability respectively. Calibration uncertainty has the largest effect on sky area. All the sky maps agree that the source is in in some region of the annulus set by the time delay between the two detectors.

Sky map

The different sky maps for GW150914 in an orthographic projection. The contours show the 90% region for each algorithm. The faint circles show lines of constant time delay \Delta t_\mathrm{HL} between the two detectors. BAYESTAR rapidly computes sky maps for binary coalescences, but it needs the output of one of the detection pipelines to run, and so was not available at low latency. The LALInference map is our best result. All the sky maps are available as part of the data release. Fig. 2 of the Electromagnetic Follow-up Paper.

A timeline of events is shown below. There were follow-up observations across the electromagnetic spectrum from gamma-rays and X-rays through the optical and near infra-red to radio.

EM follow-up timeline

Timeline for observations of GW15014. The top (grey) band shows information about gravitational waves. The second (blue) band shows high-energy (gamma- and X-ray) observations. The third and fourth (green) bands show optical and near infra-red observations respectively. The bottom (red) band shows radio observations. Fig. 1 from the Electromagnetic Follow-up Paper.

Observations have been reported (via GCN notices) by

Together they cover an impressive amount of the sky as shown below. Many targeted the Large Magellanic Cloud before the knew the source was a binary black hole.

Follow-up observations

Footprints of observations compared with the 50% and 90% areas of the initially distributed (cWB: thick lines; LIB: thin lines) sky maps, also in orthographic projection. The all-sky observations are not shown. The grey background is the Galactic plane. Fig. 3 of the Electromagnetic Follow-up Paper.

Additional observations have been done using archival data by XMM-Newton and AGILE.

We don’t expect any electromagnetic counterpart to a binary black hole. No-one found anything with the exception of Fermi GBM. This has found a weak signal which may be coincident. More work is required to figure out if this is genuine. It would be a surprise if it is, so most people are sceptical. However, I think this will make people more interested in following up on our next binary black hole signal!

Bonus notes

Naming The Event

GW150914 is the name we have given to the signal detected by the two LIGO instruments. The “GW” is short for gravitational wave (not galactic worm), and the numbers give the date the wave reached the detectors (2015 September 14). It was originally known as G184098, its ID in our database of candidate events (most circulars sent to and from our observer partners use this ID). That was universally agreed to be terrible to remember. We tried to think of a good nickname for the event, but failed to, so rather by default, it has informally become known as The Event within the Collaboration. I think this is fitting given its significance.

LVT151012 is the name of the most significant candidate after GW150914, it doesn’t reach our criteria to claim detection (a false alarm rate of less than once per century), which is why it’s not GW151012. The “LVT” is short for LIGO–Virgo trigger. It took a long time to settle on this and up until the final week before the announcement it was still going by G197392. Informally, it was known as The Second Monday Event, as it too was found on a Monday. You’ll have to wait for us to finish looking at the rest of the O1 data to see if the Monday trend continues. If it does, it could have serious repercussions for our understanding of Garfield.

Publishing in Physical Review Letters

Several people have asked me if the Discovery Paper was submitted to Science or Nature. It was not. The decision that any detection would be submitted to Physical Review was made ahead of the run. As far as I am aware, there was never much debate about this. Physical Review had been good about publishing all our non-detections and upper limits, so it only seemed fair that they got the discovery too. You don’t abandon your friends when you strike it rich. I am glad that we submitted to them.

Gaby González, the LIGO Spokesperson, contacted the editors of Physical Review Letters ahead of submission to let them know of the anticipated results. They then started to line up some referees to give confidential and prompt reviews.

The initial plan was to submit on January 19, and we held a Collaboration-wide tele-conference to discuss the science. There were a few more things still to do, so the paper was submitted on January 21, following another presentation (and a long discussion of whether a number should be a six or a two) and a vote. The vote was overwhelmingly in favour of submission.

We got the referee reports back on January 27, although they were circulated to the Collaboration the following day. This was a rapid turnaround! From their comments, I suspect that Referee A may be a particle physicist who has dealt with similar claims of first detection—they were most concerned about statistical significance; Referee B seemed like a relativist—they made comments about the effect of spin on measurements, knew about waveforms and even historical papers on gravitational waves, and I would guess that Referee C was an astronomer involved with pulsars—they mentioned observations of binary pulsars potentially claiming the title of first detection and were also curious about sky localization. While I can’t be certain who the referees were, I am certain that I have never had such positive reviews before! Referee A wrote

The paper is extremely well written and clear. These results are obviously going to make history.

Referee B wrote

This paper is a major breakthrough and a milestone in gravitational science. The results are overall very well presented and its suitability for publication in Physical Review Letters is beyond question.

and Referee C wrote

It is an honor to have the opportunity to review this paper. It would not be an exaggeration to say that it is the most enjoyable paper I’ve ever read. […] I unreservedly recommend the paper for publication in Physical Review Letters. I expect that it will be among the most cited PRL papers ever.

I suspect I will never have such emphatic reviews again [happy bonus note][unhappy bonus note].

Publishing in Physical Review Letters seems to have been a huge success. So much so that their servers collapsed under the demand, despite them adding two more in anticipation. In the end they had to quintuple their number of servers to keep up with demand. There were 229,000 downloads from their website in the first 24 hours. Many people remarked that it was good that the paper was freely available. However, we always make our papers public on the arXiv or via LIGO’s Document Control Center [bonus bonus note], so there should never be a case where you miss out on reading a LIGO paper!

Publishing the Parameter Estimation Paper

The reviews for the Parameter Estimation Paper were also extremely positive. Referee A, who had some careful comments on clarifying notation, wrote

This is a beautiful paper on a spectacular result.

Referee B, who commendably did some back-of-the-envelope checks, wrote

The paper is also very well written, and includes enough background that I think a decent fraction of it will be accessible to non-experts. This, together with the profound nature of the results (first direct detection of gravitational waves, first direct evidence that Kerr black holes exist, first direct evidence that binary black holes can form and merge in a Hubble time, first data on the dynamical strong-field regime of general relativity, observation of stellar mass black holes more massive than any observed to date in our galaxy), makes me recommend this paper for publication in PRL without hesitation.

Referee C, who made some suggestions to help a non-specialist reader, wrote

This is a generally excellent paper describing the properties of LIGO’s first detection.

Physical Review Letters were also kind enough to publish this paper open access without charge!

Publishing the Rates Paper

It wasn’t all clear sailing getting the companion papers published. Referees did give papers the thorough checking that they deserved. The most difficult review was of the Rates Paper. There were two referees, one astrophysics, one statistics. The astrophysics referee was happy with the results and made a few suggestions to clarify or further justify the text. The statistics referee has more serious complaints…

There are five main things which I think made the statistics referee angry. First, the referee objected to our terminology

While overall I’ve been impressed with the statistics in LIGO papers, in one respect there is truly egregious malpractice, but fortunately easy to remedy. It concerns incorrectly using the term “false alarm probability” (FAP) to refer to what statisticians call a p-value, a deliberately vague term (“false alarm rate” is similarly misused). […] There is nothing subtle or controversial about the LIGO usage being erroneous, and the practice has to stop, not just within this paper, but throughout the LIGO collaboration (and as a matter of ApJ policy).

I agree with this. What we call the false alarm probability is not the probability that the detection is a false alarm. It is not the probability that the given signal is noise rather that astrophysical, but instead it is the probability that if we only had noise that we would get a detection statistic as significant or more so. It might take a minute to realise why those are different. The former (the one we should call p-value) is what the search pipelines give us, but is less useful than the latter for actually working out if the signal is real. The probabilities calculated in the Rates Paper that the signal is astrophysical are really what you want.

p-values are often misinterpreted, but most scientists are aware of this, and so are cautious when they come across them

As a consequence of this complaint, the Collaboration is purging “false alarm probability” from our papers. It is used in most of the companion papers, as they were published before we got this report (and managed to convince everyone that it is important).

Second, we were lacking in references to existing literature

Regarding scholarship, the paper is quite poor. I take it the authors have written this paper with the expectation, or at least the hope, that it would be read […] If I sound frustrated, it’s because I am.

This is fair enough. The referee made some good suggestions to work done on inferring the rate of gamma-ray bursts by Loredo & Wasserman (Part I, Part II, Part III), as well as by Petit, Kavelaars, Gladman & Loredo on trans-Neptunian objects, and we made sure to add as much work as possible in revisions. There’s no excuse for not properly citing useful work!

Third, the referee didn’t understand how we could be certain of the distribution of signal-to-noise ratio \rho without also worrying about the distribution of parameters like the black hole masses. The signal-to-noise ratio is inversely proportional to distance, and we expect sources to be uniformly distributed in volume. Putting these together (and ignoring corrections from cosmology) gives a distribution for signal-to-noise ratio of p(\rho) \propto \rho^{-4} (Schulz 2011).  This is sufficiently well known within the gravitational-wave community that we forgot that those outside wouldn’t appreciate it without some discussion. Therefore, it was useful that the referee did point this out.

Fourth, the referee thought we had made an error in our approach. They provided an alternative derivation which

if useful, should not be used directly without some kind of attribution

Unfortunately, they were missing some terms in their expressions. When these were added in, their approach reproduced our own (I had a go at checking this myself). Given that we had annoyed the referee on so many other points, it was tricky trying to convince them of this. Most of the time spent responding to the referees was actually working on the referee response and not on the paper.

Finally, the referee was unhappy that we didn’t make all our data public so that they could check things themselves. I think it would be great, and it will happen, it was just too early at the time. Sorry folks!

LIGO Document Control Center

Papers in the LIGO Document Control Center are assigned a number starting with P (for “paper”) and then several digits. The Discover Paper’s reference is P150914. I only realised why this was the case on the day of submission.

The überbank

The set of templates used in the searches is designed to be able to catch binary neutron stars, neutron star–black hole binaries and binary neutron stars. It covers component masses from 1 to 99 solar masses, with total masses less than 100 solar masses. The upper cut off is chosen for computational convenience, rather than physical reasons: we do look for higher mass systems in a similar way, but they are easier to confuse with glitches and so we have to be more careful tuning the search. Since bank of templates is so comprehensive, it is known as the überbank. Although it could find binary neutron stars or neutron star–black hole binaries, we only discuss binary black holes here.

The template bank doesn’t cover the full parameter space, in particular it assumes that spins are aligned for the two components. This shouldn’t significantly affect its efficiency at finding signals, but gives another reason (together with the coarse placement of templates) why we need to do proper parameter estimation to measure properties of the source.

Alphabet soup

In the calculation of rates, the probabilistic means for counting sources is known as the FGMC method after its authors (who include two Birmingham colleagues and my former supervisor). The means of calculating rates assuming that the population is divided into one class to match each observation is also named for the initial of its authors as the KKL approach. The combined FGMCKKL method for estimating merger rates goes by the name alphabet soup, as that is much easier to swallow.

Multi-band gravitational wave astronomy

The prospect of detecting a binary black hole with a space-based detector and then seeing the same binary merger with ground-based detectors is especially exciting. My officemate Alberto Sesana (who’s not in LIGO) has just written a paper on the promise of multi-band gravitational wave astronomy. Black hole binaries like GW150914 could be spotted by eLISA (if you assume one of the better sensitivities for a detector with three arms). Then a few years to weeks later they merge, and spend their last moments emitting in LIGO’s band. The evolution of some binary black holes is sketched in the plot below.

Binary black hole mergers across the eLISA and LIGO frequency bands

The evolution of binary black hole mergers (shown in blue). The eLISA and Advanced LIGO sensitivity curves are shown in purple and orange respectively. As the black holes insprial, they emit gravitational waves at higher frequency, shifting from the eLISa band to the LIGO band (where they merge). The scale at the top gives the approximate time until merger. Fig. 1 of Sesana (2016).

Seeing the signal in two bands can help in several ways. First it can increase our confidence in detection, potentially picking out signals that we wouldn’t otherwise. Second, it gives us a way to verify the calibration of our instruments. Third, it lets us improve our parameter-estimation precision—eLISA would see thousands of cycles, which lets it pin down the masses to high accuracy, these results can be combined with LIGO’s measurements of the strong-field dynamics during merger to give a fantastic overall picture of the system. Finally, since eLISA can measure the signal for a considerable time, it can well localise the source, perhaps just to a square degree; since we’ll also be able to predict when the merger will happen, you can point telescopes at the right place ahead of time to look for any electromagnetic counterparts which may exist. Opening up the gravitational wave spectrum is awesome!

The LALInference sky map

One of my jobs as part of the Parameter Estimation group was to produce the sky maps from our parameter-estimation runs. This is a relatively simple job of just running our sky area code. I had done it many times while were collecting our results, so I knew that the final versions were perfectly consistent with everything else we had seen. While I was comfortable with running the code and checking the results, I was rather nervous uploading the results to our database to be shared with our observational partners. I somehow managed to upload three copies by accident. D’oh! Perhaps future historians will someday look back at the records for G184098/GW150914 and wonder what was this idiot Christopher Berry doing? Probably no-one would every notice, but I know the records are there…

Advanced LIGO detects gravitational waves!

The first observing run (O1) of Advanced LIGO was scheduled to start 9 am GMT (10 am BST), 14 September 2015. Both gravitational-wave detectors were running fine, but there were few a extra things the calibration team wanted to do and not all the automated analysis had been set up, so it was decided to postpone the start of the run until 18 September. No-one told the Universe. At 9:50 am, 14 September there was an event. To those of us in the Collaboration, it is known as The Event.

Measured strain

The Event’s signal as measured by LIGO Hanford and LIGO Livingston. The shown signal has been filtered to make it more presentable. The Hanford signal is inverted because of the relative orientations of the two interferometers. You can clearly see that both observatories see that same signal, and even without fancy analysis, that there are definitely some wibbles there! Part of Fig. 1 from the Discovery Paper.

Detection

The detectors were taking data and the coherent WaveBurst (cWB) detection pipeline was set up analysing this. It finds triggers in near real time, and so about 3 minutes after the gravitational wave reached Earth, cWB found it. I remember seeing the first few emails… and ignoring them—I was busy trying to finalise details for our default parameter-estimation runs for the start of O1. However, the emails kept on coming. And coming. Something exciting was happening. The detector scientists at the sites swung in to action and made sure that the instruments would run undisturbed so we could get lots of data about their behaviour; meanwhile, the remaining data analysis codes were set running with ruthless efficiency.

The cWB algorithm doesn’t search for a particular type of signal, instead it looks for the same thing in both detectors—it’s what we call a burst search. Burst searches could find supernova explosions, black hole mergers, or something unexpected (so long as the signal is short). Looking at the data, we saw that the frequency increased with time, there was the characteristic chirp of a binary black hole merger! This meant that the searches that specifically look for the coalescence of binaries (black hole or neutron stars) should find it too, if the signal was from a binary black hole. It also meant that we could analyse the data to measure the parameters.

Time–frequency plot of The Event

A time–frequency plot that shows The Event’s signal power in the detectors. You can see the signal increase in frequency as time goes on: the characteristic chirp of a binary merger! The fact that you can spot the signal by eye shows how loud it is. Part of Fig. 1 from the Discovery Paper.

The signal was quite short, so it was quick for us to run parameter estimation on it—this makes a welcome change as runs on long, binary neutron-star signals can take months. We actually had the first runs done before all the detection pipelines had finished running. We kept the results secret: the detection people didn’t want to know the results before they looked at their own results (it reminded me of the episode of Whatever Happened to the Likely Lads where they try to avoid hearing the results of the football until they can watch the match). The results from each of the detection pipelines came in [bonus note]. There were the other burst searches: LALInferenceBurst found strong evidence for a signal, and BayesWave classified it clearly as a signal, not noise or a glitch; then the binary searches: both GstLAL and PyCBC found the signal (the same signal) at high significance. The parameter-estimation results were beautiful—we had seen the merger of two black holes!

At first, we couldn’t quite believe that we had actually made the detection. The signal seemed too perfect. Famously, LIGO conducts blind injections: fake signals are secretly put into the data to check that we do things properly. This happened during the run of initial LIGO (an event known as the Big Dog), and many people still remembered the disappointment. We weren’t set up for injections at the time (that was part of getting ready for O1), and the heads of the Collaboration said that there were no plans for blind injections, but people wanted to be sure. Only three or four people in the Collaboration can perform a blind injection; however, it’s a little publicised fact that you can tell if there was an injection. The data from the instruments is recorded at many stages, so there’s a channel which records the injected signal. During a blind-injection run, we’re not allowed to look at this, but this wasn’t a blind-injection run, so this was checked and rechecked. There was nothing. People considered other ways of injecting the signal that wouldn’t be recorded (perhaps splitting the signal up and putting small bits in lots of different systems), but no-one actually understands all the control systems well enough to get this to work. There were basically two ways you could fake the signal. The first is hack into the servers at both sites and CalTech simultaneously and modify the data before it got distributed. You would need to replace all the back-ups and make sure you didn’t leave any traces of tampering. You would also need to understand the control system well enough that all the auxiliary channels (the signal as recorded at over 30 different stages throughout the detectors’ systems) had the right data. The second is to place a device inside the interferometers that would inject the signal. As long as you had a detailed understanding of the instruments, this would be simple: you’d just need to break into both interferometers without being noticed. Since the interferometers are two of the most sensitive machines ever made, this is like that scene from Mission:Impossible, except on the actually impossible difficulty setting. You would need to break into the vacuum tube (by installing an airlock in the concrete tubes without disturbing the seismometers), not disturb the instrument while working on it, and not scatter any of the (invisible) infra-red laser light. You’d need to do this at both sites, and then break in again to remove the devices so they’re not found now that O1 is finished. The devices would also need to be perfectly synchronised. I would love to see a movie where they try to fake the signal, but I am convinced, absolutely, that the easiest way to inject the signal is to collide two black holes a billion years ago. (Also a good plot for a film?)

There is no doubt. We have detected gravitational waves. (I cannot articulate how happy I was to hit the button to update that page! [bonus note])

I still remember the exact moment this hit me. I was giving a public talk on black holes. It was a talk similar to ones I have given many times before. I start with introducing general relativity and the curving of spacetime, then I talk about the idea of a black hole. Next I move on to evidence for astrophysical black holes, and I showed the video zooming into the centre of the Milky Way, ending with the stars orbiting around Sagittarius A*, the massive black hole in the centre of our galaxy (shown below). I said that the motion of the stars was our best evidence for the existence of black holes, then I realised that this was no longer the case. Now, we have a whole new insight into the properties of black holes.

Gravitational-wave astronomy

Having caught a gravitational wave, what do you do with it? It turns out that there’s rather a lot of science you can do. The last few months have been exhausting. I think we’ve done a good job as a Collaboration of assembling all the results we wanted to go with the detection—especially since lots of things were being done for the first time! I’m sure we’ll update our analysis with better techniques and find new ways of using the data, but for now I hope everyone can enjoy what we have discovered so far.

I will write up a more technical post on the results, here we’ll run through some of the highlights. For more details of anything, check out the data release.

The source

The results of our parameter-estimation runs tell us about the nature of the source. We have a binary with objects of masses 36^{+5}_{-4} M_\odot and 29^{+4}_{-4} M_\odot, where M_\odot indicates the mass of our Sun (about 2 \times 10^{30} kilograms). If you’re curious what’s going with these numbers and the pluses and minuses, check out this bonus note.

Binary black hole masses

Estimated masses for the two black holes in the binary. m_1^\mathrm{source} is the mass of the heavier black hole and m_2^\mathrm{source} is the mass of the lighter black hole. The dotted lines mark the edge of our 90% probability intervals. The different coloured curves show different models: they agree which made me incredibly happy! Fig. 1 from the Parameter Estimation Paper.

We know that we’re dealing with compact objects (regular stars could never get close enough together to orbit fast enough to emit gravitational waves at the right frequency), and the only compact objects that can be as massive as these object are black holes. This means we’re discovered the first stellar-mass black hole binary! We’ve also never seen stellar-mass black holes (as opposed to the supermassive flavour that live in the centres of galaxies) this heavy, but don’t get too attached to that record.

Black holes have at most three properties. This makes them much simpler than a Starbucks Coffee (they also stay black regardless of how much milk you add). Black holes are described by their mass, their spin (how much they rotate), and their electric charge. We don’t expect black holes out in the Universe to have much electric charge because (i) its very hard to separate lots of positive and negative charge in the first place, and (ii) even if you succeed at (i), it’s difficult to keep positive and negative charge apart. This is kind of like separating small children and sticky things that are likely to stain. Since the electric charge can be ignored, we just need mass and spin. We’ve measured masses, can we measure spins?

Black hole spins are defined to be between 0 (no spin) and 1 (the maximum amount you can have). Our best estimates are that the bigger black hole has spin 0.3_{-0.3}^{+0.5}, and the small one has spin 0.5_{-0.4}^{+0.5} (these numbers have been rounded). These aren’t great measurements. For the smaller black hole, its spin is almost equally probable to take any allowed value; this isn’t quite the case, but we haven’t learnt much about its size. For the bigger black hole, we do slightly better, and it seems that the spin is on the smaller side. This is interesting, as measurements of spins for black holes in X-ray binaries tend to be on the higher side: perhaps there are different types of black holes?

We can’t measure the spins precisely for a few reasons. The signal is short, so we don’t see lots of wibbling while the binaries are orbiting each other (the tell-tale sign of spin). Results for the orientation of the binary also suggest that we’re looking at it either face on or face off, which makes any wobbles in the orbit that are there less visible. However, there is one particular combination of the spins, which we call the effective spin, that we can measure. The effective spin controls how the black holes spiral together. It has a value of 1 if both black holes have max spin values, and are rotating the same way as the binary is orbiting. It has a value of −1 if the black holes have max spin values and are both rotating exactly the opposite way to the binary’s orbit. We find that the effective spin is small, -0.06_{-0.18}^{+0.17}. This could mean that both black holes have small spins, or that they have larger spins that aren’t aligned with the orbit (or each other). We have learnt something about the spins, it’s just not too easy to tease that apart to give values for each of the black holes.

As the two black holes orbit each other, they (obviously, given what we’ve seen) emit gravitational waves. These carry away energy and angular momentum, so the orbit shrinks and the black holes inspiral together. Eventually they merge and settle down into a single bigger black hole. All this happens while we’re watching (we have great seats). A simulation of this happening is below. You can see that the frequency of the gravitational waves is twice that of the orbit, and the video freezes around the merger so you can see two become one.

What are the properties of the final black hole? The mass of the remnant black holes is 62^{+4}_{-4} M_\odot. It is the new record holder for the largest observed stellar-mass black hole!

If you do some quick sums, you’ll notice that the final black hole is lighter than the sum of the two initial black holes. This is because of that energy that was carried away by the gravitational waves. Over the entire evolution of the system, 3.0^{+0.5}_{-0.4} M_\odot c^2 \simeq 5.3_{-0.8}^{+0.9} \times 10^{47}~\mathrm{J} of energy was radiated away as gravitational waves (where c is the speed of light as in Einstein’s famous equation). This is a colossal amount of energy. You’d need to eat over eight billion times the mass of the Sun in butter to get the equivalent amount of calories. (Do not attempt the wafer-thin mint afterwards). The majority of that energy is radiated within the final second. For a brief moment, this one black hole merger outshines the whole visible Universe if you compare its gravitational-wave luminosity, to everything else’s visible-light luminosity!

We’ve measured mass, what about spin? The final black hole’s spin in 0.67^{+0.05}_{-0.07}, which is in the middling-to-high range. You’ll notice that we can deduce this to a much higher precisely than the spins of the two initial black holes. This is because it is largely fixed by the orbital angular momentum of the binary, and so its value is set by orbital dynamics and gravitational physics. I think its incredibly satisfying that we we can such a clean measurement of the spin.

We have measured both of the properties of the final black hole, and we have done this using spacetime itself. This is astounding!

Final black hole mass and spin

Estimated mass M_\mathrm{f}^\mathrm{source} and spin a_\mathrm{f}^\mathrm{source} for the final black hole. The dotted lines mark the edge of our 90% probability intervals. The different coloured curves show different models: they agree which still makes me incredibly happy! Fig. 3 from the Parameter Estimation Paper.

How big is the final black hole? My colleague Nathan Johnson-McDaniel has done some calculations and finds that the total distance around the equator of the black hole’s event horizon is about 1100~\mathrm{km} (about six times the length of the M25). Since the black hole is spinning, its event horizon is not a perfect sphere, but it bulges out around the equator. The circumference going over the black hole’s poles is about 1000~\mathrm{km} (about five and a half M25s, so maybe this would be the better route for your morning commute). The total area of the event horizon is about 37000~\mathrm{km}^2. If you flattened this out, it would cover an area about the size of Montana. Neil Cornish (of Montana State University) said that he’s not sure which we know more accurately: the area of the event horizon or the area of Montana!

OK, we’ve covered the properties of the black holes, perhaps it’s time for a celebratory biscuit and a sit down? But we’re not finished yet, where is the source?

We infer that the source is at a luminosity distance of 410^{+160}_{-180}~\mathrm{Mpc}, a megaparsec is a unit of length (regardless of what Han Solo thinks) equal to about 3 million light-years. The luminosity distance isn’t quite the same as the distance you would record using a tape measure because it takes into account the effects of the expansion of the Universe. But it’s pretty close. Using our 90% probability range, the merger would have happened sometime between 700 million years and 1.6 billion years ago. This coincides with the Proterozoic Eon on Earth, the time when the first oxygen-dependent animals appeared. Gasp!

With only the two LIGO detectors in operation, it is difficult to localise where on the sky source came from. To have a 90% chance of finding the source, you’d need to cover 600~\mathrm{deg^2} of the sky. For comparison, the full Moon is about 0.2~\mathrm{deg^2}. This is a large area to cover with a telescope, and we don’t expect there to be anything to see for a black hole merger, but that hasn’t stopped our intrepid partners from trying. For a lovely visualisation of where we think the source could be, marvel at the Gravoscope.

Astrophysics

The detection of this black hole merger tells us:

  • Black holes 30 times the mass of our Sun do form These must be the remains of really massive stars. Stars lose mass throughout their lifetime through stellar winds. How much they lose depends on what they are made from. Astronomers have a simple periodic table: hydrogen, helium and metals. (Everything that is not hydrogen or helium is a metal regardless of what it actually is). More metals means more mass loss, so to end up with our black holes, we expect that they must have started out as stars with less than half the fraction of metals found in our Sun. This may mean the parent stars were some of the first stars to be born in the Universe.
  • Binary black holes exist There are two ways to make a black hole binary. You can start with two stars in a binary (stars love company, so most have at least one companion), and have them live their entire lives together, leaving behind the two black holes. Alternatively, you could have somewhere where there are lots of stars and black holes, like a globular cluster, and the two black holes could wander close enough together to form the binary. People have suggested that either (or both) could happen. You might be able to tell the two apart using spin measurements. The spins of the black holes are more likely to be aligned (with each other and the way that the binary orbits) if they came from stars formed in a binary. The spins would be randomly orientated if two black holes came together to form a binary by chance. We can’t tell the two apart now, but perhaps when we have more observations!
  • Binary black holes merge Since we’ve seen a signal from two black holes inspiralling together and merging, we know that this happens. We can also estimate how often this happens, given how many signals we’ve seen in our observations. Somewhere in the observable Universe, a similar binary could be merging about every 15 minutes. For LIGO, this should mean that we’ll be seeing more. As the detectors’ sensitivity improves (especially at lower frequencies), we’ll be able to detect more and more systems [bonus note].  We’re still uncertain in our predictions of exactly how many we’ll see. We’ll understand things better after observing for longer: were we just lucky, or were we unlucky not to have seen more? Given these early results, we estimate that the end of the third observing run (O3), we could have over 30. It looks like I will be kept busy over the next few years…

Gravitational physics

Black holes are the parts of the Universe with the strongest possible gravity. They are the ideal place to test Einstein’s theory of general relativity. The gravitational waves from a black hole merger let us probe right down to the event horizon, using ripples in spacetime itself. This makes gravitational waves a perfect way of testing our understanding of gravity.

We have run some tests on the signal to see how well it matches our expectations. We find no reason to doubt that Einstein was right.

The first check is that if we try to reconstruct the signal, without putting in information about what gravitational waves from a binary merger look like, we find something that agrees wonderfully with our predictions. We can reverse engineer what the gravitational waves from a black hole merger look like from the data!

Estimated waveforms from different models

Recovered gravitational waveforms from our analysis of The Event. The dark band shows our estimate for the waveform without assuming a particular source (it is build from wavelets, which sound adorable to me). The light bands show results if we assume it is a binary black hole (BBH) as predicted by general relativity. They match really well! Fig. 6 from the Parameter Estimation Paper.

As a consistency test, we checked what would happen if you split the signal in two, and analysed each half independently with our parameter-estimation codes. If there’s something weird, we would expect to get different results. We cut the data into a high frequency piece and a low frequency piece at roughly where we think the merger starts. The lower frequency (mostly) inspiral part is more similar to the physics we’ve tested before, while the higher frequency (mostly) merger and ringdown is new and hence more uncertain. Looking at estimates for the mass and spin of the final black hole, we find that the two pieces are consistent as expected.

In general relativity, gravitational waves travel at the speed of light. (The speed of light is misnamed, it’s really a property of spacetime, rather than of light). If gravitons, the theoretical particle that carries the gravitational force, have a mass, then gravitational waves can’t travel at the speed of light, but would travel slightly slower. Because our signals match general relativity so well, we can put a limit on the maximum allowed mass. The mass of the graviton is less than 1.2 \times 10^{-22}~\mathrm{eV\,c^{-2}} (in units that the particle physicists like). This is tiny! It is about as many times lighter than an electron as an electron is lighter than a teaspoon of water (well, 4~\mathrm{g}, which is just under a full teaspoon), or as many times lighter than the almost teaspoon of water is than three Earths.

Limits on the Compton wavelength of the graviton

Bounds on the Compton wavelength \lambda_g of the graviton from The Event (GW150914). The Compton wavelength is a length defined by the mass of a particle: smaller masses mean large wavelengths. We place much better limits than existing tests from the Solar System or the double pulsar. There are some cosmological tests which are stronger still (but they make assumptions about dark matter). Fig. 8 from the Testing General Relativity Paper.

Overall things look good for general relativity, it has passed a tough new test. However, it will be extremely exciting to get more observations. Then we can combine all our results to get the best insights into gravity ever. Perhaps we’ll find a hint of something new, or perhaps we’ll discover that general relativity is perfect? We’ll have to wait and see.

Conclusion

100 years after Einstein predicted gravitational waves and Schwarzschild found the equations describing a black hole, LIGO has detected gravitational waves from two black holes orbiting each other. This is the culmination of over forty years of effort. The black holes inspiral together and merge to form a bigger black hole. This is the signal I would have wished for. From the signal we can infer the properties of the source (some better than others), which makes me exceedingly happy. We’re starting to learn about the properties of black holes, and to test Einstein’s theory. As we continue to look for gravitational waves (with Advanced Virgo hopefully joining next year), we’ll learn more and perhaps make other detections too. The era of gravitational-wave astronomy has begun!

After all that, I am in need of a good nap! (I was too excited to sleep last night, it was like a cross between Christmas Eve and the night before final exams). For more on the story from scientists inside the LIGO–Virgo Collaboration, check out posts by:

  • Matt Pitkin (the tireless reviewer of our parameter-estimation work)
  • Brynley Pearlstone (who’s just arrived at the LIGO Hanford site)
  • Amber Stuver (who  blogged through LIGO’s initial runs too)
  • Rebecca Douglas (a good person to ask about what build a detector out of)
  • Daniel Williams (someone fresh to the Collaboration)
  • Sean Leavey (a PhD student working on on interferometry)
  • Andrew Williamson (who likes to look for gravitational waves that coincide with gamma-ray bursts)
  • Shane Larson (another fan of space-based gravitational-wave detectors)
  • Roy Williams (who helps to make all the wonderful open data releases for LIGO)
  • Chris North (creator of the Gravoscope amongst other things)

There’s also this video from my the heads of my group in Birmingham on their reactions to the discovery (the credits at the end show how large an effort the detection is).

Discovery paper: Observation of Gravitational Waves from a Binary Black Hole Merger
Date release:
LIGO Open Science Center

Bonus notes

Search pipelines

At the Large Hadron Collider, there are separate experiments that independently analyse data, and this is an excellent cross-check of any big discoveries (like the Higgs). We’re not in a position to do this for gravitational waves. However, the different search pipelines are mostly independent of each other. They use different criteria to rank potential candidates, and the burst and binary searches even look for different types of signals. Therefore, the different searches act as a check of each other. The teams can get competitive at times, so they do check each other’s results thoroughly.

The announcement

Updating Have we detected gravitational waves yet? was doubly exciting as I had to successfully connect to the University’s wi-fi. I managed this with about a minute to spare. Then I hovered with my finger on the button until David Reitze said “We. Have detected. Gravitational waves!” The exact moment is captured in the video below, I’m just off to the left.

Parameters and uncertainty

We don’t get a single definite number from our analysis, we have some uncertainty too. Therefore, our results are usually written  as the median value (which means we think that the true value is equally probable to be above or below this number), plus the range needed to safely enclose 90% of the probability (so there’s a 10% chance the true value is outside this range. For the mass of the bigger black hole, the median estimate is 36 M_\odot, we think there’s a 5% chance that the mass is below 32 M_\odot =(36 - 4) M_\odot, and a 5% chance it’s above 41 M_\odot =(36 + 5) M_\odot, so we write our result as 36^{+5}_{-4} M_\odot.

Sensitivity and ranges

Gravitational-wave detectors measure the amplitude of the wave (the amount of stretch and squash). The measured amplitude is smaller for sources that are further away: if you double the luminosity distance of a source, you halve its amplitude. Therefore, if you improve your detectors’ sensitivity by a factor of two, you can see things twice as far away. This means that we observe a volume of space (2 × 2 × 2) = 8 times as big. (This isn’t exactly the case because of pesky factors from the expansion of the Universe, but is approximately right). Even a small improvement in sensitivity can have a considerable impact on the number of signals detected!

General relativity at 100

General relativity, our best theory of gravitation, turns 100 this week!

Where is the cake?

Happy birthday general relativity! Einstein presented his field equations to the Prussian Academy of Science on 25 November 1915.

Gravity is the force which pulls us down towards the ground and keeps the Earth in orbit around the Sun. It is the most important force in astrophysics, causing gas clouds to collapse down to become stars; binding gas, stars and dark matter to become galaxies, and governing the overall evolution of the Universe.

Our understanding of gravity dates back to Isaac Newton. Newton realised that the same force that makes apples fall from trees also controls the motion of the planets. Realising that we could use physics to explain the everyday and the entire cosmos was a big leap! Newton’s theory was hugely successful, but he was never quite satisfied with it. In his theory gravity acted between distant objects (the Earth and an apple or the Earth and the Sun) instantaneously, without any explanation of what was linking them. The solution to this would come over 200 years later from Albert Einstein.

Einstein’s first big idea didn’t come from thinking about gravity, but thinking about electromagnetism. Electromagnetism is the force that is responsible for fridge magnets sticking, atoms binding to form molecules and the inner workings of whatever device you are currently reading this on. According to the rules of electromagnetism, ripples in electromagnetic fields (better known as light) always travel at a particular speed. This tweaked Einstein’s curiosity, as the rules didn’t say what this speed was relative to: you should measure the same speed if standing still, travelling at 100 miles per hour in a train or at a million miles per hour in a spacecraft. Speed is the distance travelled divided by the time taken, so Einstein realised that if the speed is always the same, then distances and times must appear different depending upon how you are moving! Moving clocks tick slower; at everyday speeds this effect is tiny, but we have confirmed that this is indeed the case. These ideas about space and time became known as Einstein’s theory of special relativity. Special relativity has a couple of important consequences, one is the infamous equation, the other is that the speed of light becomes a universal speed limit.

Special relativity says that no information can travel faster than the speed of light; this is a problem for Newton’s theory of gravitation, where the effects of gravity are transmitted instantaneously. Einstein knew that he would have to extend his theory to include gravity and freely falling objects, and he spend almost 11 years pondering on the problem. The result was general relativity.

In special relativity, space and time become linked, merging into one another depending upon how you are moving relative to what you are measuring. General relativity takes this further and has space–time distorted by the energy and matter. This idea can be a little tricky to explain.

In Newtonian mechanics, things (apples, light, billiard balls, etc.) like to travel in straight lines. They keep going at a constant speed in the same direction unless there is a force acting on them. Gravity is a force which pulls things away from their straight line, pulling the Earth into its circular orbit around the Sun, and accelerating an apple towards the ground. In general relativity, we take a different view. Things still travel in a straight line, but the effect of gravity is to bend space–time! A straight line in a curved space is a curve. If we don’t know about the curvature, it looks like the object is pulled off its straight line and there must be a force doing this, which we call gravity. Alternatively, we can say that gravity curves the space–time, and that the object follows its straight line in this. In general relativity, space–time tells matter how to move; matter tells space–time how to curve.

Shotest distance between London and New York

The shortest way to travel from London Heathrow airport to JFK International airport. On a long-distance flight, you may have noticed that it appears that you are moving along a curved line, but that is because the shortest distance across the Earth’s curved surface is a curve. We call this a geodesic, and the same idea applies to curved space–time in general relativity. Credit: Mr Reid.

General relativity solves Newton’s original worries. Objects are connected by space–time. This is not the rigid background of Newtonian physics, but a dynamic object, that is shaped by its contents. Space–time is curved by mass, and when the mass moves or reshapes itself, it takes time for the curvature everywhere else to readjust. When you drop a pebble into a pond, you disturb the surface, but it takes a while for the water further away to know about the splash; there’s a ripple that travels outwards, carrying the information about the disturbance. A similar thing happens for changes in gravity, there are ripples in space–time. Ripples in electromagnetic fields are electromagnetic waves, and these ripples in the gravitational fields are gravitational waves: both travel at the speed of light, in agreement with special relativity.

General relativity is not only a beautiful theory, it has so far passed every experimental test. Right from the start Einstein looked for checks of his theory. One of the calculations he did while formulating his theory was how the orbit of Mercury would change. Mercury is the planet closest to the Sun and so experiences the strongest gravity. Its orbit isn’t a perfect circle, but an ellipse so that Mercury is sometimes a little closer to the Sun, and is sometimes a little further. In Newtonian gravity, each orbit should trace out exactly the same path, but in general relativity there is some extra rotation. Each orbit is slightly shifted with respect to the last, so if you traced out many orbits, you’d end up with a Spirograph-like pattern. This is known as precession of the orbit, and is a consequence of there being slightly greater curvature closer to the Sun. This evolution of Mercury’s orbit had already been measured. Some thought it indicated there was a new planet inside Mercury’s orbit (which was called Vulcan but isn’t Spock’s home) that was giving it a little pull. However, Einstein calculated the general relativity predicted exactly the right amount of extra rotation!

The next test came in 1919. General relativity predicts that the path of light is bent by massive objects. This is gravitational lensing. At the time, the only object that could cause measurable bending was the Sun. If we could measure a change in the position of background stars when the Sun was in front of them, we could check if the amount of bending was as expected. There’s an obvious problem here: the Sun’s so bright that you can’t see stars around it. Arthur Eddington had the idea of making the measurement during an eclipse. He mounted an expedition and confirmed the prediction. This was big news and made Einstein a superstar.

Now, 100 years after Einstein proposed his theory, we are poised to make the most precise tests. There is currently a global effort to directly detect gravitational waves. Measuring the gravitational waves will tell us if ripples in space–time behave as Einstein predicted. The waves will also tell us about the systems that created them, this will give us an up-close glimpse of black holes. Black holes are the regions of strongest gravity; they are where the curvature of space–time becomes so immense that all straight lines lead inwards. Checking that the black holes of Nature match what we expect from general relativity, will test the theory in the most extreme conditions possible.

The Advanced LIGO detectors are currently listening for gravitational-wave signals from merging neutron stars or black holes, and next year Advanced Virgo plans join the hunt too. We don’t (yet) know how often such signals occur, so we can’t say when the first detection will be made. Perhaps this will be soon and we will learn something more about gravitation…

Ripples in space time

Merging black holes create ripples in space time. These can be detected with a laser interferometer. Credit: Gravitational Wave Group.

Advanced LIGO: O1 is here!

The LIGO sites

Aerial views of LIGO Hanford (left) and LIGO Livingston (right). Both have 4 km long arms (arranged in an L shape) which house the interferometer beams. Credit: LIGO/Caltech/MIT.

The first observing run (O1) of Advanced LIGO began just over a week ago. We officially started at 4 pm British Summer Time, Friday 18 September. It was a little low key: you don’t want lots of fireworks and popping champagne corks next to instruments incredibly sensitive to vibrations. It was a smooth transition from our last engineering run (ER8), so I don’t even think there were any giant switches to throw. Of course, I’m not an instrumentalist, so I’m not qualified to say. In any case, it is an exciting time, and it is good to see some media attention for the Collaboration (with stories from Nature, the BBC and Science).

I would love to keep everyone up to date with the latest happenings from LIGO. However, like everyone in the Collaboration, I am bound by a confidentiality agreement. (You don’t want to cross people with giant lasers). We can’t have someone saying that we have detected a binary black hole (or that we haven’t) before we’ve properly analysed all the data, finalised calibration, reviewed all the code, double checked our results, and agreed amongst ourselves that we know what’s going on. When we are ready, announcements will come from the LIGO Spokespreson Gabriela González and the Virgo Spokesperson Fulvio Ricci. Event rates are uncertain and we’re not yet at final sensitivity, so don’t expect too much of O1.

There are a couple of things that I can share about our status. Whereas normally everything I write is completely unofficial, these are suggested replies to likely questions.

Have you started taking data?
We began collecting science quality data at the beginning of September, in preparation of the first Observing Run that started on Friday, September 18, and are planning on collecting data for about 4 months

We certainly do have data, but there’s nothing new about that (other than the improved sensitivity). Data from the fifth and sixth science runs of initial LIGO are now publicly available from the LIGO Open Science Center. You can go through it and try to find anything we missed (which is pretty cool).

Have you seen anything in the data yet?
We analyse the data “online” in an effort to provide fast information to astronomers for possible follow up of triggers using a relatively low statistical significance (a false alarm rate of ~1/month). We have been tuning the details of the communication procedures, and we have not yet automated all the steps that can be, but we will send alerts to astronomers above the threshold agreed as soon as we can after those triggers are identified. Since analysis to validate and candidate in gravitational-wave data can take months, we will not be able to say anything about results in the data on short time scales. We will share any and all results when ready, though probably not before the end of the Observing Run. 

Analysing the data is tricky, and requires lots of computing time, as well as carefully calibration of the instruments (including how many glitches they produce which could look like a gravitational-wave trigger). It takes a while to get everything done. If you would like to help out, you can sign up for Einstein@Home, which will use your computer’s idle time to crunch through data. It doesn’t just analyse LIGO data, but has also discovered pulsars in radio and gamma-ray data. You can find out more about Einstein@Home in the LIGO Magazine.

We heard that you sent a gravitational-wave trigger to astronomers already—is that true?
During O1, we will send alerts to astronomers above a relatively low significance threshold; we have been practising communication with astronomers in ER8. We are following this policy with partners who have signed agreement with us and have observational capabilities ready to follow up triggers. Because we cannot validate gravitational-wave events until we have enough statistics and diagnostics, we have confidentiality agreements about any triggers that hare shared, and we hope all involved abide by those rules.

I expect this is a pre-emptive question and answer. It would be amazing if we could see an electromagnetic (optical, gamma-ray, radio, etc.) counterpart to a gravitational wave. (I’ve done some work on how well we can localise gravitational-wave sources on the sky). It’s likely that any explosion or afterglow that is visible will fade quickly, so we want astronomers to be able to start looking straight-away. This means candidate events are sent out before they’re fully vetted: they could just be noise, they could be real, or they could be a blind injection. A blind injection is when a fake signal is introduced to the data secretly; this is done to keep us honest and check that our analysis does work as expected (since we know what results we should get for the signal that was injected). There was a famous blind injection during the run of initial LIGO called Big Dog. (We take gravitational-wave detection seriously). We’ve learnt a lot from injections, even if they are disappointing. Alerts will be sent out for events with false alarm rates of about one per month, so we expect a few across O1 just because of random noise.

While I can’t write more about the science from O1, I will still be posting about astrophysics, theory and how we analyse data. Those who are impatient can be reassured that gravitational waves have been detected, just indirectly, from observations of binary pulsars.

Periastron shift of binary pulsar

The orbital decay of the Hulse-Taylor binary pulsar (PSR B1913+16). The points are measured values, while the curve is the theoretical prediction for gravitational waves. I love this plot. Credit: Weisberg & Taylor (2005).

LIGO Magazine: Issue 7

It is an exciting time time in LIGO. The start of the first observing run (O1) is imminent. I think they just need to sort out a button that is big enough and red enough (or maybe gather a little more calibration data… ), and then it’s all systems go. Making the first direct detection of gravitational waves with LIGO would be an enormous accomplishment, but that’s not all we can hope to achieve: what I’m really interested in is what we can learn from these gravitational waves.

The LIGO Magazine gives a glimpse inside the workings of the LIGO Scientific Collaboration, covering everything from the science of the detector to what collaboration members like to get up to in their spare time. The most recent issue was themed around how gravitational-wave science links in with the rest of astronomy. I enjoyed it, as I’ve been recently working on how to help astronomers look for electromagnetic counterparts to gravitational-wave signals. It also features a great interview with Joseph Taylor Jr., one of the discoverers of the famous Hulse–Taylor binary pulsar. The back cover features an article I wrote about parameter estimation: an expanded version is below.

How does parameter estimation work?

Detecting gravitational waves is one of the great challenges in experimental physics. A detection would be hugely exciting, but it is not the end of the story. Having observed a signal, we need to work out where it came from. This is a job for parameter estimation!

How we analyse the data depends upon the type of signal and what information we want to extract. I’ll use the example of a compact binary coalescence, that is the inspiral (and merger) of two compact objects—neutron stars or black holes (not marshmallows). Parameters that we are interested in measuring are things like the mass and spin of the binary’s components, its orientation, and its position.

For a particular set of parameters, we can calculate what the waveform should look like. This is actually rather tricky; including all the relevant physics, like precession of the binary, can make for some complicated and expensive-to-calculate waveforms. The first part of the video below shows a simulation of the coalescence of a black-hole binary, you can see the gravitational waveform (with characteristic chirp) at the bottom.

We can compare our calculated waveform with what we measured to work out how well they fit together. If we take away the wave from what we measured with the interferometer, we should be left with just noise. We understand how our detectors work, so we can model how the noise should behave; this allows us to work out how likely it would be to get the precise noise we need to make everything match up.

To work out the probability that the system has a given parameter, we take the likelihood for our left-over noise and fold in what we already knew about the values of the parameters—for example, that any location on the sky is equally possible, that neutron-star masses are around 1.4 solar masses, or that the total mass must be larger than that of a marshmallow. For those who like details, this is done using Bayes’ theorem.

We now want to map out this probability distribution, to find the peaks of the distribution corresponding to the most probable parameter values and also chart how broad these peaks are (to indicate our uncertainty). Since we can have many parameters, the space is too big to cover with a grid: we can’t just systematically chart parameter space. Instead, we randomly sample the space and construct a map of its valleys, ridges and peaks. Doing this efficiently requires cunning tricks for picking how to jump between spots: exploring the landscape can take some time, we may need to calculate millions of different waveforms!

Having computed the probability distribution for our parameters, we can now tell an astronomer how much of the sky they need to observe to have a 90% chance of looking at the source, give the best estimate for the mass (plus uncertainty), or even figure something out about what neutron stars are made of (probably not marshmallow). This is the beginning of gravitational-wave astronomy!

Monty and Carla map parameter space

Monty, Carla and the other samplers explore the probability landscape. Nutsinee Kijbunchoo drew the version for the LIGO Magazine.

Parameter estimation for binary neutron-star coalescences with realistic noise during the Advanced LIGO era

The first observing run (O1) of Advanced LIGO is nearly here, and with it the prospect of the first direct detection of gravitational waves. That’s all wonderful and exciting (far more exciting than a custard cream or even a chocolate digestive), but there’s a lot to be done to get everything ready. Aside from remembering to vacuum the interferometer tubes and polish the mirrors, we need to see how the data analysis will work out. After all, having put so much effort into the detector, it would be shame if we couldn’t do any science with it!

Parameter estimation

Since joining the University of Birmingham team, I’ve been busy working on trying to figure out how well we can measure things using gravitational waves. I’ve been looking at binary neutron star systems. We expect binary neutron star mergers to be the main source of signals for Advanced LIGO. We’d like to estimate how massive the neutron stars are, how fast they’re spinning, how far away they are, and where in the sky they are. Just published is my first paper on how well we should be able to measure things. This took a lot of hard work from a lot of people, so I’m pleased it’s all done. I think I’ve earnt a celebratory biscuit. Or two.

When we see something that looks like it could be a gravitational wave, we run code to analyse the data and try to work out the properties of the signal. Working out some properties is a bit trickier than others. Sadly, we don’t have an infinite number of computers, so it means it can take a while to get results. Much longer than the time to eat a packet of Jaffa Cakes…

The fastest algorithm we have for binary neutron stars is BAYESTAR. This takes the same time as maybe eating one chocolate finger. Perhaps two, if you’re not worried about the possibility of choking. BAYESTAR is fast as it only estimates where the source is coming from. It doesn’t try to calculate a gravitational-wave signal and match it to the detector measurements, instead it just looks at numbers produced by the detection pipeline—the code that monitors the detectors and automatically flags whenever something interesting appears. As far as I can tell, you give BAYESTAR this information and a fresh cup of really hot tea, and it uses Bayes’ theorem to work out how likely it is that the signal came from each patch of the sky.

To work out further details, we need to know what a gravitational-wave signal looks like and then match this to the data. This is done using a different algorithm, which I’ll refer to as LALInference. (As names go, this isn’t as cool as SKYNET). This explores parameter space (hopping between different masses, distances, orientations, etc.), calculating waveforms and then working out how well they match the data, or rather how likely it is that we’d get just the right noise in the detector to make the waveform fit what we observed. We then use another liberal helping of Bayes’ theorem to work out how probable those particular parameter values are.

It’s rather difficult to work out the waveforms, but some our easier than others. One of the things that makes things trickier is adding in the spins of the neutron stars. If you made a batch of biscuits at the same time you started a LALInference run, they’d still be good by the time a non-spinning run finished. With a spinning run, the biscuits might not be quite so appetising—I generally prefer more chocolate than penicillin on my biscuits. We’re working on speeding things up (if only to prevent increased antibiotic resistance).

In this paper, we were interested in what you could work out quickly, while there’s still chance to catch any explosion that might accompany the merging of the neutron stars. We think that short gamma-ray bursts and kilonovae might be caused when neutron stars merge and collapse down to a black hole. (I find it mildly worrying that we don’t know what causes these massive explosions). To follow-up on a gravitational-wave detection, you need to be able to tell telescopes where to point to see something and manage this while there’s still something that’s worth seeing. This means that using spinning waveforms in LALInference is right out, we just use BAYESTAR and the non-spinning LALInference analysis.

What we did

To figure out what we could learn from binary neutron stars, we generated a large catalogue of fakes signals, and then ran the detection and parameter-estimation codes on this to see how they worked. This has been done before in The First Two Years of Electromagnetic Follow-Up with Advanced LIGO and Virgo which has a rather delicious astrobites write-up. Our paper is the sequel to this (and features most of the same cast). One of the differences is that The First Two Years assumed that the detectors were perfectly behaved and had lovely Gaussian noise. In this paper, we added in some glitches. We took some real data™ from initial LIGO’s sixth science run and stretched this so that it matches the sensitivity Advanced LIGO is expected to have in O1. This process is called recolouring [bonus note]. We now have fake signals hidden inside noise with realistic imperfections, and can treat it exactly as we would real data. We ran it through the detection pipeline, and anything which was flagged as probably being a signal (we used a false alarm rate of once per century), was analysed with the parameter-estimation codes. We looked at how well we could measure the sky location and distance of the source, and the masses of the neutron stars. It’s all good practice for O1, when we’ll be running this analysis on any detections.

What we found

  1. The flavour of noise (recoloured or Gaussian) makes no difference to how well we can measure things on average.
  2. Sky-localization in O1 isn’t great, typically hundreds of square degrees (the median 90% credible region is 632 deg2), for comparison, the Moon is about a fifth of a square degree. This’ll make things interesting for the people with telescopes.

    Sky localization map for O1.

    Probability that of a gravitational-wave signal coming from different points on the sky. The darker the red, the higher the probability. The star indicates the true location. This is one of the worst localized events from our study for O1. You can find more maps in the data release (including 3D versions), this is Figure 6 of Berry et al. (2015).

  3. BAYESTAR does just as well as LALInference, despite being about 2000 times faster.

    Sky localization for binary neutron stars during O1.

    Sky localization (the size of the patch of the sky that we’re 90% sure contains the source location) varies with the signal-to-noise ratio (how loud the signal is). The approximate best fit is \log_{10}(\mathrm{CR}_{0.9}/\mathrm{deg^2}) \approx -2 \log_{10}(\varrho) +5.06, where \mathrm{CR}_{0.9} is the 90% sky area and \varrho is the signal-to-noise ratio. The results for BAYESTAR and LALInference agree, as do the results with Gaussian and recoloured noise. This is Figure 9 of Berry et al. (2015).

  4. We can’t measure the distance too well: the median 90% credible interval divided by the true distance (which gives something like twice the fractional error) is 0.85.
  5. Because we don’t include the spins of the neutron stars, we introduce some error into our mass measurements. The chirp mass, a combination of the individual masses that we’re most sensitive to [bonus note], is still reliably measured (the median offset is 0.0026 of the mass of the Sun, which is tiny), but we’ll have to wait for the full spinning analysis for individual masses.

    Mean offset in chirp-mass estimates when not including the effects of spin.

    Fraction of events with difference between the mean estimated and true chirp mass smaller than a given value. There is an error because we are not including the effects of spin, but this is small. Again, the type of noise makes little difference. This is Figure 15 of Berry et al. (2015).

There’s still some work to be done before O1, as we need to finish up the analysis with waveforms that include spin. In the mean time, our results are all available online for anyone to play with.

arXiv: 1411.6934 [astro-ph.HE]
Journal: Astrophysical Journal; 904(2):114(24); 2015
Data release: The First Two Years of Electromagnetic Follow-Up with Advanced LIGO and Virgo
Favourite colour: Blue. No, yellow…

Notes

The colour of noise: Noise is called white if it doesn’t have any frequency dependence. We made ours by taking some noise with initial LIGO’s frequency dependence (coloured noise), removing the frequency dependence (making it white), and then adding in the frequency dependence of Advanced LIGO (recolouring it).

The chirp mass: Gravitational waves from a binary system depend upon the masses of the components, we’ll call these m_1 and m_2. The chirp mass is a combination these that we can measure really well, as it determines the most significant parts of the shape of the gravitational wave. It’s given by

\displaystyle \mathcal{M} = \frac{m_1^{3/5} m_2^{3/5}}{(m_1 + m_2)^{1/5}}.

We get lots of good information on the chirp mass, unfortunately, this isn’t too useful for turning back into the individual masses. For that we next extra information, for example the mass ratio m_2/m_1. We can get this from less dominant parts of the waveform, but it’s not typically measured as precisely as the chirp mass, so we’re often left with big uncertainties.