This page displays the results of the different solvers for each benchmark for category n-ary constraints in intension (N-ARY-INT), subcategory real world 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). |
Cell example | Meaning |
---|---|
Answer | Solver 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. |
Abbreviation | Meaning |
---|---|
f=... | Value of the objective function |
TO | Time Out |
MO | Mem. Out (out of memory) |
Color | Meaning |
---|---|
text | the solver cannot handle this instance |
text | the solver gave no answer |
text | the solver could give an answer (SAT) |
text | the solver gave a definitive answer (OPTIMUM FOUND or UNSAT) |
text | the solver performed better than the other ones on that instance |
text | the solver was ended by a signal |
text | the solver gave an incomplete answer |
text | the solver was disqualified in the category |
text | the 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
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 answer | 0 | 0 | 2 | 0 | 1 | 1 |
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) | 0 | 0 | 2 | 0 | 1 | 1 |
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) | 0 | 0 | 2 | 0 | 0 | 1 |
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) | 0 | 0 | 0 | 0 | 0 | 1 |