Mid Atlantic Regional
ACM Programming Contest
Sponsored By IBM
at
Radford University
November 2, 2013
Welcome
• Welcome
– Dr. Maung Htay, Regional Director
– Dr. Art Carter, Associate Dean of College of Science and
Technology and Chair of Department of Information
Technology, Radford University
– Mr. David Horton, Assistant to the Dean of CSAT, Radford
University
– Mr. Eric Woods, IBM
• Contest Rules by Dr. Hwajung Lee, Site Director
Rules
• At most one contestant from each team may hold
a baccalaureate degree.
• No contestant may have completed two years of
post-baccalaureate studies or hold a graduate
degree.
• Students who have competed in two World Finals
may not compete in a Regional Contest.
• Contestants are not required to be student
members of the ACM in order to be eligible to
compete in a regional contest.
• Note, however, that all World Finals contestants
are required to be student members of ACM
• World Finals, June 22 ~ June 26, 2014 in
Ekaterinburg, Ural Federal University, Russia
• Each team competing in the Mid-Atlantic
Regional 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.
• Contestants may bring resource materials such as
books, manuals and program listings.
• Contestants may not bring any machine-readable
versions of software or data.
• 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.
• 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.
• Rejected runs will be marked as one of the
following:
–
–
–
–
–
–
syntax error
run-time error
time-limit exceeded (30 second program running time)
incorrect output
incomplete output
incorrect output format
• If more than one of these applies, the judge can
choose any of the applicable responses.
• Notification of final accepted runs may occur
after the end of the contest 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.
• A contestant may submit a claim of ambiguity or error in a
problem statement by submitting a clarification request
to the Contest Judges. Coaches may NOT submit such a
claim and should not, for any reason, communicate with
judges during the contest.
• Read the problem carefully before requesting a
clarification. Also, check to see if clarifications for that
problem have already occurred.
• If the Judges believe that the problem statement is
sufficiently clear, you will receive the response “The
problem statement is sufficient; no clarification is
necessary”. Read problem statement carefully again and
again.
• If you still feel there is an ambiguity, you will have
to be more specific or descriptive of the
ambiguity you have found.
• If the problem statement is ambiguous in
specifying the correct output for a particular
input, please include that input data in the
clarification request.
• You may not submit clarification request asking
for correct output for inputs you provide.
• If the Judges agree that an ambiguity or an error
exists, a clarification will be issued to all
contestants by the Head Judge.
• Contestants are not to converse with anyone
except members of their team and personnel
designated by the Regional Contest Director.
• 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.
• 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.
• 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.
• While the contest is scheduled to last exactly five
hours, the Regional 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.
• A team may be disqualified by the Regional
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.
• 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 Regional Contest Director is solely
responsible for ruling on unforeseen situations
and interpreting these rules for the Regional
Contest.
• The problem set will be available for coaches and
others two hour after contest begins. Coaches or
unauthorized persons are NOT supposed to
contact to head judge or any judges during the
contest time. If they do so, there may be a serious
penalty to their teams.
SCORING THE CONTEST
• The Regional Contest Judges are solely
responsible for determining the correctness of
submitted runs.
• In consultation with the Judges, the Regional
Contest Head Judge is responsible for
determining the winners of the Regional Contest.
• The judging staff is empowered to adjust for or
adjudicate unforeseen events and conditions.
• Their decisions are final and may not be
appealed.
• 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.
• 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.
• It is the responsibility of the Regional Contest
Director to specify any tie-breakers if necessary.
Contact Persons
•
•
•
•
•
Dr. Maung Htay, Regional Director
Dr. Hwajung Lee, Site Director & Local Judge
Dr. Hui Wang, Associate Site Director & Local Judge
Dr. Andrew Ray, Regional System Administrator
Mr. Lloyd Jones, Systems Administrator
Please Join me to thank you
to those who make this event happen
•
•
•
•
•
•
•
•
•
IBM (represented today by Mr. Eric Woods) for sponsoring this event
Regional Director, Dr. Maung Htay
Dean Orion Rogers for his strong support and encouragement
Associate Dean and Department chair Dr. Art Carter for his strong
support and encouragement
Assistant to the Dean David Horton
Dr. Andrew Ray for serving as Regional System Administrator, and also
our panel of distinguished regional judges.
Dr. Hui Wang, Associate site Director
Mr. Lloyd Jones for systems management
ACM local chapter volunteers, Justin Price, Brandyn Price, Mary
VanDyke, Roshan Patel, Jordan Wilson, Eric Ashenden, Kayla Evans, Ben
Doerflinger, JPhill Valoyi, Andrew Wassell, Alejandro Figueroa, Ethan
Preston, Alex Sarahan, and Danielle Capezzuto
Schedule to Go
8:00 – 8:45
8:45 – 9:30
9:30 – 10:30
11:00 – 12:00
12:00 – 5:00
5:00 - 6:00 pm
Registration & Breakfast (McGuffey Hall 203)
Welcome Session (McGuffey Hall 203)
Practice Session (Davis 114 , 201, and 225 Labs)
Lunch (McGuffey Hall 203)
Contest (Davis 114 , 201, and 225 Labs)
During the contest, coaches can stay at McGuffey Hall 203
Dinner & Awarding Ceremony (McGuffey Hall 203)
PC Lab (Room 114)
Team
Institution
Floofy Rainbox Uncorn
Longwood University
Gold
Bridgewater College
Sleep Deficit
Longwood University
↓ ↓ barely better than ↓ ↓
Radford University
The Runtime Exceptionals
Radford University
bletch
University of Virginia
baz
University of Virginia
foo
University of Virginia
thud
University of Virginia
snork
University of Virginia
£
Virginia Tech
\b
Virginia Tech
SyntacticSugar
Washington and Lee University
ArrayList
Washington and Lee University
Location
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
DA114
CO-OP Lab (Room 201)
Team
Institution
Hardy House Hackers
!(NaN==NaN)!
fum
zot
^
Longwood University
Radford University
University of Virginia
University of Virginia
Virginia Tech
Washington and Lee
University
West Virginia University
Institute of Technology
SyntaxHeirs2TheThrownException
Team 337
Location
DA201
DA201
DA201
DA201
DA201
DA201
DA201
UNIX Lab (Room 225)
Team
Institution
Crimson
Elwoods
I/O, not 1/0
↑ ↑ almost as good as ↑ ↑
blarg
bar
grunt
qux
flarp
~
\
Team 3
Bridgewater College
Longwood University
Radford University
Radford University
University of Virginia
University of Virginia
University of Virginia
University of Virginia
University of Virginia
Virginia Tech
Virginia Tech
Virginia Tech
Location
DA225
DA225
DA225
DA225
DA225
DA225
DA225
DA225
DA225
DA225
DA225
DA225
 Good Luck 