This is a private hackathon open to Futarians, If you would like to participate, contact 08166700905.

This challenge was designed by AI community FUTA, Specifically for AI community FUTA Monthly Competition, which takes place 23-28 May. Welcome to the AI Community participants!

Deep sea marine invertebrates are frequently long-lived, slow growing and have limited to zero mobility. As a result of these life history characteristics they are known to reflect the changing climate of the ecosystem. They frequently have wide tolerance ranges as they are unable to rapidly move away from unfavourable conditions. For this reason, marine invertebrates are considered good indicators of long-term ecosystem health. In a changing ocean environment it is likely that marine invertebrates will provide early warning signs through reduced biodiversity, along with dramatic increases of a few species for which the changes are beneficial.

Marine invertebrates living on South Africa’s seafloor are meticulously collected, measured and photographed annually during research trawl surveys. Individual invertebrates are photographed in isolation, especially if identification thereof is uncertain, enabling identification at a later stage. Identification of each individual in each image is a laborious effort and is still required. Once the species have been identified, the data are added to a South African marine invertebrates database. Any species not previously encountered are also being added to a field guide to improve taxonomic knowledge of the region.

Teams are challenged to develop an automated image classification solution for photographs of marine invertebrate taken by researchers in South Africa. This will substantially reduce the manual image processing efforts of the team and enable them to detect any changing patterns in marine invertebrates much faster by reducing the need for human intervention in sample processing and evaluation.

Watch a SAEON team out in the field collecting data.

About Developer Student Clubs FUTA (dscfuta.dev)

Helping students bridge the gap between theory and practice Google Developer Student Clubs are community groups for college and university students interested in Google developer technologies. Students from all undergraduate or graduate programs with an interest in growing as a developer are welcome. By joining a DSC, students grow their knowledge in a peer-to-peer learning environment and build solutions for local businesses and their community.

About Data Science Nigeria (www.datasciencenigeria.org):

Data Science Nigeria is a non-profit run and managed by the Data Scientists Network Foundation. Our vision is to accelerate Nigeria’s development through a solution-oriented application of machine learning in solving social/business problems and to galvanize data science knowledge revolution, which can position Nigeria to become the outsourcing hub for international Data Science/Advanced Analytics/Big Data projects, with opportunity to access at least 1% share of the global big data and analytics market, valued at $150b in 2017 ($203b in 2020).

We adopt a practitioner-led model where experienced and hands-on data scientists in Nigeria and in the Diaspora train and mentor young Nigerians through face-to-face, virtual coaching classes, project-based support and holiday boot camps funded by individuals and corporate organizations.

About South African Environmental Observation Network (SAEON) (http://www.saeon.ac.za/):

SAEON is a sustained, coordinated, responsive and comprehensive in situ South African Earth observation network that delivers long-term reliable data for scientific research and informs decision-making for a knowledge society and improved quality of life.

This is a private hackathon open to Futarians, If you would like to participate, contact 08166700905.

This challenge was designed by AI community FUTA, Specifically for AI community FUTA Monthly Competition, which takes place 23-28 May. Welcome to the AI Community participants!

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. Your models should not use any of the metadata provided.

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 30 submissions per day.

You may make a maximum of 150 submissions for this hackathon.

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 50% 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 50% 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 5 at the time the leaderboard closes, the host of this hackathon will reach out to you via the Zindi inbox to request your code. On receipt of the message, 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 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).

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 or points for 6 months (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 or Zindi points for the next six months.
• 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.This is a private hackathon open to Futarians, If you would like to participate, contact 08166700905.

This challenge was designed by AI community FUTA, Specifically for AI community FUTA Monthly Competition, which takes place 23-28 May. Welcome to the AI Community participants!

Teams and collaboration

You may participate in competitions as an individual.

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. Any code that is shared, must be made available to all competition participants through the platform. (i.e. on the discussion boards).

Datasets and packages

The solution must use publicly-available, open-source packages only. Your models should not use any of the metadata provided.

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

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

You are allowed to access, use and share competition data for any commercial,. 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 25 submissions per day.

You may make a maximum of 100 submissions for this hackathon.

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 50% 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 50% 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 5 at the time the leaderboard closes, the host of this hackathon will reach out to you via the Zindi inbox to request your code. On receipt of the message, 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 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).

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 or points for 6 months (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 or Zindi points for the next six months.
• 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.

The evaluation metric for this challenge is Log Loss.

Note that there are 137 classes (species of invertebrate). Values should be probabilities and can be between 0 and 1 inclusive. The probabilities do not need to add up to 1.

Your submission file should look like:

FILE           Pteraster_capensis   Porifera   Astropecten_irregularis_pontoporeus ...
00G9CO1.jpeg            1                0                    0
01TO3K4.jpeg            0.98             0.33                 0.78                                         
01YAQRV.jpeg            0.10             0.56                 0.21      

This is a learning competition. Aside from knowledge, there are no prizes for this competition.

Hackathon closes on 28 May 2021.

Final submissions must be received by 11:59 PM Nigerian time.

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