South Central USA Regional Programming Contest

Contest Rules

ACM

Local Contest

Results

Contest
Details

And now for the rules:

• Eligibility
  • Teams must have exactly three members. Period.
  • Undergraduates and or students starting graduate school (for technical details, visit Official ACM Rules and read the section on Team Composition. That is our stance.)
  • You must pay your entrance fee (I wish this could be free, but as long as the world charges us, we will have to charge you).
  • You must complete Registration before 9:00 AM on Saturday.
  • Each Team Member must wear their official contest t-shirt during the contest on Saturday (if we could not provide one of appropriate size, we will suspend this rule for you. This must be done before 9:00 AM, Saturday.) This is a "recommendation" from ACM. I see no reason to not follow this recommendation.
• Disqualification
  • Doing something that this contest deems unacceptable will get you disqualified.
  • There is no appeal (it's too late afterwards).
  • You will be required to immediately leave and will not be allowed to participate in any other function related to the contest. You will not have any money refunded.
  • Eating during the Practice Contest.
  • Eating during the Contest.
• Language
  • The only language we are supporting is English. All problems will be presented in English. Any questions must be presented in English. If there are any questions concerning English (mine is a Mississippi variant of American English), please feel free to ask. What is obvious to one, is not always obvious to the other.
  • Language that offends others is prohibited. Abuse can/will result in disqualification.
• Actual Contest Rules
  • Contestants may bring resource materials such as books, manuals, and program listings. Contestants may not bring any machine-readable versions of software or data.
  • Solutions to problems submitted for judging are called runs. Each run is judged as accepted or rejected by a judge, and the team is notified of the results.
  • 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.
  • A contestant may submit a claim of ambiguity or error in a problem statement by submitting a clarification request to a judge. If the judges agree that an ambiguity or error exists, a clarification will be issued to all contestants.
  • 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.
  • While the contest is scheduled for a particular time length (five hours), the regional contest director has the authority to alter the length of 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 materials, or distracting behavior.
  • Eight problems are planned to be posed. So far as possible, problems will avoid dependence on detailed knowledge of a particular applications area or particular contest language.
    
    In other words: do your best to solve the problems, do not do anything to disrupt your competitors, and concentrate on solving problems.
  • Scoring
    • Each minute a problem remains unsolved is considered a penalty minute.
    • Each submission you make counts as fifteen penalty minutes.
  • Submissions
    • Teams are responsible for knowing how to be able to submit solutions via PC^2 (use the practice time before the contest).
    • All submissions will accumulate penalty points (don't make silly mistakes - submit the wrong file, select the wrong language, etc.). Judges will make no effort to guess what you meant.
    • All input will be from standard input. All output will be to standard output. When your program is run, the < will be used to redirect input into your program. The > will be used to redirect your output to a file. Failure on your part to plan for this will probably result in your program not being judged as correct. We will be doing all judging via our scripts (they use command line compiles - not the IDEs).
    • Working - you need to create all files in C:\temp. Do not put files in other places. This is important.
  • Judging
    • Judges will attempt to judge every submission made by a team during the contest.
    • These are the only rulings that you will get back
      • Yes - this means that your program was judged as correct. Quit working on it. Go on to another problem.
      • No - Compilation Error - this means that the judge was unable to compile your program
        Check the following:
        • Did you submit the correct source file?
        • Did you submit for the correct problem?
        • Did you choose the correct the language?
        • Did you test it before submitting?
      • No - run-time error - your program crashed while it was being run by the judge
      • No - time limit exceeded - your program ran for more than 5 minutes of clock time on the judge's system with the judge's data file
      • No - wrong answer - your program produced output that did not match the judge's expected output
      • No - presentation error - your output has a minor formatting issue. It is HIGHLY unlikely that you will get this message. Judges will be told to always respond with wrong answer if your output does not match. If you get this message, you know that a judge is tired of your repeated submissions with some simple text string mis-spelled.
      • No - other - contact staff - if you get this, that means that you have managed to do something totally unexpected. If someone does not talk to you soon, ask a helper for help.
    • Judging will be done as timely as possible. If it takes a long time to get an answer back, that means we are having a lot of submissions or we are having problems.
    • Judges decisions are not questionable. If you feel that we have made a mistake, you may send a clarification. Normally when a team believes that the judges are wrong, the real answer is that the team did not consider a possible variation of the input data. We will examine any data that seems to be producing unusual results. If we determine an error in our data (or solution), we will do what we can to rectify the situation. We will rejudge your submissions in sequence and give you credit for solving the problem at the earliest point that your problem ran correctly. We cannot give you the time back. If you continue to miss a problem, go on to others. Even if the fault is with us, we cannot set the clock back. Let us know if you suspect a problem and go on to another problem.
  • Winning
    • Teams solving more problems than others will be ranked higher (win by solving the most problems).
    • Teams having solved the same number of problems will be ranked based on penalty points (team with least is best)
    • Penalty points for unsolved problems are NOT figured into this score
    • Teams that have solved the same number of problems with the same number of penalty points will be ranked according to number of submissions (fewer is better)
    • Ties after that point will be up to the Contest Director to resolve.
  • Clarifications
    • Only clarifications submitted via the PC^2 software will be read.
    • All clarifications will be answered in one of two ways:
      1. No comment response
      2. Printed result will be sent to all teams
    • PC^2 provides a list of all submitted clarifications and the responses
    • Clarifications will be handled by the judges
  • Printing - we plan to provide network-based printing. The more people that print, the longer it will take to get printouts. Helpers will deliver your printout to you. Any file you wish to print MUST state your team number at the top of the printout. Put a comment at the top of your source that is very clear. Edit any text files to have your team number as the first line of any printout. If the helpers cannot determine who to deliver the printout to, they will throw it away.
  • Saving the code you write
    • The only way for you to preserve your code is to write it to floppy before you leave your computer. The only way you can have a floppy is if you bring it with you to the contest. The only floppies you can bring into the contest are floppies that are sealed in the box from the vendor. In other words, bring a box of unopened floppies with you to the contest. Make sure that you set the box in plain sight.
  • Resources
    • You are expected to use only the computer provided to you. Attempting to use the network is an automatic disqualification (during the contest).
    • You may use any resources that are not alive, not machine readable, and not a computational device. Clocks are allowed (unless they include calculators).
    • You may use any source or object code provided with the approved packages.
  • Helpers - We have a number of volunteers that will be helping throughout the contest. Most of them will be wearing purple t-shirts with the tiger on the front on Friday. Saturday they will be wearing gold t-shirts with the tiger on the back. These people are volunteers. They will do their best to help you throughout the weekend. During the contest they are not allowed to answer any questions about languages, how to compile, what a question is asking, etc. Make sure you have asked all your questions prior to the contest starting. Most of the time, these helpers will merely act as indirect references (you will ask something, they will go get an answer or someone who can provide an answer). Please be polite to these people.
  • Advice
    • Print when you need to (like when you switch from one person to another).
    • Expect delays when printing (at least five minutes).
    • Be courteous to everyone - it might help.
    • Take advantage of the practice time and the practice contest.
    • Don't miss the rules presentation.
    • Ask before it's too late.
    • Don't allow a question of un-ethical behavior to happen.

LSU