The competition is held in high schools on the second Friday in June. As far as possible the event is conducted 2pm-4pm AEST, though variations of up to 90 minutes in the start time may be requested.
Registrations and ProgComp itself are managed through the cupcake service.
Schools that have obtained access to cupcake for practice can register competition teams after they open. Competition teams are competely separate from practce teams:
Teams log on to cupcake, making sure they select Competition as the team type. It doesn't matter if they are a few minutes late, as the 120 minutes begins when they open the first task.
As each task is solved, the output corresponding to each supplied data file, and the source code for the program, must be pasted into the relevant text boxes on the task web page and submitted.
There is a small, undisclosed grace period when the 120 minutes are up, to allow for any delays when hundreds of teams are trying to make their final submission. Do not rely on this period to do any development or testing, it can evaporate without warning. No late submissions are accepted.
Students will need to be online throughout the competition to access the tasks and to submit their solutions and test results. There are five tasks plus one or two Junior tasks (see below). Teams may not use the internet during the competition apart from accessing the cupcake website and any sites linked directly from it. It is expressly forbidden to use web searches to obtain information of any kind about the problems to be solved.
Teams can incorporate any software written beforehand by the members, or obtained from third parties provided the source is disclosed in the submitted code.
The ProgComp organisers recognise that only a small number of teams are in the running for the Grand Final, but everyone deserves a chance at competing, and completing at least a few tasks. Accordingly, there are (usually) two Junior-level tasks, and the open tasks are graded progressively more difficult.
All teams may attempt any of the tasks, but there are restrictions on how many tasks of each type can contribute to the team score, depending on the team's level (that's determined by the year of the most senior member). Details will be provided here soon.
Competitors and supervisors should refrain from discussing the tasks with others until the conclusion of the competition. Under no circumstances may any of the materials be released to third parties without the written consent of the competition organisers.
The registered supervising teacher is responsible for ensuring and certifying that the competition is conducted and submitted under all of these rules.
Authorised by Head,
School of Computer Science and Engineering
UNSW CRICOS Provider Code 00098G, ABN 57 195 873 179
NSW 2052 Australia