Rules
Programming Language
Programs may be submitted in Astarte, Java or C++
Teams
A team is any subset of
students at ECU, working together to solve one or more of the
programming challenges.
Teams can have any number of members, and can overlap in any way.
For example, student Carlos Codecrusher might submit solutions as a
singleton team, but also be part of another team consisting of himself
and two friends who are just starting to program.
Each team should have a name. The name can be any (up to) 32
standard keyboard characters. Keep it decent... Teams
should also have one contact email address for feedback from their
submissions.
Scoring - Each Challenge
Each team will receive (12 - 2n)
points for that challenge, where n
is the number of submissions the team needed to make in order to solve
the challenge. A program is said to solve the challenge if it
compiles, runs and gives the correct answers within 10 seconds.
Scoring - Cumulative Standings
Each team's cumulative score will be the average of their scores on the
five most recent challenges. For teams which did not submit a
solution to some challenge, their score will be considered to be '0' on
that challenge for purposes of computing cumulative scores.
Rankings will be updated after each challenge.
Note that as long as there have not yet been five challenges, the
average will be taken over all challenges so far.
Timeouts
Some challenges will be designed so that a brute-force approach will
simply take too long, meaning that some cleverness will be
required. To force cleverness, a ten-second limit will be imposed
on all solutions.
Files
Programs will not have access to the filesystem. All I/O will be
conducted through the standard input and standard output.
Back to challenge homepage.