New Zealand Informatics Competition
NZIC Contest Rules
These are subject to change until each contest begins.
There will be official scoreboards for individual students and an informal one for schools.
Each student will be ranked for the year based on a weighted sum of their round 1-3 scores. The higher scores will have a larger weighting than lower scores.
The scoring system is subject to change at the discretion of the contest administrator.
Cheating and inappropriate behaviour
Breaching the rules will result in instant disqualification.
Inappropriate behaviour involves being dishonest, taking advantage of our systems, or acting in a way that is not in the spirit of the competition. Behaviour is determined to be inappropriate by the contest administrator and will be dealt with at their discretion. In particular, the NZIC is an individual competition and collaboration between competitors is strictly forbidden. The offending account(s) may be deleted and the student(s) may be disqualified.
Any person who is currently enrolled in a New Zealand secondary or intermediate school. Non-eligible students may still compete but they will not be offically ranked.
Each contest will be held online. After logging into https://train.nzoi.org.nz/, the contest will appear at the start time. When ready, students may start the contest. The 3 hours will begin at that time. The problems will be visible on the contest page, and submissions may be made from there. To submit a solution, students submit the source code, which will be compiled and executed on the judging system.
After the submission is judged, the results will appear immediately. Students may use this to fix any bugs. There are no guarantees on how long it might take for the submission to be judged, if there are a large number of submissions made at the same time.
Please note that with Java, the source code will be put in a file called
Main.java, so submissions must use a class named
Local editors and compilers
The editors and compilers on local machines may vary from school to school, depending on what is available, including the operating system installed on the computers.
We suggest that schools have at least a basic text editor (such as Gedit or Notepad++). The compiler may vary depending on the language, but for C++, gcc/g++ is suggested as this is what is used for judging. For Windows, Dev-C++ is a light-weight fully featured editor/IDE and compiler that is probably the easiest to install. It is also much easier to use as new users have trouble setting up projects in Visual Studio or Eclipse.
For power users, we suggest that the compiler be made available on the command line. This is already the case with Linux operating systems. For Windows, for which cmd.exe lacks many features and is difficult to use, MinGW (including a port of GCC) is recommended along with MSYS as a command-line interface. Cygwin is not recommended because it may be too slow. The compile command used by the online judging software is displayed on the results page after submitting a solution.
Documentation and other material during the contest
While competing, students may only access the https://train.nzoi.org.nz/ website, or an official (static) language documentation site (language documentation installed locally may also be used). Electronic language documentation (but not source code) stored locally is also permitted. Forums or interactive websites are strictly forbidden.
Students may also use any printed material during the contest, including language documentation, textbooks or source code. These materials may not be shared.
Students may not access or use any electronically stored source code, whether it is stored locally or on the internet. This includes source code written by the student prior to the contest. All source code submitted must be written during the contest, without any collaboration with others.
Students may ask a supervisor questions on administrative tasks, such as, when the contest ends or how to use the website to make a submission.
Questions such as how to solve a problem, how use a language feature, or where a bug is in a program will not be answered. The student should be able to find out how to use a language feature by reading the language documentation.
If a student is new to a programming language, we suggest that they bring printed sample source code for reference.
Any questions related to the problems should be emailed to firstname.lastname@example.org for a response.