Coral Classification Challenge
Can you classify types of coral?
Prize
$800
Time
Ended 8 months ago
Participants
44 active ยท 139 enrolled
Helping
South Africa
Advanced
Classification
Conservation
Description

Due to human impact and the rise in climate change, coral reefs and the health of its inhabitants are in a dire situation. Reef Support aims to aid this situation and bring relief to an already hurt ecosystem.

The objective of this challenge is to use machine learning to identify the type of coral in an image and whether it is healthy or not.

A solution like this could help organizations like Reef Support and Ocean Innovation Africa scale coral conservation efforts in Africa and around the world.

Your solutions will be used by the Ocean Hackathon.

About the Ocean Hackathon® Cape Town:

For the first time since the creation of the Ocean Hackathon® in 2015, an African city is on the world map of the 15 cities competing simultaneously to solve challenges faced by the oceans, using essentially data.

Ocean Hackathon® Cape Town will take place as part of this year’s Ocean Innovation Africa event. The African chapter of the Ocean Hackathon® will take place over 48 hours straight from the 5th to the 7th of November 2021, at the V&A Waterfront, with data scientists, project managers, web developers, marine scientists and communication specialists forming 9 teams of up to 6 hackers.

Supported by data scientists and coaches, the teams will have to tackle one of the 3 selected ocean-impact data challenges:

The participants will stand a chance to win one of the cash prizes and to represent Cape Town at Ocean Hackathon® Grand Final, in France, in December 2021.

The registration link: https://ocean-innovation.africa/the-event/hackathon/

Links about the Hackathon:

Presentation of challenges:

We invite you all to consider volunteering as a coach/mentor. The coaches give guidance to the teams on subjects such as:

  • Software development, IT, data treatment
  • Project management, promotion, pitch training, business model
  • intellectual property

The coaches are not assigned to a specific team. However, duos of coaches will be designated to follow each team during the Hackathon and liaise with other coaches in person or online.

The coaches do not necessarily have to be available throughout the whole event. A programme of attendance will be established and the schedule will be communicated to the participants. The coaches who have the same expertise will take turns during the event.

The coaches can provide tutorials and best practices documents to help the teams.

The highlights for the local coaches during the event are:

  • Coaches' online meeting 2 days before the event: to explain the methodology of the event
  • Coaches meetings:
- Briefing meeting on 5th November afternoon
- Meeting on 6th November afternoon to exchange about the projects
- Meeting on 7th November afternoon to brief the jury before the teams pitch their projects
  • Checkpoints: At least one checkpoint a day with the teams to follow up on their progress
  • Rehearsal; On 7th November morning, teams are invited to rehearse their pitch in "real conditions" and test their presentation

The coaches will be also asked to evaluate the projects on:

  • The quality of the artefact
  • The data use
  • The business model
  • The environmental and societal dimension

Apply as a coach here.

About Reef Support (reef.support)

Reef support is a Dutch start-up that focuses on building software to accelerate the transition from data to decisions to protect coral reefs. Their mission is to take practical action and support the blue economy with imagery and artificial intelligence. They aim to accomplish it by building robust research and predictive maintenance tools for research institutions, reef managers and other coastal activities – from small conservation efforts to large-scale coastal developments.

About Ocean Innovation Africa (ocean-innovation.africa)

Africa offers a particularly high potential in terms of Blue Economy developments, paving the way to ocean community-based resource management and offering an ideal ground to test and scale impact innovation. Africa's ocean economy – three times the size of its landmass – is on top of the continent's political agenda and seen to be a major contributor to continental transformation and growth of industries such as fisheries and aquaculture, marine renewables and biotechnologies, boat building and shipping, coastal tourism and ocean-sports, etc.

The development of the Blue Economy is an immensely important first step towards creating Sustainable Development pathways and this is what Ocean Innovation Africa event (OIA) promotes. The platform showcases African initiatives and brings together entrepreneurs, investors, scientists, businesses and leaders that are working from around the world towards the development of a more sustainable ocean economy.

Ocean Innovation Africa Summit 2021 (ocean-innovation.africa/the-event)

We believe that innovations led by science, technology, and entrepreneurship will provide the necessary leverage points to address the Sustainable Development Goals (SDG), at the right pace and scale. By addressing the issues of sustainable Oceans economy and Oceans conservation, our event seeks to find solutions linking up to almost all SDGs in addition to SDG14 – Life Below Water.

Our focus stems from a passion and the need for efficient, impactful action: at the current pace, SDGs objectives would only be met by 2094 instead of 2030! Oceans are the heart and lungs of our planet, it is crucial – and now urgent – to support the development and adoption of new sustainable ocean solutions that will shape better interactions between people and the Earth’s largest ecosystem. In the recovery of the recent COVID-19-related crisis, Oceans have also a key role to play by keeping trade moving between nations and providing sustainable energy and healthy food for all.

Rules

Teams and collaboration

You may participate in competitions as an individual or in a team of up to four people. When creating a team, the team must have a total submission count less than or equal to the maximum allowable submissions as of the formation date. A team will be allowed the maximum number of submissions for the competition, minus the total number of submissions among team members at team formation. Prizes are transferred only to the individual players or to the team leader.

Multiple accounts per user are not permitted, and neither is collaboration or membership across multiple teams. Individuals and their submissions originating from multiple accounts will be immediately disqualified from the platform.

Code must not be shared privately outside of a team. Any code that is shared, must be made available to all competition participants through the platform. (i.e. on the discussion boards).

The Zindi user who sets up a team is the default Team Leader. The Team Leader can invite other data scientists to their team. Invited data scientists can accept or reject invitations. Until a second data scientist accepts an invitation to join a team, the data scientist who initiated a team remains an individual on the leaderboard. No additional members may be added to teams within the final 5 days of the competition or the last hour of a hackathon, unless otherwise stated in the competition rules

A team can be disbanded if it has not yet made a submission. Once a submission is made individual members cannot leave the team.

All members in the team receive points associated with their ranking in the competition and there is no split or division of the points between team members.

Datasets and packages

The solution must use publicly-available, open-source packages only.

You may use only the datasets provided for this competition. Automated machine learning tools such as automl are not permitted.

If the challenge is a computer vision challenge, image metadata (Image size, aspect ratio, pixel count, etc) may not be used in your submission.

You may use pretrained models as long as they are openly available to everyone.

The data used in this competition is the sole property of Zindi and the competition host. You may not transmit, duplicate, publish, redistribute or otherwise provide or make available any competition data to any party not participating in the Competition (this includes uploading the data to any public site such as Kaggle or GitHub). You may upload, store and work with the data on any cloud platform such as Google Colab, AWS or similar, as long as 1) the data remains private and 2) doing so does not contravene Zindi’s rules of use.

You must notify Zindi immediately upon learning of any unauthorised transmission of or unauthorised access to the competition data, and work with Zindi to rectify any unauthorised transmission or access.

Your solution must not infringe the rights of any third party and you must be legally entitled to assign ownership of all rights of copyright in and to the winning solution code to Zindi.

Submissions and winning

You may make a maximum of 10 submissions per day.

You may make a maximum of 50 submissions for this competition.

Before the end of the competition you need to choose 2 submissions to be judged on for the private leaderboard. If you do not make a selection your 2 best public leaderboard submissions will be used to score on the private leaderboard.

Zindi maintains a public leaderboard and a private leaderboard for each competition. The Public Leaderboard includes approximately 20% of the test dataset. While the competition is open, the Public Leaderboard will rank the submitted solutions by the accuracy score they achieve. Upon close of the competition, the Private Leaderboard, which covers the other 80% of the test dataset, will be made public and will constitute the final ranking for the competition.

Note that to count, your submission must first pass processing. If your submission fails during the processing step, it will not be counted and not receive a score; nor will it count against your daily submission limit. If you encounter problems with your submission file, your best course of action is to ask for advice on the Competition’s discussion forum.

If you are in the top 20 at the time the leaderboard closes, we will email you to request your code. On receipt of email, you will have 48 hours to respond and submit your code following the submission guidelines detailed below. Failure to respond will result in disqualification.

If your solution places 1st, 2nd, or 3rd in the final ranking, will NOT be required to assign rights of copyright to Zindi. We will however encourage the winners to share their code on GitHub as a public good to the sector.

If two solutions earn identical scores on the leaderboard, the tiebreaker will be the date and time in which the submission was made (the earlier solution will win).

If the error metric requires probabilities to be submitted, do not set thresholds (or round your probabilities) to improve your place on the leaderboard. In order to ensure that the client receives the best solution Zindi will need the raw probabilities. This will allow the clients to set thresholds to their own needs.

The winners will be paid via bank transfer, PayPal, or other international money transfer platform. International transfer fees will be deducted from the total prize amount, unless the prize money is under $500, in which case the international transfer fees will be covered by Zindi. In all cases, the winners are responsible for any other fees applied by their own bank or other institution for receiving the prize money. All taxes imposed on prizes are the sole responsibility of the winners. The top 3 winners or team leaders will be required to present Zindi with proof of identification, proof of residence and a letter from your bank confirming your banking details.Winners will be paid in USD or the currency of the competition. If your account cannot receive US Dollars or the currency of the competition then your bank will need to provide proof of this and Zindi will try to accommodate this.

Payment will be made after code review and an introductory call with the host.

You acknowledge and agree that Zindi may, without any obligation to do so, remove or disqualify an individual, team, or account if Zindi believes that such individual, team, or account is in violation of these rules. Entry into this competition constitutes your acceptance of these official competition rules.

Zindi is committed to providing solutions of value to our clients and partners. To this end, we reserve the right to disqualify your submission on the grounds of usability or value. This includes but is not limited to the use of data leaks or any other practices that we deem to compromise the inherent value of your solution.

Zindi also reserves the right to disqualify you and/or your submissions from any competition if we believe that you violated the rules or violated the spirit of the competition or the platform in any other way. The disqualifications are irrespective of your position on the leaderboard and completely at the discretion of Zindi.

Please refer to the FAQs and Terms of Use for additional rules that may apply to this competition. We reserve the right to update these rules at any time.

Reproducibility of submitted code

  • If your submitted code does not reproduce your score on the leaderboard, we reserve the right to adjust your rank to the score generated by the code you submitted.
  • If your code does not run you will be dropped from the top 10. Please make sure your code runs before submitting your solution.
  • Always set the seed. Rerunning your model should always place you at the same position on the leaderboard. When running your solution, if randomness shifts you down the leaderboard we reserve the right to adjust your rank to the closest score that your submission reproduces.
  • We expect full documentation. This includes:
  • All data used
  • Output data and where they are stored
  • Explanation of features used
  • A requirements file with all packages and versions used
  • Your solution must include the original data provided by Zindi and validated external data (if allowed)
  • All editing of data must be done in a notebook (i.e. not manually in Excel)
  • Environment code to be run. (e.g. Google Colab or the specifications of your local machine)
  • Expected run time for each notebook. This will be useful to the review team for time and resource allocation.

Data standards:

  • Your submitted code must run on the original train, test, and other datasets provided.
  • If external data is allowed, external data must be freely and publicly available, including pre-trained models with standard libraries. If external data is allowed, any data used should be shared with Zindi to be approved and then shared on the discussion forum. Zindi will also make note of the external data available on the data page.
  • Packages:
  • You must submit a requirements file with all packages and versions used.
  • If a requirements file is not provided, solutions will be run on the most recent packages available.
  • Custom packages in your submission notebook will not be accepted.
  • You may only use tools available to everyone i.e. no paid services or free trials that require a credit card.

Consequences of breaking any rules of the competition or submission guidelines:

  • First offence: No prizes for 6 months and 2000 points will be removed from your profile (probation period). If you are caught cheating, all individuals involved in cheating will be disqualified from the challenge(s) you were caught in and you will be disqualified from winning any competitions for the next six months and 2000 points will be removed from your profile. If you have less than 2000 points to your profile your points will be set to 0.
  • Second offence: Banned from the platform. If you are caught for a second time your Zindi account will be disabled and you will be disqualified from winning any competitions or Zindi points using any other account.
  • Teams with individuals who are caught cheating will not be eligible to win prizes or points in the competition in which the cheating occurred, regardless of the individuals’ knowledge of or participation in the offence.
  • Teams with individuals who have previously committed an offence will not be eligible for any prizes for any competitions during the 6-month probation period.

Monitoring of submissions

  • We will review the top 20 solutions of every competition when the competition ends.

We reserve the right to request code from any user at any time during a challenge. You will have 24 hours to submit your code following the rules for code review (see above). Zindi reserves the right not to explain our reasons for requesting code. If you do not submit your code within 24 hours you will be disqualified from winning any competitions or Zindi points for the next six months. If you fall under suspicion again and your code is requested and you fail to submit your code within 24 hours, your Zindi account will be disabled and you will be disqualified from winning any competitions or Zindi points with any other account.

Evaluation

The evaluation metric for this challenge is Accuracy.

Your submission file should look like this:

Image_ID           label   
ImageID_OXGFPVDK   Algae   
ImageID_2O917SYP   Hard Coral
Prizes

The prize for this challenge is a travel grant of up to 12,000 ZAR (the equivalent of approximately $800 USD) to attend the Ocean Innovation Africa Summit in Cape Town 5-9 November 2021 in person.

Note that this travel grant will be awarded only after the Summit. Reimbursement will be made for train, plane, and/or accommodations, up to the maximum amount and based on receipts.

The travel grant is non-transferable. We reserve the right to award the prize to the top participant that is able to travel to attend the Summit in person.

If you are not able to attend the event in person, you are encouraged to participate virtually.

There are 1000 Zindi Points for this challenge.

Timeline

Competition closes on 31 October 2021.

Final submissions must be received by 11:59 PM GMT.

We reserve the right to update the contest timeline if necessary.