Tag Archives: Zooniverse

Exoplanet Explorers Discoveries – A Sixth Planet in the K2-138 System

This is the first of two guest posts from the Exoplanet Explorers research team announcing two new planets discovered by their Zooniverse volunteers. This post was written by Jessie Christiansen.

Hello citizen scientists! We are here at the 233rd meeting of the American Astronomical Society, the biggest astronomy meeting in the US of the year (around 3000 astronomers, depending on how many attendees are ultimately affected by the government shutdown). I’m excited to share that on Monday morning, we are making a couple of new exoplanet announcements as a result of your work here on Zooniverse, using the Exoplanet Explorers project!

Last year at the same meeting, we announced the discovery of K2-138. This was a system of five small planets around a K star (an orange dwarf star). The planets all have very short orbital periods (from 2.5 to 12.8 days! Recall that in our solar system the shortest period planet is Mercury, with a period of ~88 days) that form an unbroken chain of near-resonances. These resonances offer tantalizing clues as to how this system formed, a question we are still trying to answer for exoplanet systems in general. The resonances also beg the question – how far could the chain continue? This was the longest unbroken chain of near first-order resonances which had been found (by anyone, let alone citizen scientists!).

At the time, we had hints of a sixth planet in the system. In the original data analysed by citizen scientists, there were two anomalous events that could not be accounted for by the five known planets – events that must have been caused by at least one, if not more, additional planets. If they were both due to a single additional planet, then we could predict when the next event caused by that planet would happen – and we did. We were awarded time on the NASA Spitzer Space Telescope at the predicted time, and BOOM. There it was. A third event, shown below, confirming that the two previous events were indeed caused by the same planet, a planet for which we now knew the size and period.

So, without further ado, I’d like to introduce K2-138 g! It is a planet just a little bit smaller than Neptune (which means it is slightly larger than the other five planets in the system, which are all between the size of Earth and Neptune). It has a period of about 42 days, which means it’s pretty warm (400 degrees K) and therefore not habitable. Also, very interestingly, it is not on the resonant chain – it’s significantly further out than the next planet in the chain would be. In fact, it’s far enough out that there is a noticeable gap – a gap that is big enough to hide more planets on the chain. If these planets exist, they don’t seem to be transiting, but that doesn’t mean they couldn’t be detected in other ways, including by measuring the effect of their presence on the other planets that do transit. The planet is being published in a forthcoming paper that will be led by Dr Kevin Hardegree-Ullman, a postdoctoral research fellow at Caltech/IPAC.

In the meantime, astronomers are still studying the previously identified planets, in particular to try to measure their masses. Having tightly packed systems that are near resonance like K2-138 provides a fantastic test-bed for examining all sorts of planet formation and migration theories, so we are excited to see what will come from this amazing system discovered by citizen scientists on Zooniverse in years to come!

We are also announcing a second new exoplanet system discovered by Exoplanet Explorers, but I will let Adina Feinstein, the lead author of that paper, introduce you to that exciting discovery.

Zooniverse Workflow Bug

We recently uncovered a couple of bugs in the Zooniverse code which meant that the wrong question text may have been shown to some volunteers on Zooniverse projects while they were classifying. They were caught and a fix was released the same day on 29th November 2018.

The bugs only affected some projects with multiple live workflows from 6th-12th and 20th-29th November.

One of the bugs was difficult to recreate and relied on a complex timing of events, therefore we think it was rare and probably did not affect a significant fraction of classifications, so it hopefully will not have caused major issues with the general consensus on the data. However, it is not possible for us to say exactly which classifications were affected in the timeframe the bug was active.

We have apologised to the relevant science teams for the issues this may cause with their data analysis, but we would also like to extend our apologies to all volunteers who have taken part in these projects during the time the bugs were in effect. It is of the utmost importance to us that no effort is wasted on our projects and when something like this happens it is taken very seriously by the Zooniverse team. Since we discovered these bugs we worked tirelessly to fix them, and we have taken actions to make sure nothing like this will happen in the future.

We hope that you accept our most sincere apologies and continue the amazing work you do on the Zooniverse. If you have any questions please don’t hesitate to contact us at contact@zooniverse.org.

Sincerely,

The Zooniverse Team

Zooniverse Data Aggregation

Hi all, I am Coleman Krawczyk and for the past year I have been working on tools to help Zooniverse research teams work with their data exports.  The current version of the code (v1.3.0) supports data aggregation for nearly all the project builder task types, and support will be added for the remaining task types in the coming months.

What does this code do?

This code provides tools to allow research teams to process and aggregate classifications made on their project, or in other words, this code calculates the consensus answer for a given subject based on the volunteer classifications.  

The code is written in python, but it can be run completely using three command line scripts (no python knowledge needed) and a project’s data exports.

Configuration

The first script is the uses a project’s workflow data export to auto-configure what extractors and reducers (see below) should be run for each task in the workflow.  This produces a series of `yaml` configuration files with reasonable default values selected.

Extraction

Next the extraction script takes the classification data export and flattens it into a series of `csv` files, one for each unique task type, that only contain the data needed for the reduction process.  Although the code tries its best to produce completely “flat” data tables, this is not always possible, so more complex tasks (e.g. drawing tasks) have structured data for some columns.

Reduction

The final script takes the results of the data extraction and combine them into a single consensus result for each subject and each task (e.g. vote counts, clustered shapes, etc…).  For more complex tasks (e.g. drawing tasks) the reducer’s configuration file accepts parameters to help tune the aggregation algorithms to best work with the data at hand.

A full example using these scripts can be found in the documentation.

Future for this code

At the moment this code is provided in its “offline” form, but we testing ways for this aggregation to be run “live” on a Zooniverse project.  When that system is finished a research team will be able to enter their configuration parameters directly in the project builder, a server will run the aggregation code, and the extracted or reduced `csv` files will be made available for download.

Experiments on the Zooniverse

Occasionally we run studies in collaboration with external  researchers in order to better understand our community and improve our platform. These can involve methods such as A/B splits, where we show a slightly different version of the site to one group of volunteers and measure how it affects their participation, e.g. does it influence how many classifications they make or their likelihood to return to the project for subsequent sessions?

One example of such a study was the messaging experiment we ran on Galaxy Zoo.  We worked with researchers from Ben Gurion University and Microsoft research to test if the specific content and timing of messages presented in the classification interface could help alleviate the issue of volunteers disengaging from the project. You can read more about that experiment and its results in this Galaxy Zoo blog post https://blog.galaxyzoo.org/2018/07/12/galaxy-zoo-messaging-experiment-results/.

As the Zooniverse has different teams based at different institutions in the UK and the USA, the procedures for ethics approval differ depending on who is leading the study. After recent discussions with staff at the University of Oxford ethics board, to check our procedure was up to date, our Oxford-based team will be changing the way in which we gain approval for, and report the completion of these types of studies. All future study designs which feature Oxford staff taking part in the analysis will be submitted to CUREC, something we’ve been doing for the last few years. From now on, once the data gathering stage of the study has been run we will provide all volunteers involved with a debrief message.

The debrief will explain to our volunteers that they have been involved in a study, along with providing information about the exact set-up of the study and what the research goals were. The most significant change is that, before the data analysis is conducted, we will contact all volunteers involved in the study allow a period of time for them to state that they would like to withdraw their consent to the use of their data. We will then remove all data associated with any volunteer who would not like to be involved before the data is analysed and the findings are presented. The debrief will also contain contact details for the researchers in the event of any concerns and complaints. You can see an example of such a debrief in our original post about the Galaxy Zoo messaging experiment here https://blog.galaxyzoo.org/2015/08/10/messaging-test/.

As always, our primary focus is the research being enabled by our volunteer community on our individual projects. We run experiments like these in order to better understand how to create a more efficient and productive platform that benefits both our volunteers and the researchers we support. All clicks that are made by our volunteers are used in the science outcomes from our projects no matter whether they are part of an A/B split experiment or not. We still strive never to waste any volunteer time or effort.

We thank you for all that you do, and for helping us learn how to build a better Zooniverse.

Celebrating Earth Day

Zooniverse team members based at Chicago’s Adler Planetarium celebrated Earth Day this weekend at Earthfest, a two-day-long celebration of the planet we call home.

Visitors to the Adler Planetarium participate in a Zooniverse hands-on activity during Earthfest
Visitors to the Adler Planetarium participate in a Zooniverse hands-on activity during Earthfest

In addition to many activities for all ages throughout the museum, museum visitors were able to speak with Zooniverse team members to learn about the many earth-related projects available online and on the app. Visitors could also participate in a real-life version of Floating Forests, in which they used tracing paper to illustrate areas of kelp forests on a satellite image. The activity demonstrated how Zooniverse researchers use aggregation to combine many classifications into one very accurate result. Stay tuned for the results of those tracings, coming soon!

Check out a few more photos from the event here.

Zooniverse team members also had some help from our friends at the Field Museum, who stopped by to talk about Microplants, a Zooniverse project studying some of the earliest land plants in the liverwort genus Frullania.

We love speaking with museum visitors and sharing the excitement of participating in real citizen science projects. If you’re in the Chicago area and missed us last weekend, keep an eye out for more information about the Adler Planetarium’s spring Members’ Night, when we’ll have even more fun Zooniverse-related activities for you!

Help the victims of Hurricane Irma

The Zooniverse has again been asked to enable The Planetary Response Network – this time in response to Hurricane Irma.
The US virgin Islands as seen from ESA’s Sentinel-2 satellite on 23rd August 2017. Pre-storm imagery like this is used to compare to post-storm images in order to spot major changes.
Irma has brought widespread devastation to many islands in the Caribbean over the last few days, and now Hurricane Jose is a growing threat in the same region.

 

By analysing images of the stricken areas captured by ESA’s Sentinel-2 satellites, Zooniverse volunteers can provide invaluable assistance to rescue workers. Rescue Global are a UK-based disaster risk reduction and response charity who are deploying a team to the Caribbean and will use the information you provide to help them assess the situation on the ground.

 

The last time The Planetary Response Network was brought online was to help in the aftermath of the 2016 Ecuador Earthquake. Back then over two thousand volunteers helped analyse almost 25,000 square kilometres of satellite imagery in only 12 hours, and we hope to be of help this time too!

 

Right now we have limited clear-sky images of the affected area, mostly around Guadeloupe, but we are working hard to upload images from the other islands as soon as possible.

 

Join the effort right now at www.planetaryresponsenetwork.org.

Pop-ups on Comet Hunters

pasted-image-at-2016_10_20-11_05-am

 

We’re testing out a new feature of our interface, which means if you’re classifying images on Comet Hunters you may see occasional pop-up messages like the one pictured above.

The messages are designed to give you more information about the project. If you do not want to see them, you have the option to opt-out of seeing any future messages. Just click the link at the bottom of the pop-up.

You can have a look at this new feature by contributing some classifications today at www.comethunters.org.

Emails from the Zooniverse

pasted-image-at-2016_09_16-02_48-pm
Click this image to be taken to your Zooniverse email settings

We’re cleaning up our email list to make sure that we do not email anyone who does not want to hear from us. You will have got an email last week asking you if you want to stay subscribed. If you did not click the link in that email, then you will have received one today saying you have been unsubscribed from our main mailing list. Don’t worry! If you still want to receive notifications from us regarding things like new projects, please go to www.zooniverse.org/settings/email and make sure you’re subscribed to general Zooniverse email updates.
NOTE: This has not affected emails you get from individual Zooniverse projects.

Asteroid Zoo Paused

The AsteroidZoo community has exhausted the data that are available at this time. With all the data examined we are going to pause the experiment, and before users spend more time we want to make sure that we can process your finds through the Minor Planet Center and get highly reliable results.

We understand that it’s frustrating when you’ve put in a lot of work, and there isn’t a way to confirm how well you’ve done. But please keep in mind that this was an experiment – How well do humans find asteroids that machines cannot?

Often times in science an experiment can run into dead-ends, or speed-bumps; this is just the nature of science. There is no question that the AsteroidZoo community has found several potential asteroid candidates that machines and algorithms simply missed. However, the conversion of these tantalizing candidates into valid results has encountered a speed bump.

What’s been difficult is that all the processing to make an asteroid find “real” has been based on the precision of a machine – for example the arc of an asteroid must be the correct shape to a tiny fraction of a pixel to be accepted as a good measurement. The usual process of achieving such great precision is hands-on, and might take takes several humans weeks to get right. On AsteroidZoo, given the large scale of the data, automating the process of going from clicks to precise trajectories has been the challenge.

While we are paused, there will be updates to both the analysis process, and the process of confirming results with the Minor Planet Center. Updates will be posted as they become available.

https://talk.asteroidzoo.org/
http://reporting.asteroidzoo.org/

Thank you for your time.

What is Penguin Watch 2.0?

We’re getting through the first round of Penguin Watch data- it’s amazing and it’s doing the job we wanted, which is to revolutionise the collection and processing of penguin data from the Southern Ocean – to disentangle the threats of climate change, fishing and direct human disturbance. The data are clearly excellent, but we’re now trying to automate processing them so that results can more rapidly influence policy.

In “PenguinWatch 2.0”, people will be able to see the results of their online efforts to monitor and conserve Antarctica’s penguins colonies. The more alert among you will notice that it’s not fully there yet, but we’re working on it!

We have loads of ideas on how to integrate this with the penguinwatch.org experience so that people are more engaged, learn more and realise what they are contributing to!

unnamed

For now, we’re doing this the old-fashioned way; anyone such as schools who want to be more engaged, can contact us (tom.hart@zoo.ox.ac.uk) and we’ll task you with a specific colony and feedback on that.