General Rules

1. The competition is open to UT ECE and Computer Science majors.
2. Teams must consist of one or two people
3. Teams are not allowed to discuss challenges with each other or collaborate on solving problems in any way
4. The competition is active between 19 Mar. 2008 9:00 PM Central and 23 Mar. 2008 11:59 PM Central
5. There are 100 possible points obtainable in the competition. Details on obtaining points will be discussed at the kick-off on 19 Mar. 2008
6. Results for the competition will be unveiled and prizes will be presented at the keynote lecture on 26 Mar. 2008
7. Prizes are final and detailed on the Prizes page

Requirements:

The contest will be open to five languages to accommodate the participants. The languages are as follows:


1. C/C++ (GCC 1.4.2 )
2. Java (Sun SDK 1.5.0)
3. Ruby 1.8.5
4. Python 2.4.3

Your submitted solutions will be invoked on the command line on the ECE or CS Linux machines. This means you cannot submit a Visual Studio project or a Java application with a GUI. Along with your submission, include a README file that provides instructions for compiling and running your code.

Submissions:

Teams will submit their solutions to the IEEE Computer Society's Challenge website. All submission files MUST be a zip, gzipped or bzip2 tarball of your solution. In addition to submitting source code solutions, you will be required to provide a solution for a given test case on the website. Each team will only be allowed to submit ONE solution per problem. The submission website will not accept your source code until the correct answer has been given for the problem.

We advise that you do not wait till the last minute to submit because if you don't have the correct answer to the given test case, your source file will not be accepted. After you have answered a problem correctly and submitted the corresponding source code, you will not be able to update or resubmit new code for this problem.

Judging:

Each programming puzzle will be graded against test cases that will not be available to participants. It is your responsibility to test your code for corner cases in addition to verifying your solution returns the correct result for the given sample test cases. Any submissions that error during run time or do not compile will not be debugged (or graded) Each puzzle is worth 20 points of the your total grade, but the puzzles are not the same level of difficulty. Contestants are responsible for determining the difficulty of each programming puzzle and should allocate their time so that they can achieve the most points possible.