This is a private hackathon. In order to enter you must be currently enrolled as a university student in Tunisia. Please register here: https://bit.ly/2KdaA7O by midnight 25 December 2020.
Please check out this link: https://fb.me/e/4K6wUXCRm for more details about the event.
Please contact iheb.sliti.5@gmail.com if you have any additional questions.
As customers express their thoughts and feelings more openly than ever before, sentiment analysis is becoming an essential tool to monitor and interpret customer sentiment from online posts. Automatically analyzing customer feedback, such as opinions in survey responses, social media conversations, and product reviews, allows brands to learn what makes customers happy or frustrated, so that they can tailor products and services to meet their customers’ needs. In Tunisia, companies such as banks and insurance companies and even global companies like Google, could benefit from automating sentiment analysis, but would struggle to set such a system up due to the complexity of our Arabic dialect.
For this task, we have collected reviews from Tunisian Apps on Google play. The objective of this challenge is to, given a review, classify whether the review is of positive, negative, or neutral sentiment.
About Developer student clubs
Developer Student Clubs are university based community groups for undergraduate students interested in Google developer technologies. They focus on solving real life problems using modern technologies.
This is a private hackathon. In order to enter you must be currently enrolled as a university student in Tunisia. Please register here: https://bit.ly/2KdaA7O by midnight 25 December 2020.
Teams and collaboration
You may participate in this competition 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 highest 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 disqualified.
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).
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.
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 200 submissions per day. Your highest-scoring solution on the private leaderboard at the end of the competition will be the one by which you are judged.
Sliti Iheb will reach out to the winners via the Zindi inbox. You will have 24 hours from the direct message to submit your code for review. Zindi reserves the right to disqualify any user, team if the code does not reproduce the winning submission. We encourage winners to share their solutions on Github and the discussion board.
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.
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.
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.
The metric for the classification tasks will be Accuracy.
Submission files should contain 2 columns: ID and score (1:positive, 0: neutral, -1: negative).
Your submission file should look like this (numbers to show format only):
ID score
356 -1 19 0
In order to win, you must be currently enrolled as a student at a Tunisian university.
1st Place: 600 DT
2nd Place: 400 DT
3rd Place: 200 DT
All times are local time in Tunisia (GMT+1).
Competition opens on 26 December 2020 at 8:00 PM.
Competition closes on 27 December 2020 at 8:00 PM.
The private leaderboard will be revealed on 27 December 2020 at 8:00 PM.
We reserve the right to update the contest timeline if necessary.