The exoplanet imaging data challenge will consist of two consecutive stages, each one with its own type of submission and metrics.

Stage 1

Deadline 1st of June 2020

The expected output from an algorithm (i.e. the submission from a given participant), consists of:

  • All the detection maps (9 for the first ADI sub-challenge and 10 for the second ADI+mSDI sub-challenge);
  • One detection threshold for all the maps (1 value per sub-challenge), which is the threshold from which a detection is claimed;
  • Optionally, the FHWM values used for each dataset can be submitted (the FWHM is related to the expected size of a candidate detection - or resolution element - in the detection maps).

Every file must be in .FITS format

All of these .fits files must be submitted within a single .zip file, with a flat structure.

One .zip file must be submitted for each sub-challenge (one for ADI and one for ADI+mSDI).

For example, for generating a submission file to the second sub-challenge (ADI+mSDI) you must compile the following files in .zip format (any name can be used):

  • detection_threshold.fits (scalar value, enclosed in a 1x1 vector-array),
  • gpi_detmap_1.fits (2d array),
  • gpi_detmap_2.fits (2d array),
  • gpi_detmap_3.fits (2d array),
  • gpi_detmap_4.fits (2d array),
  • gpi_detmap_5.fits (2d array),
  • sphere_ifs_detmap_1.fits (2d array),
  • sphere_ifs_detmap_2.fits (2d array),
  • sphere_ifs_detmap_3.fits (2d array),
  • sphere_ifs_detmap_4.fits (2d array),
  • sphere_ifs_detmap_5.fits (2d array).

Optionally, you can include:

  • gpi_fwhm_1.fits (scalar value),
  • gpi_fwhm_2.fits (scalar value),
  • gpi_fwhm_3.fits (scalar value),
  • gpi_fwhm_4.fits (scalar value),
  • gpi_fwhm_5.fits (scalar value),
  • sphere_ifs_fwhm_1.fits (scalar value),
  • sphere_ifs_fwhm_2.fits (scalar value),
  • sphere_ifs_fwhm_3.fits (scalar value),
  • sphere_ifs_fwhm_4.fits (scalar value),
  • sphere_ifs_fwhm_5.fits (scalar value).

Note: Each submission must correspond to the results of applying a single algorithm to all the datasets. If your algorithm works for both 3D and 4D datasets then you need to make two submissions (to have your score on each scoreboard). Please keep in mind that a partial submission for a given sub-challenge is possible, but that will penalize the metrics computations and your score.

Note: The detection threshold is one single value for all of the detection maps submitted. Also the threshold must be a 1x1 array containing the chosen scalar value.

Note: Please check out the documentation of the Astropy Python library if you want to know more about saving data in FITS format. Optionally, the VIP Python library contains a wrapper (vip_hci.fits.write_fits()) of Astropy for saving Python numpy arrays as FITS files.

Potential error message

Zipping the file: The zip file must be flat (i.e. without subfolder structure), please consider checking this aspect.

Space left on device: This error occurs when a compute worker is full, usually because it has too many docker images. If this happens, we have to contact CodaLab and clean the repository. Please notify us if you encounter such error (exoimg.datachallenge@gmail.com).

Other error message: Please contact us if you encounter any issue when submitting your results exoimg.datachallenge@gmail.com.

Stage 2

This expensive procedure will be performed locally, therefore the source code of the algorithm (implemented on an open source language such as Python or R), an executable file or a Docker image will be required from the participants. Additionally, each participant must submit a single detection threshold (per sub-challenge) to be used during the thresholding and blob counting procedures.

Important: this stage of the data challenge will only be conducted if enough participants demonstrate their interest in submitting/sharing their code.