SPONSORED BY Department of Information Technology, College of Science and Technology,

1. Commonwealth of Virginia2013 Community Colleges and High Schools Programming & Game Programming Competitions& RU Local Programming Competition SPONSORED BY Department of Information Technology, College of Science and Technology, Radford University March 29, 2013

2. Please Join me in thanking thosewho help 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. Joe Chase for serving as RU Ambassador • Dr. Chen-Chi Shing for serving as the head judge for Game Programming Competition • Ms. Kathy Anderson, Mr. Travis Smith for system management • Ms. Joyce Dalton for all kinds of work • From ACM RU chapter, President Travis Smith, and Volunteers, Ben Pruitt, Jennifer Gay, and Brandyn Price.

3. Game Programming CompetitionAgenda • 7:00 - 7:15 PM Registration (McGuffey 206) • 7:15 - 7:30 PM Welcome Session (McGuffey 206) Prof. Htay and Prof. Chase • 7:30 - 8:30 PM Game Presentations (McGuffey 206) • 8:30 - 9:00 PM Game Playing (Davis Hall 225) • 9:00 – 9:15 PM Award Ceremony (McGuffey 206)

4. Contact Persons • Dr. Maung Htay, Director • Dr. Lee, Associate Director • Dr. Joe Chase, RU Ambassador • Dr. Shing, Head Judge of Game Programming Competition • Mr. Travis Smith, Systems Administrator

5. Game Programming CompetitionAgenda • 7:00 - 7:15 PM Registration (McGuffey 206) • 7:15 - 7:30 PM Welcome Session (McGuffey 206) • 7:30 - 8:30 PM Game Presentations (McGuffey 206) • PhOenix Ink • Tanks in JAVA • Monsters • 8:30 - 9:00 PM Game Playing (Davis Hall 225) • 9:00 – 9:15 PM Award Ceremony (McGuffey 206)

6. Have a safe trip back home~! 

7. End

8. Rules • No contestant may have completed two years of associate degree or hold an undergraduate degree in the field of Computer Science or Information Technology. • Students who have enrolled in a Community Colleges or High Schools of the Commonwealth of Virginia.

9. Each team competing in the VCC/HS Contest may make one substitution for a contestant who is unable to compete. • The team Coach or Faculty Advisor must notify the Contest Director of the substitution as soon as possible, but no later than at team check-in. The resulting team must be properly constituted.

10. Contestants may bring resource materials such as books, manuals and program listings. • Contestants may not bring any machine-readable versions of software or data.

11. Contestants may not use their own computers, computer terminals, keyboards, or programmable calculators. • Contestants may not use any kind of communication device such as radio sets, cellular phones or pagers.

12. Solutions to problems submitted for judging are called runs. • Each run is judged as accepted or rejected by a Contest Judge, and the team is notified of the result.

13. Rejected runs will be marked as one of the following: "syntax error", "run-time error", "time-limit exceeded" (two minute program running time), "incorrect output", "incomplete output", or "incorrect output format". • If more than one of these applies, the judge can choose any of the applicable responses.

14. Notification of accepted runs may be suspended at an appropriate time to keep the final results secret. • A general announcement to that effect will be made during the contest. • Notification of rejected runs will continue until the end of the contest.

15. A contestant may submit a claim of ambiguity or error in a problem statement by submitting a clarification request to the Contest Judges. • If the Judges agree that an ambiguity or an error exists, a clarification will be issued to all contestants by the Head Judge.

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

17. 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.

18. 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.

19. 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.

20. 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.

21. 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.

22. 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.

23. 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.

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

25. 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.

26. 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.

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

28. Contact Persons • Dr. Maung Htay, Director • Dr. Lee, Associate Director • Dr. Shing, Head Judge of Game Programming Competition • Dr. Edward Okie, Head Judge of Programming Competition • Ms. Kathy Sacklin, Systems Administrator

29. Agenda • 9:00 - 9:30 AM Registration (McGuffey 206) • 9:30 - 10:00AM Welcome Session (McGuffey 206) • 10:00 - 11:00 AM Environment Training & Practice Session (Davis Hall 225) • 11:00 - 12: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 (McGuffey 206) • 3:30 – 4:00 PM Award Ceremony (McGuffey 206)

30. Good Luck