This document contains information about the:
The design and procedures of CASC-16 evolved from those of CASC-13, CASC-14, and CASC-15. The rules, deadlines, and specifications given here, are absolute. Only the competition panel has the right to make exceptions.
Divisions
Competition Divisions
The Problems section explains what problems are
eligible for use in each division and category.
Mixed means Horn and non-Horn problems, with or without
equality, but not unit equality problems (see the UEQ Division below).
The MIX Division is divided into five categories:
The FOF Division is divided into two categories:
Entry into the competition divisions is subject to the following rules:
Number of Problems
A lower bound on the total number of problems that will be used will be
determined from
the number of workstations available,
the time allocated to the competition,
the number of ATP systems to be run on the general hardware over all the
divisions, and
the time limit,
according to the following relationship:
Problem Preparation
In the Special Hardware Division the same problems will be used as for the
general hardware, with the same tptp2X transformations applied.
However, the original file names will be retained.
A minimal time limit of 180 seconds will be used.
The maximal time limit will be determined using the relationship used for
determining the number of problems, with
the minimal number of problems as the "Number of problems".
The time limit will be chosen as a reasonable value within the range
allowed.
The timing will be done by the UNIX
On the general hardware a wall clock time limit will be imposed in addition
to the CPU time limit, in order to prevent very high memory usage that causes
swapping.
The wall clock time limit will be double the CPU time limit.
Entering many similar versions of the same system is deprecated.
Entrants may be required to limit the number of system versions
that they enter.
Winners are expected to provide public access to their system's source code.
It is assumed that each entrant has read all the WWW pages related
to the competition, and has complied with the competition rules.
Non-compliance with the rules could lead to disqualification.
A "catch-all" rule is used to deal with any unforseen circumstances:
No cheating is allowed.
The panel is allowed to disqualify entrants due to unfairness and to adjust
the competition rules in case of misuse.
Please
email the system description to the competition organizers.
The ATP systems that run on the general hardware have to be interruptable
by a SIGXCPU signal, so that the CPU time limit can be imposed on each
solution attempt.
The default action on receiving this signal is to exit (thus complying
with the time limit, as required), but systems may catch the signal
and exit of their own accord.
Both approaches are acceptable for the competition.
If any system runs past the time limit this will be noticed in the timing
data and the system will be considered to have not solved that problem.
In the Special Hardware Division the wall clock time limit will be
imposed using SIGALRM.
When terminating, the ATP systems have to output a distinguished string
(specified by the entrant) to
The ATP systems are not required to output solutions (proofs or models).
However, systems that do output solutions to
The precomputation and storage of any information for individual TPTP
problems for usage during the competition is contrary to the spirit of
the competition, and the no cheating rule
applies.
The precomputation and storage of information for sets of formulae that
are reasonably likely to form the basis of new problems is permitted.
For every problem solved, the system's solution process has to be
reproducible by running the system again.
Entrants have to ensure that their systems execute in the competition
environment, according to the checks listed below.
Entrants are advised to firstly perform these checks on their own machines,
well in advance of the installation period.
This gives the competition organizers time to help resolve any difficulties
that are encountered.
Secondly, entrants must perform these checks on the general hardware.
Systems that do not pass these checks on the general hardware cannot compete.
After the installation deadline access to the general hardware will be
denied, and no further changes to the ATP systems will be permitted.
The organizers will then test the ATP systems, first to check that the systems
execute correctly (according to the above checks), and secondly to check for
soundness.
For the soundness testing, non-theorems
(satisfiable variants of the eligible problems, e.g., without the conjecture
clause, and satisfiable problems selected from the TPTP)
will be submitted to the systems participating in the MIX, UEQ, and FOF
Divisions, and theorems (selected from the TPTP)
will be submitted to the systems participating in the SAT Division.
Finding a proof of a non-theorem or a model for a theorem indicates that the
system is unsound.
If an ATP system fails the soundness testing it will be disqualified.
The soundness testing has a secondary aim of eliminating the possibility of
an ATP system simply delaying for some amount of time and then claiming to
have found a solution. Further soundness testing will be performed after
the competition, as described in the section on
Performance Evaluation.
In the Special Hardware Division the systems will be installed on the
respective hardware by the entrants, and no soundness testing needs to be
performed.
Demonstration Division
ATP systems that cannot run on the general hardware can enter into the Special
Hardware Division.
The hardware can be supplied by the entrant.
The entry specifies which general hardware division's problems are to
be used.
The results will be presented along with the general hardware division's
results, but may not be comparable with those from the systems that ran on
the general hardware.
Infrastructure
Hardware and Software
The competition will be run on 10 SUN Ultra10 workstations, each having:
Problems
Problem Selection
The problems will be selected from the
TPTP Problem Library, v2.2.1.
The problems have to meet certain criteria to be eligible for selection:
The problems used will be randomly selected from the eligible problems at the
start of the competition, based on a seed supplied by the competition panel.
Difficult problems will be eligible.
Note: Entrants are encouraged to
submit their
latest system performance data
to the collection, to help ensure that problems have appropriate ratings.
Entrants will benefit from contributing their latest system performance
data, as it ensures that problems that their system can solve are
eligible (unless they are easy problems).
The deadline for submitting data to be taken into account for CASC-16 is
14th June 1999.
The minimal numbers of problems that have to be used in each division and
category, to ensure sufficient confidence in the competition results,
will be determined from the numbers of eligible problems in each division
and category
(the competition organizers have to ensure that there is sufficient CPU time
available to run the ATP systems on this minimal number of problems).
This minimal numbers of problems will then be used in determining the
time limit imposed on each solution
attempt.
Number of workstations * Time allocated
Number of problems = ---------------------------------------
Number of ATP systems * Time limit
It is a lower bound on the total number of problems because it assumes that
every system will use all the time limit for each problem.
Since some solution attempts will obviously succeed before the time
limit is reached, more problems can actually be used.
The actual numbers used in each division and category will be determined
according to the judgement of the competition organizers.
It is necessary to ensure that no system receives an advantage or
disadvantage due to the specific presentation of the problems in the TPTP.
To this end the tptp2X utility, distributed with the TPTP, will be used to:
Further, to prevent systems from recognizing problems from their file names,
symbolic links will be made to the selected problems, using names of the
form CCCNNN-1.p
for the symbolic links, with NNN
running from 001
to the number of problems in the respective
division or category.
The problems will be specified to the ATP systems using the symbolic link names.
Time Limits and Timing
A time limit will be imposed on each solution attempt.
On the general hardware a CPU time limit will be imposed, while in the Special
Hardware Division the entrant can choose to use either a CPU or a wall
clock time limit.
/usr/bin/time
command,
which returns times in units of 0.1 second.
If an ATP system cannot solve a problem, the runtime will be set to the
time limit.
Entry Requirements and Procedures
System Description
A system description has to be provided for each ATP system entered.
The system descriptions, along with information regarding the competition
design and procedures, will form the proceedings for the competition.
The system descriptions must fit onto a single A4 page, using this
LaTeX schema.
The schema has the following sections:
System Properties
The ATP systems have to be executable by a single command line, with the
file name, the time limit (if required by the entrant), and entrant specified
system switches (the same for all problems) as command line arguments.
No shell features, such as input or output redirection, may be used in the
command line.
stdout
indicating the result:
stdout
will be
highlighted in the presentation of results.
For practical reasons excessive output from the ATP systems is not allowed.
A limit, dependent on the disk space available, will be imposed on the amount
of stdout
and stderr
output that can be produced.
The limit will be at least 10KB per problem (averaged over all problems so
that it is possible to produce some long proofs).
System Installation
Access to the general hardware (or equivalent) will be made available from the
21th June 1999, and the entrants have to have their ATP systems installed
and operational by 2nd July 1999.
No late systems will be accepted.
prompt>which MyATPSystem
/home/tptp/bin/MyATPSystem
prompt>/home/tptp/bin/MyATPSystem /home/tptp/TPTP/Problems/GRP/GRP001-1.p
Proof found in 147 seconds.
prompt>
prompt> cd /home/tptp/tmp
prompt> ln -s /home/tptp/TPTP/Problems/GRP001-1.p CCC001-1.p
prompt> /home/tptp/bin/MyATPSystem /home/tptp/tmp/CCC001-1.p
Proof found in 147 seconds.
prompt>
CPULimitedRun.c
program.
For example:
prompt>which CPULimitedRun
/home/tptp/bin/CPULimitedRun
prompt>/home/tptp/bin/CPULimitedRun 10 /home/tptp/bin/MyATPSystem /home/tptp/tmp/CCC001-1.p
CPULimitedRun: ----------------------------------------------------------
CPULimitedRun: /home/tptp/bin/MyATPSystem
CPULimitedRun: Time limit is 10s
CPULimitedRun: PID is 5827
CPULimitedRun: ----------------------------------------------------------
CPU time limit exceeded (core dumped)
prompt>
/bin/time
. For example:
prompt> /bin/time /home/tptp/bin/CPULimitedRun 200 /home/tptp/bin/MyATPSystem /home/tptp/tmp/CCC001-1.p
CPULimitedRun: ----------------------------------------------------------
CPULimitedRun: /home/tptp/bin/MyATPSystem
CPULimitedRun: Time limit is 200s
CPULimitedRun: PID is 13526
CPULimitedRun: ----------------------------------------------------------
Proof found in 147 seconds.
real 3:04.2
user 2:19.3
sys 7.6
prompt>
rsh
. The timed command
needs to be quoted, and don't forget to make an appropriate
rhosts
entry. For example:
prompt> rsh atoll.cs.jcu.edu.au '/bin/time /home/tptp/bin/CPULimitedRun 200 /home/tptp/bin/MyATPSystem /home/tptp/tmp/CCC001-1.p'
CPULimitedRun: ----------------------------------------------------------
CPULimitedRun: /home/tptp/bin/MyATPSystem
CPULimitedRun: Time limit is 200s
CPULimitedRun: PID is 25461
CPULimitedRun: ----------------------------------------------------------
Proof found in 147 seconds.
real 3:04.2
user 2:19.3
sys 7.6