Code#

Cafe_OS v2.0

1. Eligibility

  • Institutional Requirement: This competition is open strictly to students currently enrolled in the School of Computing and Information Systems (SCIS) at Singapore Management University (SMU).
  • Disqualification: Submissions from individuals who are not current students of SCIS at SMU will be automatically disqualified.

2. Contest Format & Participation

  • Duration: The competition will run for 24 continuous hours.
  • Problem Set: Participants will be faced with a set of algorithmic challenges.
  • Submission Limit: You may submit solutions as many times as you like within the 24-hour window. There is no limit on the number of attempts.
  • Confirmation of Participation: You are officially deemed a participant the moment your first submission is uploaded to HackerRank. Once this action is taken, you are bound by all rules and regulations strictly.

3. Integrity & Resources Policy

To ensure a fair test of fundamental algorithmic logic, we enforce specific strict rules on resource usage.

3.1 Prohibited Actions (The “Black List”)

  • NO AI Tools: The use of ChatGPT, Gemini, GitHub Copilot, Claude, Tabnine, or any other Generative AI is STRICTLY PROHIBITED.
  • NO Regular Expressions (RegExp): The use of Regular Expression libraries or objects (e.g., import re in Python, <regex> in C++, RegExp objects/literals in JS) is BANNED. You must solve parsing problems using algorithmic logic.
  • NO Active Asking: You are NOT allowed to post the competition questions, ask for help, or start new threads on StackOverflow, Reddit, Discord, or any other forum during the contest.
  • NO Collaboration: You may not discuss solutions with other participants or non-participants.

3.2 Permitted Resources (The “White List”)

  • String Methods: Standard string manipulation methods built into the language (e.g., .split(), .find(), .substring(), .indexOf()) are PERMITTED.
  • StackOverflow (Read-Only): You are allowed to search for and read existing threads on StackOverflow to troubleshoot errors or look up syntax.
  • Documentation: Official language documentation (e.g., Python Docs, CppReference, MDN) is permitted.
  • Personal Code: You may reuse code snippets or templates you have personally written prior to the competition.

4. Technical Environment

  • Platform: The competition is hosted entirely on HackerRank.
  • Submission Method: All code must be submitted directly through the HackerRank interface. Submissions sent via email, Telegram, or other means will not be accepted.
  • Supported Languages: All major programming languages supported by HackerRank are allowed.
  • Libraries:
    • Only Standard Libraries are allowed.
    • External dependencies (e.g., numpy, pandas, boost) are not available.
  • Input/Output: Solutions will be tested against pre-defined test cases on the HackerRank platform.

5. Scoring & Ranking

  • Partial Scoring: Points are awarded based on the number of test cases your solution passes. You do not need a “perfect” solution to earn points for a problem.
  • No Penalties: There is no negative marking or time penalty for failed submissions. You are encouraged to iterate and improve your code.
  • Tie-Breakers: In the event of a tie in total points, rank will be determined by the Time of Completion (the timestamp of the submission that achieved your final highest score).

6. Consequences & Organisers’ Rights

6.1 Right to Disqualify & Revoke

The organisers reserve the absolute right to disqualify any participant and revoke any prizes won (including demanding the return of distributed prizes) should anyone be suspected of cheating or violating the spirit of the competition.

6.2 Cheating Definition

Cheating includes, but is not limited to:

  • Using AI tools.
  • Plagiarism of code from other participants or online sources (outside of permitted documentation).
  • Collaboration with others.
  • Attempting to bypass the “No RegExp” rule.

6.3 Dispute Resolution

  • Investigation: If suspected, participants are obliged to provide their submission history and any other information required by the organising team.
  • Final Decision: The organisers have the final say on all disputes.

7. Code of Conduct

By participating in Code# 2026, you agree to abide by the [SMU/SCIS Code of Conduct]. We are dedicated to providing a harassment-free experience for everyone.

Effective Date: 22 January 2026

Last Updated: 22 January 2026