The Alberta Collegiate Programming Contest (ACPC) is an opportunity for university and college students in Alberta to excel in a programming competition.
Students will test their aptitude and their knowledge of computer science against a set of programming puzzles requiring problem-solving, programming, math, and teamwork skills. Teams are ranked according to the number of problems solved within five hours. The event will begin on November 19th with a warm-up practice, followed by a five-hour competition to decide the winners.
The ACPC is sponsored by Arcurve who provides a platform for the next generation of computing professionals to pursue excellence.
A practice contest is provided to allow contestants to become familiar with the Kattis judging system:
Below are the links to the contest for each division.
Make sure you are doing the contest for the division you registered under on Eventbrite.
|
|
Anyone is welcome to compete.
In order to be eligible for prizes, you must be:
- Enrolled in a post-secondary institution/high school in Alberta as an undergraduate/full time graduate student.
- If you are a post secondary student, you must register with your school email and university ID
- If you are a high school student, you must register with your student ID
- In a team of up to three members
- Participating in the same division as everyone else on your team
- Please note: high school students are STRONGLY encouraged to register in Division 2.
- (Extra requirement for Division 2) Students who have not taken (or not currently taking) a data structures course, i.e. CPSC 319/331
Register on Eventbrite.
The registration deadline is on 10:45PM on Wednesday, November 23rd.
The contest is set for Saturday, November 19th, 2022.
In Calgary, the contest will be held in the CPSC lab on the main floor of the Math Science building at the University of Calgary.
The currently planned schedule is as follows:
10:00AM - 10:15AM
- Coffee and Mingling
10:15AM - 10:30AM
- Contest Rules in ICT 122
10:30AM - 11:15AM
- Practice Contest in the CPSC lab
10:45AM - 11:30AM
- Lunch will be served
11:30AM - 4:30PM
- Official Contest
4:30PM - 4:45PM
- Solutions to Problem Set
4:45PM - 5:30PM
- Arcurve Presentation & Awards Ceremony + Door Prizes
Teams of up to three students enrolled in an Albertan educational institution, meeting the criteria linked to in the "Eligibility" section above may compete for prizes. Teams not meeting these requirements may participate as guests. The contest is free of charge for entry; lunch will be provided to official competitors at the Calgary location.
The contest itself is a collection of 6-10 problems to be solved using C, C++, Java, Python. Team rankings are decided first by number of problems solved, and second by time taken to solve.
During the contest, the following rules are in effect:
- No collaboration is allowed with anyone outside of your team members when working on/discussing the contest problems.
- All contestants can work on their personal computer. Any team member can submit a solution to Kattis.
- Resource access is restricted to standard library and language documentation, the contest website, and the I/O cheat-sheet (linked below)
- External libraries are not allowed. For example, the C++ header '#include <math.h>' is allowed since it is a part of the language's standard library. However, headers in an external C++ library such as Boost are not allowed.
- Coding reference material
- Each team is allowed one coding reference "document"
- There is no maximum page limit for the coding reference document
- Document submission options:
- Each option will count as one document (i.e. you can choose either i or ii)
- Teams creating their own document (option i) cannot share their document with other teams or people within the contest
- Create your own
- Each team can make their own document and email it to cpc.uofc@gmail.com. You can also host the files on a private GitHub and share it with the club executives. Make sure all reference code is committed by the date in the point below.
- Reference a public, pre-existing code library
- You are allowed to reference an already available public GitHub code library (i.e. created by official coaches from a university), with proof of permission. The link to the repository must be emailed to cpc.uofc@gmail.com, along with proof of permission from the repository owner.
- It must be emailed to at least cpc.uofc@gmail.com or have the repository shared with us at least 12 hours before the contest start date (by 10:30PM, November 18th).
- Important note: For GitHub reference material, code committed only at least 12 hours before the contest can be used.
- Aside from the two main points above, all other references materials on the internet are not allowed
- Use of electronic devices other than the computer is strictly prohibited
- Teams are ranked according to which has solved the most problems, with ties broken by time taken to solve
The main contest will start at 11:30PM MDT on Saturday, November 19th. The practice contest starts one hour before the main contest and will last 45 minutes. Participation in the practice is optional but recommended for new competitors.
Any disrespectful behavior towards the Competitive Programming Club, our sponsors or participants can result in disqualification from the event.
Permissible Internet resources:
- Contest page
- C reference
- C++ reference 1
- C++ reference 2
- Java 6 reference
- Python reference
- All other internet resources are prohibited.
If you want a leg up on the competition, there are some preparation opportunities available:
- In Calgary, the Competitive Programming Club meets every Tuesday from 18:00 - 20:00 at MS160 on the main floor of the Math Science building at the University of Calgary.
- The UVa Online Judge contains many programming puzzles for self-directed practice
Some time-tested strategies for during the competition:
- Read all the problems, identify the easy ones, and solve them first
- If you're having trouble identifying easy problems, look at the scoreboard to see what others are solving
- Computer time is very valuable, so sketch out your program on paper before coding it (unless it's trivially simple)
- Debugging a program on paper is more effective than sticking print statements everywhere, 99% of the time
- Come up with your own test cases for your program, especially edge cases
Arcurve Website | Twitter | Facebook
CPC Website | Facebook | Twitter | Mailing list
UofA Website
UofL Website
.png){kind=spacer}