Archive by Author | mzevin

LIGO bags its 4th binary black hole, with the help of Virgo!

Hello Gravity Spy team,

As you may have heard, the LIGO and Virgo detector network has found its first triple-coincident signal! This signal, GW170814, is a binary black hole inspiral, with the masses of the two colliding black holes at about 25 and 30 times the mass of the Sun. Virgo’s observation of this event, and the relative time delay of receiving the signals between the 3 detectors, GREATLY improves our ability to pinpoint the location of the event on the sky, which will help our electromagnetic partners to possibly find a coincident signal with their telescopes. You can find the full paper of this discovery here.

Take a look at the spectrogram from the Virgo detector below? See the signal? If you’re looking at the bright thing just right of center, you’re actually looking at a glitch that occurred right after the signal! Soon, we will be adding data from the Virgo interferometer to the Gravity Spy project, so we can help to better the sensitivity of this instrument, just like what Gravity Spy has been doing for the two LIGO instruments.

Also, we have finally figured out and updated our statistics page with the correct retirement information! Take a gander at our progress here.

-Mike & the Gravity Spy team

 

V1_GSGW170814_spectrogram_0.5.png

Advertisements

GW170104 – the third GW event!

Hi Gravity Spiers,

Today we announced the detection of the third confidently-observed gravitational wave event – GW170104. It was detected on January 4 2017, as the name suggests! It’s the most distant black hole merger detected to date.

We have a surprise waiting for you on the Gravity Spy project, try doing a few classifications and see if you can find the event for yourself…

Best,
Mike

 

blackhole-merger-locations.jpg

Great Press for Gravity Spy!

The Gravity Spy project has recently been featured in a couple great places! Check out a recent article about the project in LIGO magazine as well as a shoutout for the project on NASA’s Education Express newsletter!

Screen Shot 2017-03-17 at 8.39.21 AM.png

New data from LIGO’s second observing run

Dear Gravity Spiers, 

Gravity Spy has recently hit a new milestone – over one million classifications! Thank you for all your hard work so far – we are humbled by you continued enthusiasm. All these classifications have helped uncover new glitch classes in the data from LIGO’s first observing run, and have bolstered the labeled datasets that we use to train machine learning algorithms. 

Now for some more good news! LIGO started its second observing run at the end of 2016 and is still collecting data and searching for more gravitational-wave events. We are happy to announce that we have added the data from this observing run (O2) and the preceding engineering run (ER10) to the Gravity Spy project. As the detector has evolved a great deal over the past year, we expect many new types of glitches in this dataset. Furthermore, we will now upload new glitches to the project every few days as LIGO records them, so there should be no shortage of data to look through! Your classifications and analysis will be a massive help to LIGO scientists, and help us to uncover even more of the gravitational-wave universe. 

You may also notice that we’ve added two new categories to choose from – ‘1080 Line’ and ‘1400 Ripple’. As we find more prominent glitches in O2, we’ll add more glitch options to choose from.

All the best,

-Mike and the GSpy Team

Glitches associated with phone accidentally left plugged in at LHO

PhoneGltch.png

Hi GSpy users,

At LIGO Hanford we recently discovered that some of the telephones in the large experimental areas of LIGO were accidentally left switched on during a a couple of weeks of O2 data collection up to December 13 when they were switched off. At least once these phones rang and the ringtone made loud sounds (glitches) show up in microphones but also in the gravitational-wave channel data. Attached is an O2-preview of what this glitch will look like in GravitySpy data. We am worried that there might be other times in the data set for O1 and O2 when a phone at one of the sites was on. We would be very interested to learn whether any of you have seen glitches similar to this in the GravitySpy data set so far?

For more information, see this LIGO Hanford logbook post, including wave files, https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32503.

-Josh

O2 has started – get ready for new glitches!

LIGO’s second observing run (O2) started this morning – on November 30th 2016 at 8 am, pacific time. Get ready for some new glitches! We’ll have new data from the engineering run (ER10) and the first few days of O2 by the end of the week.

Who knows, maybe there’ll be a gravitational wave in there too!

Update after 1 week of launch

Hi everyone,

It has been one week since our full public launch, and we couldn’t be happier with the awesome participation! We’ve had over 200,000 classifications already, and thanks to everyone’s work on classifications and on talk, we are starting to see new categories emerge through talk, which will be added to the workflows in the near future. One of this is being hashtagged as #1400ripple:

b00d1038-f19e-4b97-bbc6-f11eb49ef7a8.png

Also, it looks like both LIGO site will (finally!) be coming back online and doing science over the next month – so we’ll have much more data and new glitches to classify. Thanks for everyone’s continued support!