Juilfs Programming Competition Rules
Juilfs Programming Contest
Saturday, June 3, 2017
10:00 AM - 2:00 PM
The programming contest will take place in the CIS Computing Lab in Deschutes Room 100. The contest itself will be approximately three hours long starting when all teams have submitted the practice problem. Each team should bring a notebook computer (one per team) on which they will code and test their program solutions.
The contest will begin promptly at 10:00 AM with a practice problem so contestants can make sure they know how to submit a solution. Contestants should be there at least a few minutes early to find their teammate and choose a place to work. Light refreshments will be provided.
Remember that this is intended to be a fun competition!
Contest Policies and Rules
- Resources
-
Each team can use only a single notebook computer.
If neither team member has a computer of their own,
the team may use one of the iMac workstations in the lab.
You may also use any written or printed material that
you have brought to the competition.
- Teams should make sure they have installed and configured the programming tools (e.g., Java or C++ compiler, Python interpreter, editors) that they plan to use for programming problem solutions.
- You may access the internet during the contest. However, any code you submit should be your own. Wireless access is available throughout Deschutes, but the team should configure their machine prior to the contest if it is not already configured for the uowireless network.
- Format of Competion
- The contest will consist of five problems. Each problem will be worth some number of points as specified in the problem description. The more points, the harder the problem is likely to be. The winning team will be the team with the most points. In the event of a tie, the winning team will be the first to have submitted the final correct solution.
- Programming Languages
- Problem solutions may be coded in C, C++, Java, or Python. The language versions are GCC 4.8, G++ 4.9, Java 1.7, Python 2.7, and Python 3.4.
- Submission of Solutions
-
Solutions will be submitted in source form and
should be named by the single letter (or letter
and digit) identifying the problem and an extension
indicating the type of program, e.g., A.cpp or
A.java or A.py.
Each solution must consist of just a single source
file, although that source file may contain many
class and function definitions. In the case of Java,
there must be exactly one public class and its name
must agree with the source file name.
To submit a problem solution, click this submit link. You will choose a problem, and browse to your program source code to submit for the problem solution. If you have not logged in yet as a team, you will be prompted to do so.
- Scoring
- Each submitted solution that is correct will earn the specified number of points for the problem. Ranking is determined by the point total of the correct solutions which have been submitted. However, each incorrect solution submitted for a problem that is eventually solved correctly will incur a penalty of one point subtracted from the total, so it is important to only submit a solution when you are fairly certain that it is correct.
- Judging
- Your submission is in source code form. Depending on the language, your solution will be compiled by the judges, and then run with some test input data (which may be more extensive than the sample given in the problem description). Your program must produce the correct output for the test data, and cannot execute for longer than two minutes. You will be notified of the judges' result on the results whiteboard in room 100. The result will be whether your solution is correct or not. Sometimes additional information will be given, e.g., your program did not compile, or the execution time limit was exceeded.
- Problem Description Clarifications
- You may request clarifications of the problem statement. These should not be frivolous questions, or questions that try to get hints for a solution; they should be legitimate questions to clarify problem wording or assumptions. Clarification requests may be submitted by writing the request on a notepad that will be provided in the contest room. Clarifications will be written on the big whiteboard in room 100.
- Contest Duration
- The contest will end three hours after the official start.
- Work Areas
- The contest will take place in Deschutes Room 100. During the contest, contestants are not to converse with anyone except members of their team and judges.
- Contest Scoreboard
- Submission results will be displayed on the results whiteboard in room 100. The team rankings will be released immediately after all last minute submissions are judged.
The first time you use the submit web interface, you must supply a team login and password. Team logins are assigned as shown below. Passwords are the same as the logins.
The full URL for the submit script is: http://www.cs.uoregon.edu/Activities/Juilfs_Contest/submit.cgi
cwilson@cs.uoregon.edu
Last updated 2013/05/01