UIU Inter-University Programming Contest
2025 Rulebook
The Department of Computer Science and Engineering (CSE) at United International University
(UIU) is thrilled to host the 1st UIU Inter-University Programming Contest 2025, set to take place
on January 17-18, 2025! This exciting event will unite talented programmers from universities
across Bangladesh, offering a challenging platform to demonstrate their programming and
problem-solving prowess.
Registration Eligibility :
Participants must be currently enrolled students from an accredited university or IOI
(International Olympiad in Informatics) students. Each team must consist of 3 members and one
coach. After the final slot distribution, 150 teams will compete at UIU IUPC 2025.
Registration:
After the final slot distribution, Teams must register online by the specified deadline. No changes
to team composition are allowed after registration closes. The registration fee is 5000 BDT.
Event:
Registration Closes: January 05, 2025
Shortlisted Teams Announcement: January 10, 2025
Last Date for Registration Payment: January 12, 2025
Mock Contest: Friday, January 17, 2025
Final Contest: Saturday, January 18, 2025
Venue for the Mock and Final Contest:
United International University (UIU)
United City, Madani Ave, Dhaka 1212, Bangladesh
Contest Format:
Duration: The contest will last for 5 hours.
Problems: Teams will be given 8-12 programming problems of varying difficulty.
Languages: The allowed programming languages are C, C++, Java, and Python3.
Environment: The contest will be conducted on BAPS OJ. Each team will have a single
account provided by the organizers.
General Rules of Contest
1. Solutions to problems submitted for judging are called runs. Each run is judged
as accepted or rejected by the judge, and the team is notified of the result. Only
source code should be submitted, not the executables or any other files.
2. The contest will be held on bapsoj online judge. Only this website will be
accessible from the contestant’s pc. Any attempt to access other websites or the
Internet will result in disqualification. Any attempt to tamper with the online judge
will also result in disqualification.
3. Teams must participate in the MOCK contest and report to the volunteer if they
face any problems. Each team will be given the same machine in the same
location during the mock and main contest.
4. A contestant may submit a clarification request to the judges only through
bapsoj’s clarification system. If the judges agree that an ambiguity or error exists,
a clarification will be issued to all contestants. Judges may decide not to answer
a clarification at all in which case that particular clarification request will be
marked as IGNORED on the bapsoj clarification page.
5. If teams believe that there is something wrong with the judge data, they are
strongly advised to use the bapsoj clarification system to communicate with the
judges rather than meeting them in person after the contest.
6. Contestants are not to converse with anyone except members of their own team
and personnel designated by the organizing committee while seated at the team
desk. They may not even talk with their team members when they are walking
around the contest floor to have food or any other purposes.
7. While the contest is scheduled for a particular time length (five hours), the
judging panel in consultation with the contest director can alter the length of the
contest in the event of any unforeseen difficulties. Should the contest duration be
altered, every attempt will be made to notify contestants in a timely and uniform
manner.
8. A team may be disqualified for any activity that jeopardizes the contest such as
dislodging extension cords, unauthorized modification of contest materials,
distracting behavior, or communicating with other teams. The judges can also
recommend penalizing a team with additional penalty minutes for their distracting
behavior.
9. 8-12 problems will be posted. So far as possible, problems will avoid
dependence on detailed knowledge of a particular application area or particular
contest language.
10. Rank-list will be frozen in the final hour of the contest. During this period, teams
will only get the verdict of their own submissions.
11. Contestants cannot leave the contest arena during the contest without explicit
permission from the judges/invigilators. The contestants are not allowed to
communicate with any other contestants (even contestants of the same team) or
coaches when they are outside the contest arena. If a team decides to leave the
contest venue for the day while the contest is still running, it must inform the
judges/invigilators first. No single member of a team will be allowed to leave the
contest venue for the day while other member(s) are still there.
12. Teams can bring a printed Team Reference Document (TRD). This document
may contain up to 25 pages of reference materials, single-sided, letter or A4 size.
Each page must be numbered in the upper right-hand corner and your university
name and team name printed in the upper left-hand corner. Text and illustrations
must be readable by a person with correctable eyesight without magnification
from a distance of .5 meter. It may include hand-written comments and
corrections on the fronts of pages only. The backside of each page must be
completely empty. No other hardcopy documents (including books) will be
allowed.
13. Teams need to submit the Team Reference Document to the host volunteers on
the opening day for inspection. Teams will receive it back on the next day before
the main contest starts. If any team fails to do so, their document may reach the
team desk late due to inspection delay.
14. Teams are not allowed to bring any electronic devices like calculator, CD, DVD,
Pen-drive, iPod, MP3/MP4 players, floppy disks, watches(smart, digital, analog),
etc. Teams CANNOT bring their own keyboard, mouse, etc.
15. Teams can only touch the workstation after the contest has started.
16. With the help of the volunteers and judges, the contestants can have printouts of
their codes for debugging purposes. Passing printout of codes to other teams is
strictly prohibited and may cause disqualifications of the teams involved.
17. Teams need to seek the attention of volunteers to print codes during the contest.
In each command, a team can ask for a printout of up to 10 pages. A team can
ask for printouts up to 50 pages in total.
18. Teams should inform the volunteers/invigilators/judges if they don’t get any
verdict/reply within 10 minutes of submission/clarification. Teams should also
notify the volunteers if they cannot log into bapsoj. These sorts of complaints will
not be entertained after the contest.
19. Codes must not use any system command or use multi-threading. Contestants
must not attempt to access any other computers other than their own in the
network. Violating these rules may result in disqualification.
20. Teams using Java and Python should be extra careful about TL and ML, since
problems are not tested with Java and Python.
21. Any member of a team, if late, may not be allowed to enter the contest arena
AFTER THE START OF THE CONTEST.
22. The decision of the judges is final.
Available Languages (in Bapsoj): C, C++, Java, and Python3.
Prizes:
First Prize: 150,000 BDT
Second Prize: 100,000 BDT
Third Prize: 50,000 BDT
4th - 10th Prizes: 10,000 BDT each (7 prizes)
For any queries
Md. Tashin Parvez
Md. Mostafizur Rahman
Associate, Competitive Programming Wing
Head, Competitive Programming Wing
Programming Wing, UIU Computer Club
Programming Wing, UIU Computer Club
Contact:
Contact:
+8801954449226
+8801521773834
[email protected]
[email protected]
Thank You
