SPAR (South Pacific Algorithmic Rounds) (formerly ANZAC) is a series of practice contests for the ICPC. Any team of up to three students from a university or high school can take part. Both beginners and experienced competitors are welcome. The contest server is at contest.sppcontests.org.
2024 Schedule
Round | Date | Time | Format | Results |
1 | Sat 2 March | 12:00 – 17:00 AEDT | Full | Scoreboard |
2 | Wed 20 March | 17:15 – 18:45 AEDT | Sprint | Scoreboard |
3 | Wed 27 March | 17:15 – 18:45 AEDT | Sprint | Scoreboard |
4 | Sat 27 April | 12:00 – 17:00 AEST | Full | Scoreboard |
5 | Sat 6 July | 12:00 – 17:00 AEST | Full | |
6 | Wed 24 July | 17:15 – 18:45 AEST | Sprint | Scoreboard |
7 | Wed 31 July | 17:15 – 18:45 AEST | Sprint | Scoreboard |
8 | Sat 17 Aug | 12:00 – 17:00 AEST | Full* |
SPAR 8 is a simultaneous mirror of the New Zealand Programming Contest.
2024 Awards
In each round, medals were allocated to high performing teams. The top one-twelfth of teams in each round earned Gold, the top one-quarter Silver and the top one-half Bronze.
Teams who earned a particular medal or higher in at least three rounds are recognised below, and will receive certificates by email.
Award | Team Name | Affiliation | Nationality |
---|---|---|---|
Gold | sushipizza | UNSW Sydney | AUS |
Gold | caterpillow | North Sydney Boys High School | AUS |
Gold | prog4pain | University of Canterbury | NZL |
Gold | DC | Australian National University | AUS |
Gold | goods | UNSW Sydney | AUS |
Silver | teamskelly | UNSW Sydney | AUS |
Silver | syntaxation | UNSW Sydney | AUS |
Silver | amoonguss | Monash University | AUS |
Silver | iason | UNSW Sydney | AUS |
Silver | CAA9000 | University of Canterbury | NZL |
Silver | CommissionFees | The University of Western Australia | AUS |
Silver | Chicken Extinction | UNSW Sydney | AUS |
Silver | Sprinkle Forces | The University of Adelaide | AUS |
Bronze | sqrt | UNSW Sydney | AUS |
Bronze | !DirectCurrent | University of Wollongong | AUS |
Bronze | Idle1 | UNSW Sydney | AUS |
Bronze | InvasiveSpecies | Monash University | AUS |
Bronze | Code_Runnings | University of Melbourne | AUS |
Bronze | noodlequacks second edition | University of Canterbury | NZL |
Bronze | UPC2 | ||
Bronze | herobrine overdose | University of Auckland | NZL |
Bronze | MegaKangaskhan | The University of Sydney | AUS |
Bronze | O(n!) | UNSW Sydney | AUS |
Bronze | Hanoi Is Purple | University of Adelaide | AUS |
Bronze | lemon | UNSW Sydney | AUS |
Bronze | Graters | University of Melbourne | AUS |
Bronze | Recompile.org | University of Auckland | NZL |
Bronze | IBARB0 | University of Adelaide | AUS |
Bronze | kty | University of Adelaide | AUS |
Bronze | yousoro | UNSW Sydney | AUS |
Registration
Register your team by filling out the Google Form (under construction).Your site coordinator is the person responsible for overseeing the site you’ll compete at (typically a university academic or school teacher).
- Make an account for your team on the DOMjudge server, where the contests will be conducted.
- Note that the link is slightly different from last year (so do not insert
/domjudge
in the URL). - For the registration fields:
- ‘Username’ and ‘Password’ are used for login
- ‘Full name’ and ‘Email address’ can be one of the team members (but aren’t necessary)
- ‘Team name’ is how your team name will appear on the scoreboard
- Please use an existing affiliation if possible.
- At the start of the contest, you will be sent a clarification in the bottom right of the screen, asking for some details about your team. Reply to this clarification at your earliest convenience.
- Note that the link is slightly different from last year (so do not insert
- On the day of the contest, attend a live site at a university or school, or participate online.
- Each site will be overseen by a site coordinator (typically a university academic or school teacher). We are in the process of preparing a centralised list of sites, but for now we advise you to follow any instructions circulated by staff at your institution.
Using the same DOMjudge account throughout the year will help us distribute awards to the top achievers.
Registrations from last year will not roll over to this year.
Rules
- Site coordinators will aim to provide at least one copy of the problem set per team, in addition to the PDF and sample data on the contest server.
- Teams must use only one computer, one keyboard and one monitor.
- Teams may use their own devices.
- At live sites, teams without one copy of the problem set per team member may use additional monitors only to view the problem set.
- Teams competing remotely should use their own devices and arrange an informal system to claim and unclaim use of the keyboard.
- Teams may use any amount of paper reference material. This includes books and printed notes.
- Teams may use pens and paper, for developing and discussing solutions among themselves.
- Teams should not use the internet other than to access the contest server (under construction) and contest website (this website).
- Teams may print code from their computer, if it is supported at the site they attend.
- Teams must not discuss the problems with people outside the team during the contest. Any questions must be sent through the DOMJudge clarification system.
- Electronic devices (phones, tablets etc) must not be used during the contest.
- All submitted code must have been entirely typed during the contest.
- Teams using their own devices may not copy and paste existing code; these must be re-typed instead.
- Generative AI tools cannot be used.
- To solve a problem, teams should submit source code through the DOMjudge system written in C, C++, Java or Python. The only feedback teams will receive is “compile error”, “run error”, “time limit exceeded”, “wrong answer” or “correct”.
- Details of the scoreboard, documentation and judging environment are available on the Technical Specifications page.
- Any teams found to be cheating will be removed from the contest server.