Ada Lovelace National Girls' Programming Contest 2021 - Preliminary Rules and Policies

Rules for the Contestants:

  1. After the start of the contest, a contestant will not communicate or attempt to communicate with anyone other than her teammates.

  2. It is encouraged for each of the participants to read the problem statements carefully. Contestants should go through the problem descriptions, input formats, output formats and the constraints thoroughly.

  3. The solution of a problem must be written in a single file in a language that is available for this contest. For the full list of languages available for this contest, please see point 12. The solution of a problem can be submitted using Toph’s problem-specific submission form.

  4. If not stated otherwise in the specific problem, the input should be taken from the standard input stream. Similarly, the output should be written to the standard output stream if not stated otherwise.

  5. A team can submit solutions for a problem as many times as necessary. However, if the Ardent Programmers’ Judge Panel or the Toph authority identifies any attempt to destabilize the platform, the judges hold the complete right to disqualify any teams who are responsible for the attempt.

  6. A team must not make deliberate attempts to obfuscate their solutions. If the judges encounter such obfuscation, the team will be disqualified from the contest.

  7. Each team will receive login credentials before the contest. A team must not share the credentials outside of its own team members.

  8. A team will not be able to participate from multiple accounts. However, a team can log in from multiple workstations using the credentials given to them.

  9. During the time of the contest, teams are not allowed to use any Q&A sites including, but not limited to: StackOverflow, Quora for any type of assistance. If the judges find proof of any such activities, they hold the right to disqualify a team during or after the contest.

  10. A team can use online language reference sites like cppreference.com for receiving syntax related information. However, syntax-related support must not be received from any Q&A sites or forums as mentioned above. A team can also take support from printed books, documents or self-curated coding templates, if necessary.

  11. If a code submitted by the participants matches with other teams or matches with any code that is available online, judges hold the right to disqualify all the teams that are associated with this match. If a team uses a publicly available code template, then they should do it bearing the aforementioned condition in mind.

  12. The problems of the contest can be submitted using the languages: C, C++, Java and Python. A team must choose the correct version of the language from the drop-down page of Toph’s Submission System. Detailed options and specifications of the available versions of these languages can be found here: https://toph.co/languages

  13. If a contestant does not understand the problem statement clearly, she can use Toph’s clarification system to ask specific questions regarding the statement. However, a contestant must not ask for ideas related to the solution of a problem or test cases related to a problem.

  14. If a team has a problem-specific clarification request, the team should choose the problem from the drop-down list of Toph’s clarification system carefully. A contestant should also check the previous clarification requests of a specific problem to avoid duplicate clarification requests.

  15. Contestants are encouraged to report any issues regarding the platform or the dataset during the contest using Toph’s clarification system. However, the participants are requested to avoid clarification requests that are repetitive or that have been responded to earlier.

  16. If a contestant uses abusive or improper terms in the clarification system, the judges hold the right to disqualify the team.

  17. If disrespectful and derogatory comments are found in a team’s submitted codes, they will be considered for disqualification.

  18. Teams are not encouraged to use online editors or IDEs other than Toph’s online IDE. This is to avoid scenarios where other teams might get access to others’ codes.

  19. Teams should ensure updated browsers to get the best experience on Toph. A list of supported browsers and their versions can be found here: https://help.toph.co/toph/minimum-requirements/

  20. Judges’ decisions will be final.

Contest Policies:

  1. The Ada Lovelace National Girls Programming Contest 2021 will be hosted online on Toph.

  2. The problem-set of the contest will be provided by Ardent Programmers.

  3. The contest will take place for 5 hours and will have 10-12 problems of varying difficulty and concept. The statements of the problems will be written in English. Statements of each of the problems can be accessed from Toph Arena after the start of the contest. A booklet containing all the statements of the contest will also be available after the start of the contest.

  4. Each problem will include the problem’s name, description, input format, output format, constraints and sample test cases. Optionally, some problems may have explanations for some of the sample cases. For interactive problems, descriptions of how to interact with the system will be specified in the problem statement. For more information regarding interactive problems, please refer to the following link: https://help.toph.co/toph/interactive-problems

  5. The limits of allocated memories and CPU limits will be mentioned for each of the problems. The source code limit for each problem will be 64KB.

  6. After submitting a solution, a participating team will receive one of the following verdicts: “Accepted”, “Wrong Answer”, “Runtime Error”, “Compilation Error”, “CPU Limit Exceeded” or “Output Limit Exceeded”. The verdict “Accepted” is what a team is aiming for. The “Accepted” verdict indicates that a team has managed to solve the problem correctly. Explanations of all the other verdicts can be found under specific submissions on Toph. Explanations about the verdicts can also be found here: https://help.toph.co/toph/how-are-submissions-evaluated/

  7. The contest will follow the ICPC-style scoring while judging a problem. A submission will have to correctly solve all the test cases within the given constraints of a problem in order to achieve the “Accepted” status for that problem. If a team manages to solve a problem, 20 minutes of penalty time will be added for each of the wrong submissions on that problem. Additionally, the number of full minutes taken to solve the problem successfully for the first time will be added with the penalty. Please note that the penalties will be added for a problem only after the “Accepted” status is achieved for that problem. For example, if a team solves a problem in the 79th minute after two failed submissions, then the total penalty for that problem will be 78 + 40 = 118. But if a team makes three incorrect attempts to solve the problem and does not manage to solve it eventually, no penalties will be added.

  8. The dataset for each of the problems will be comprehensive. Participants should expect the “worst-case” scenarios in the dataset according to the constraints of the problems. Despite the best effort of the judges, if it is found out that the dataset of a specific problem is weak or erroneous, the judges will update the dataset and will re-judge each submission that was judged incorrect before the mistake was found. In cases where a re-judgment is made, an announcement will be given to all the participants using Toph’s announcement system.

  9. Judges will go through all the clarification requests that were made by the contestants during contest time. After reading each of the clarifications, judges may decide to respond to that request. They may also decide to ignore that request by pressing the “Ignore” button from Toph’s Judge Console. However, if the judges decide to respond to a clarification, it will be made available to all the participants of the contest using Toph’s notification system.

  10. The rank list of a contest will be ordered by the following conditions:

    a. A team that has solved more problems will be placed ahead of the teams that solved fewer problems.
    b. If two teams have solved the same number of problems, then the team that has the fewer penalties will be placed ahead.
    c. If two are still tied with the same number of solutions and same penalties, then the team that has made the latest successful submission earlier will be placed ahead.

  11. The rank list will be frozen during the last 60 minutes of the contest. It will be published publicly during the prize-giving ceremony of the contest. A frozen rank list will not show any position updates of any teams after the fourth hour of the contest. However, all the teams will continue to receive their own verdicts during the final hour of the contest.

  12. After the contest, all the submissions for each of the teams will be tested for possible plagiarism attempts. Each of the submissions will be examined thoroughly to detect any misconduct that might have taken place during the coding phase. Multiple layers of automated and manual tests will be executed to detect the teams who are involved with plagiarism. Finally, these teams will be removed from the official rankings.