The 29th PACISE Conference Programming Contest

California University of Pennsylvania

Registration

Teams will be accepted on a first-come, first-serve basis, as space permits. Each team must complete the contest application form provided on the conference Web site and return it no later than March 21st (Friday). Applications will be acknowledged via email. Note: Team members must also register for the PACISE Conference; a separate registration form is required.

Information and Rules

Team Composition

• All team members, including faculty and alternates, must be registered for the conference using the conference registration form.
• Any team with one or more members unregistered for the conference will be disqualified.
• There will be two or three undergraduate students per team, plus alternates.
• Each team is comprised solely of undergraduate students currently registered at that school.

Location and Hardware

• The programming contest location is in the Eberly Science and Technology Building (Eberly Hall - EBE).
• All machines will be running Windows 7.
• All programs must be written in C, C++, or Java.
• The Visual Studio 2010, NetBeans and Bloodshed Dev-C++ development environments will be available.
• Each team will be allocated one computer.

Contest Time

• There will be a practice session which begins Friday, April 4th at 7:30 PM for the purpose of familiarizing participants with the computing environment.
• Teams will be given directions on using our machines, followed by a practice session with one sample problem. This practice session ends at 9:30.
• The contest will officially run on Saturday April 5th from 8:00 AM until 11:30 AM. A group of 5 problems will be given to solve in this time period.

Contest Procedures, Rules and Restrictions

• No Internet access will be allowed.
• Students can bring text books and printouts; however, no electronic tools (flash drives, cell phones, electronic watches, calculators, etc.).
• All decisions of the judges and/or the contest chairs regarding permissible references are final.
• Team advisors, coaches and alternates are NOT permitted to help (hinder) teams solve problems during the contest.
• The conference organizers cannot be responsible for the security of unattended electronic devices.

Rule Violations

• Violations of the rules may result in team penalties or disqualification.
• All decisions of the contest judges and/or contest chairs are final.
• Refreshments will be available.

Questions

Please forward any questions to the Chairs of the Programming Contest: Dr. Anthony Rodi or Prof. Paul Sible.