There several policies that participant are required to consider in order to be included in the competition:

• All final submissions should be in the form of docker containers or a github repository and follow the template provided by the organizers to be tested successfully. 
• It is the user's responsibility to check the sanity of  their algorithm's docker during the preliminary test period before submitting it for the final test set.
• Only fully automated methods are accepted as the submission is in the form of docker containers. It is not possible to submit manual annotations or interactive methods.
• Submissions will be ranked solely based on their performance on the final test set and according to the criteria explained in the evaluation page.
• All performance results will be made public.
• All participants must form a team. If a single participant is taking part, they can form a team with a single user.
• Participants may join the challenge Slack workspace
• Teams can have multiple submissions on the preliminary test set to verify the quality of their methods. However, the number of submissions per day per team and for each task is limited to 1 in order to restrict test data hacking. If a team makes multiple submissions per day (from different users) in the preliminary test phase, they will be disqualified. 
• Anonymous registration is NOT allowed. Any information entered when registering a team must be accurate, including the (TRUE) name of the contact person, the affiliation (including department, university/institute/company, country), and any E-mail addresses.
• For the final test set, only the last submission will be considered for the challenge results.
• Members from the organizing team may participate but not eligible for awards.
• To be considered for the post challenge publication, teams must make their algorithm available (on GitHub repo). An appropriate license may be selected.