2025 Lipscomb Invitational Programming Contest

We hope to see you March 22, 2025 on the second floor of the Fields Engineering Center on the Lipscomb University campus.

Directions and maps.

To participate, please register your team using this form. Space is limited.

If you have questions please contact Dwayne Towell via email.

Schedule

11:00registration, setup
11:30lunch
12:00contest begins
12:10coaches briefing
1:00lifelines become available
4:00scoreboard freezes
5:00contest ends
5:15results, debrief, prizes for top 3 teams


Invitational Programming Contest Rules

The following rules are designed to clarify the difference between acceptable behavior and unacceptable behavior. This is not a complete list. We reserve the right to define new rules as necessary to make this a fair and enjoyable contest. In general, these rules should be familiar to ICPC participants with the notable exception of Lifelines.

All contest submissions, including problem submissions and clarifications, are the property of Lipscomb University. We reserve the right to use and publish these submissions as we choose.

Rules

Teams may have at most three members, who must be undergraduate students.

Teams have only one computational device: the computer we provide. No phones, calculators, smart watches, or any other potentially computational devices are allowed.

Contestants may bring non-machine readable resource materials such as books, manuals, and program listings.

Contestants are not to communicate with anyone except members of their team, their coach, and contest personnel.

Coaches are not allowed in the locations where teams are competing.

The contest is scheduled for five hours; however, the Contest Director may alter the length of the contest in the event of unforeseen difficulties.

Disqualification

Doing something that the Contest Director deems unacceptable will get you disqualified. You will be required to leave immediately and will not be allowed to participate further. Examples of ways to get disqualified:

Submissions

Teams submit solutions to problems via a web form, vaguely similar to Kattis. Submissions will be judged and the results delivered via the contest website.

All input will be from standard input. All output will be to standard output. This means "<" will be used to redirect input into your program.

Judging and Clarifications

Submissions are judged as quickly as possible and will be one of the following results:

Normally when a team believes that the judges are wrong, the team has not consider a possible variation of the input data or has misunderstood the problem. However, if you believe a problem statement is in error or is ambiguous, they may submit a clarification request via the contest website.

If you believe a mistake was made judging your run, you may submit a clarification request via the contest website.

Clarifications will be answered with a "no comment" response to the submitting team, or via an announcement to all teams via the contest website.

In the event that the Contest Director determine an error in judging has occurred, we will do what we can to rectify the situation. For example, all submissions will be rejudged in sequence to give you credit for solving the problem at the earliest point that your problem ran correctly.

Scoring

The team with the most problems solved wins. Fewest penalty minutes are used to resolve ties. Each minute, or fraction of a minute, a problem remains unsolved is considered a penalty minute. Each incorrect submission counts as an additional 20 penalty minutes. Penalty minutes for unsolved problems are NOT included.

Lifelines

Each team has three lifelines for use anytime except the first hour of the contest.

Each lifeline allows up to 10 minutes consulting with a coach, away from the contest area as designated by contest officials. All team members must be present during coaching. No written or electronic materials are allowed during coaching; a whiteboard and copy of the problems will be available during coaching.

Either the coach or the team may call for a timeout.