MAX-CSP 2008 Competition: results by benchmark

Results by benchmark for category binary constraints in intension (2-ARY-INT), subcategory boolean problems

This page displays the results of the different solvers for each benchmark for category binary constraints in intension (2-ARY-INT), subcategory boolean problems

REMINDER

Keep in mind that the 'Best result' columns only provide the best result given by one of the solvers. This 'Best result' may be wrong in case of an UNSATISFIABLE or OPTIMUM FOUND answer (because there's no efficient way to check these answers).

Description of a cell contents:

Cell exampleMeaning
AnswerSolver result
f=...value of the objective function for the model reported by the solver
TT=...Total Time (TT): this is the CPU time (in seconds) used by the solver until termination. This time is only meaningful for complete solvers because incomplete solvers will always run until they time out
T1=...Time to get the best model (T1): this is the wall clock time (in seconds) ellapsed when the solver found its best model. This time is obtained from the 'o lines'. It is useful to compare both complete and incomplete solvers. It doesn't take into account the time to prove optimality of the solution.
Remember that CPU time and wall clock time are two very different notions. The CPU time represents the time during which the instructions of the solver were executed by the processor. The wall clock time represents how much time ellapsed on the clock. For a same event, the CPU time may be either smaller or greater than the wall clock time depending on the number of threads of execution and the number of processors.

Meaning of some abbreviations:

AbbreviationMeaning
f=...Value of the objective function
TOTime Out
MOMem. Out (out of memory)

Meaning of the different colors:

ColorMeaning
textthe solver cannot handle this instance
textthe solver gave no answer
textthe solver could give an answer (SAT)
textthe solver gave a definitive answer (OPTIMUM FOUND or UNSAT)
textthe solver performed better than the other ones on that instance
textthe solver was ended by a signal
textthe solver gave an incomplete answer
textthe solver was disqualified in the category
textthe solver gave a wrong answer

For better readability, you may choose to hide some solvers:
AbsconMax 112 pc-d
AbsconMax 112 pc-w
Concrete + CSP4J - MCRW Engine 2008-05-30
Concrete + CSP4J - Tabu Engine 2008-05-30
Sugar v1.13+minisat
Sugar++ v1.13+minisat-inc

Bench nameBest results
on this
instance
AbsconMax 112
pc-d
AbsconMax 112
pc-w
Concrete + CSP4J - MCRW Engine
2008-05-30
Concrete + CSP4J - Tabu Engine
2008-05-30
Sugar
v1.13+minisat
Sugar++
v1.13+minisat-inc
csp/pseudo/mps/
normalized-mps-diamond.xml
MOPT
f=1
TT=0.551
T1=0.43
OPTIMUM
f=1
TT=3.293
T1=0.58
CHECKS=16
NODES=1
OPTIMUM
f=1
TT=3.279
T1=0.58
CHECKS=16
NODES=1
? (TO)

TT=3600.02

? (TO)

TT=3600.03

OPTIMUM
f=1
TT=0.551
T1=0.43
OPTIMUM
f=1
TT=0.567
T1=0.44

Some statistics...

AbsconMax 112
pc-d
AbsconMax 112
pc-w
Concrete + CSP4J - MCRW Engine
2008-05-30
Concrete + CSP4J - Tabu Engine
2008-05-30
Sugar
v1.13+minisat
Sugar++
v1.13+minisat-inc
Number of times the solver is able to give the best known answer110011
Number of times the solver is able to give the best known answer from an incomplete solver point of view (i.e. without considering optimality proof)110011
Number of times the solver is the best solver from a complete solver point of view (i.e. best known answer and best TT time)000010
Number of times the solver is the best solver from an incomplete solver point of view (i.e. best known answer and best T1 time)000010