1. Commonwealth of Virginia Community Colleges and High Schools Programming & Game Programming Competitions & RU Local Programming Competition
SPONSORED BY
COLLEGE OF SCIENCE AND TECHNOLOGY, RADFORD UNIVERSITY
IBM, ACM
DR. BOB PHILLIPS, DR. ANDREW RAY
APRIL 23~24, 2010

2. Please Join me to thanks to those who make this event happen
Dean Dr. Orion Rogers for his leadership and support
Chair Dr. Art Carter for support and allowing to use department facilities (labs, etc...)
Dr. Chen-Chi Shing for serving as the head judge for Game Programming Competition
Dr. Edward Okie for serving as the head judge for Programming Competition
Dr. Joe Chase for serving as RU Ambassador
Drs. Andrew Ray, Ian Barland, Prem Uppuluri, and Ms. Kathy Anderson as judges
Ms. Kathy Anderson for system management
Ms. Joyce Dalton for all kinds of work
From ACM RU chapter, President Alex Meade, Webmaster Andrew Melton, Treasurer Stephanie Reese, and other Volunteers
Karen MCPherson
Caitlin Minteer
Kelly Clynes
Damien Allen
Jason Dowd
Chris Cook
Bill Burton
Joran Clark
Brooks Wornick
Tim Jones
Susan Rogers
Sean Gunter

3. Contestants are not to converse with anyone except members of their team and personnel designated by the Contest Director.

4. Systems support staff may advise contestants on system-related problems such as explaining system error messages. Support staff will not answer questions pertaining to contest problems, compilers, editors, etc.
Any conversation between contestants on different teams (whether they are from the same or different universities) or with the Faculty Advisor or the team Coach is strictly forbidden.

5. The contest will be held in a networked environment.
The network may only be used to submit problems and to produce a listing in ways designated by the Head Judge and system support staff.

6. Remote login, ftp, telnet, mail or other networking activities within the contest environment or with machines outside this environment are strictly forbidden.
Any contestant who discovers a security leak must report this leak immediately to a system support staff member.

7. While the contest is scheduled to last exactly three hours, the Contest Director has the authority to lengthen the contest in the event of unforeseen difficulties.
Should the contest duration be altered, every attempt will be made to notify contestants in a timely and uniform manner.

8. A team may be disqualified by the Contest Director for any activity that jeopardizes the Contest, such as dislodging extension cords, unauthorized modification of contest material (software or hardware), forbidden network activity, or destructive behavior. The disqualification may occur immediately upon detection or up to 72 hours after the end of the Contest. If a team is disqualified for any reason, all awards must be surrendered.

9. At least six problems will be posed
At least six problems will be posed. As far as possible, problems will avoid dependence on detailed knowledge of a particular applications area or a particular contest language.
The Contest Director is solely responsible for ruling on unforeseen situations and interpreting these rules for the Contest.

10. SCORING THE CONTEST
The Contest Judges are solely responsible for determining the correctness of submitted runs.
In consultation with the Judges, the Contest Head Judge is responsible for determining the winners of the Contest.

11. The judging staff is empowered to adjust for or adjudicate unforeseen events and conditions.
Their decisions are final and may not be appealed.

12. Teams are ranked according to the most problems solved.
For the purposes of awards, or in determining qualifier(s) for the Contest Finals, teams who solve the same number of problems are ranked by least total time.

13. The total time is the sum of the time consumed for each problem solved.
The time consumed for a solved problem is the time elapsed from the beginning of the contest to the submittal of the accepted run plus 20 penalty minutes for every rejected run for the problem, regardless of submittal time.
There is no time consumed for any problem that is not solved.

14. It is the responsibility of the Contest Director to specify any tie-breakers if necessary.

15. Contact Persons Dr. Maung Htay, Director Dr. Lee, Assistant Director
Dr. Shing, Head Judge of Game Programming Comeptition
Dr. Edward Okie, Head Judge of Programming Competition
Ms. Kathy Sacklin, Systems Administrator

16. Agenda 9:00 - 9:30 AM Registration (Davis Hall 212)
9: :00AM Welcome Session (Davis Hall 212)
10: :00 AM Environment Training & Practice Session
(Davis Hall 225)
11: :00 PM Lunch (Dalton Hall)
12:00 - 3:00 PM Contest (Davis Hall 225)
3:00 - 3:30 PM Demonstration of Games to All Students
(Davis Hall 201)
3:30 – 4:00 PM Award Ceremony (Davis Hall 212)

17. Good Luck