Cosmology Views
An Excel spreadsheet contains all the LIGO gravitational wave candidates and the earth tide details.
That spreadsheet is available in pdf here in several parts:
LIGOpt1
GraceDBpt2
LIGO-Combined.
Legends
GraceDB is an online Gravitational-Wave Candidate Event Database
Its records begin in 2019.
These candidates are reviewed and some of them are placed in the LIGO list available in Wikipedia with the identified binary.
As of December 16, 2019 here are these candidate events and their associated earth tide events which trigger the detections.
There are 56 candidate events in GraceDB for 22 earth tide events.
This topic is a follow up to the topic titled LIGO Event Trigger Timing.
The LIGO list has GW detections with assigned probabilities for the inspiral event. GraceDB has all GW candidates, even those lacking confidence to assign probabilities so the GraceDB list has a higher count when covering fewer years.
One comparison between the two lists:
In the LIGO list begun in 2015:
All 50 events in Wikipedia are within 8 days of an earth tide peak. 29 are within 2 days of an earth tide.
In the GraceDB list begun in 2019:
All 56 events in GraceDB are within 8 days of an earth tide peak. 31 are within 2 days of an earth tide.
The celestial events causing an earth tide in this time period: Full Moon, New Moon, PeriGee, PeriHelion, Moon-Jupiter alignment.
* - is in LIGO list
- is not in LIGO list
NOP = No PE_READY. The last status indicator for an event progression in the Grace data base is PE_READY and those events usually get published in the Wikipedia LIGO list; NOP indicates this event does not have that final PE_READY status. Its omission or presence suggests the parameters are important about the quality of this detection.
NM-19-04-05 --- caused one trigger, after this event
- S190405ar _ same day as NM not in LIGO list _ NOP
* S190408an _ 3 days after NM
PG-19-04-15 --- caused one trigger, before this event
S19040412m 4 days before PG
FM-19-04-19_ resulted in 1 trigger after
* S190421ar _ 2 days after FM _ NOP
MJ-19-04-23 -- caused 2 triggers after
* S190425z _ 2 days after MJ
* S190426c _ 3 days after MJ
NM-19-05-04 _ resulted in 2 triggers, 1 before, 1 after
* S190503bf _ 1 day before NM
PG-19-05-13 _ resulted in 3 triggers before
- S190510g _ 3 days before PG _ not in LIGO list _ NOP
S190512at _ 1 days before PG
* S190513bm _ same day as PG
FM-19-05-18 _ resulted in 6 triggers, 2 before, 4 after
* * S190517h _ 1 day before FM
- S190518bb _ same day as FM but not in LIGO list _ NOP
* S190519bj _ 1 day after FM
* S190521g _ 3 days after FM
* S190521r _ 3 days after FM
- S190524a _ 6 days after FM _ not in LIGO list _ NOP
NM-19-06-03 --- caused one trigger, before this event
* S190602aq _ 1 day before NM
NM-19-07-02 _ NM solar eclipse _ resulted in 4 triggers, 2 before, 2 after
* S190630ag _ 2 days before NM
* S190701br _ 1 day before NM
* S190706ai _ 4 days after NM
* S190707q _ 5 days after NM
FM-19-07-18 --- caused 2 triggers, 1 before, 1 after
- S190718y _ same day as FM but not in LIGO list _ NOP
* S190720a _ 2 days after FM
NM-19-07-31 -- caused 2 triggers, both before
* S190727h _ 4 days before NM
* S190728q _ 3 days before NM
FM-19-08-15 -- caused 3 triggers, 1 before, 2 after
- S190808ae _ 6 days after PG _ not in LIGO list _ NOP
* S190814bv _ 1 day before FM
- S190816i _ 1 day after FM
- S190822c _ 7 days after FM _ not in LIGO list _ NOP
NM--19-08-30 --- caused 4 triggers, 3 before, 1 after
* S190828j _ 2 days before NM
* S190828l _ 2 days before NM
* S190829u _ 1 day before NM
* S190901ap _ 2 days after NM
FM-19-09-13 -- caused 3 triggers, 2 before, 1 after
* S190910d _ 3 days before FM
* S190910h _ 3 days before FM
* S190915ak _ 2 days after FM
NM--19-09-28 -- caused 5 triggers 3 before, 2 after
* S190923y _ 5 days before NM _ NOP
* S190924h _ 4 days before NM
- S190928c _ same day as NM _ not in LIGO list _ NOP
* S190930s _ 2 days after NM _ NOP
* S190930t _ 2 days after NM _ NOP
NM-19-11-12 -- caused 5 triggers, 4 before, 1 after
* S191105e _ 7 days before NM _ NOP
- S191109d _ 3 days before NM _ NOP
- S1911110x _ 2 days before NM _ not in LIGO list _ NOP
- S1911110af _ 2 days before NM _ not in LIGO list _ NOP
- S191117j _ 5 days after FM_ not in LIGO list _ NOP
PG-19-11-23 -- caused 3 triggers before
S191120aj _ 3 days before PG _ not in LIGO list _ NOP
- S191120at_ 3 days before PG _ not in LIGO list _ NOP
- S191124be _ 1 day after PG _ not in LIGO list _ NOP
NM-19-11-26 -- caused 1 trigger after
* S191129u _ 3 days before NM _NOP
FM-19-12-12 -- caused 5 triggers, 3 before, 2 after
- S191204t _ 8 days before FM _ not in LIGO list _ NOP
- S191205ah_ 7 days before FM _ not in LIGO list _ NOP
- S191212q_ same day as FM _ not in LIGO list _ NOP
- S191213g _ 1 day after FM _ not in LIGO list _ NOP
- S191213ai _ 1 day after FM _ not in LIGO list _ NOP
* S191215w _ 3 days after FM _ NOP
The distribution of days (days=count):
0=4, 1=12, 2=15, 3=13, 4=4, 5=2, 6=3, 7=3, 8=3
31 of 56 events in GraceDB are within 2 days of an earth tide peak.
All 56 events in GraceDB are within 8 days of an earth tide peak.
Note: the outliers at 7 or 8 days lack the PE_READY status or these are inconsistent with most in LIGO list; both have only SKYMAP_READY.
Ignoring those outliers leaves all detections within 6 days.
link to GraceDB
Last updated (12/04/2019)