SUST Inter-University Programming Contest 2023 Rules for the Contestants

  1. After the start of the contest, a contestant will not communicate or attempt to communicate with anyone other than his/her teammates. However, a contestant may ask for assistance to the volunteers who are available in the contest room.
  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. 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: Languages | Toph
  9. If a contestant does not understand the problem statement clearly, they 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.
  10. 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.
  11. 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.
  12. If a contestant uses abusive or improper terms in the clarification system, the judges hold the right to disqualify the team.
  13. If disrespectful and derogatory comments are found in a team’s submitted codes, they will be considered for disqualification.
  14. Multi-threading can not be used to solve a problem during the contest.
  15. A team should request up to 30 pages of printing during the contest. If they need to print more that this limit, they must contact with judges through the clarification system. A team should not take more than 10 pages of printing in one request. However, a team must not print any part of the problem set.
  16. A team should take up to 25 pages of printed material with them. Prints should only be taken on one side of the page. The format of the printed paper should either be A4 or Letter.
  17. And the cliché, the decision of the judges will be final.