Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided in four parts:
  1. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provide some useful information on the computer.
  2. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser !
  3. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to 1200 seconds. After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to 1230 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (900Mb).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  4. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.

General information on the benchmark

Namemps-v2-13-7/MIPLIB/miplib/normalized-mps-v2-13-7-bell4.opb
MD5SUM8dd8e9a0c4cbb3e21a2a125fbb321c29
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of terms in the objective function 1147
Biggest coefficient in the objective function 618659840000000
Number of bits for the biggest coefficient in the objective function 50
Sum of the numbers in the objective function 13444970235724050
Number of bits of the sum of numbers in the objective function 54
Biggest number in a constraint 618659840000000
Number of bits of the biggest number in a constraint 50
Biggest sum of numbers in a constraint 13444970235724050
Number of bits of the biggest sum of numbers54
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.39279
Number of variables1466
Total number of constraints169
Number of constraints which are clauses18
Number of constraints which are cardinality constraints (but not clauses)34
Number of constraints which are nor clauses,nor cardinality constraints117
Minimum length of a constraint1
Maximum length of a constraint95

Trace number 10330

Launcher Data

LAUNCH ON wulflinc2 THE 2005-09-23 17:52:48 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=9090 boxname=wulflinc2 idbench=886 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  8dd8e9a0c4cbb3e21a2a125fbb321c29  /oldhome/oroussel/tmp/wulflinc2/normalized-mps-v2-13-7-bell4.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc2/normalized-mps-v2-13-7-bell4.opb
IDLAUNCH: 9090
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.261
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 888.83

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.261
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        894148 kB
Buffers:         17272 kB
Cached:         103700 kB
SwapCached:          0 kB
Active:          46092 kB
Inactive:        77772 kB
HighTotal:      131008 kB
HighFree:        31136 kB
LowTotal:       903652 kB
LowFree:        863012 kB
SwapTotal:     2097136 kB
SwapFree:      2097136 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6980 kB
Slab:            10988 kB
Committed_AS:    63624 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-23 17:53:18 (client local time) WITH STATUS 20 IN 30.0934 SECONDS
stats: 9090 7 30.0934 20

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
s UNSATISFIABLE

Watcher Data

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGTERM then SIGKILL): 921600 Kb
Enforcing VSIZE limit: 994918400 bytes
Current StackSize limit: 67108864 bytes
Raw data (/proc/10672/stat): 10672 (pb2sat) R 10671 10672 4070 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 22155009 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/10672/statm): 373 2 364 364 0 9 0
[pid=10672] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc2/normalized-mps-v2-13-7-bell4.opb

[startup+10.0019 s]
Raw data (loadavg): 0.86 0.93 0.94 2/55 10672
Raw data (/proc/10672/stat): 10672 (pb2sat) R 10671 10672 4070 0 -1 0 27364 0 0 0 936 60 0 0 25 0 1 0 22155009 81911808 16205 4294967295 134512640 135987407 3221224560 3221216688 134560536 0 0 5 16384 0 0 0 17 1 0 0
Raw data (/proc/10672/statm): 19998 16205 364 364 0 19634 0
[pid=10672] vsize: 79992
Current children cumulated CPU time (s) 9.96
Current children cumulated vsize (Kb) 79992

[startup+20.0026 s]
Raw data (loadavg): 0.88 0.93 0.94 2/55 10672
Raw data (/proc/10672/stat): 10672 (pb2sat) R 10671 10672 4070 0 -1 0 53854 0 0 0 1879 116 0 0 25 0 1 0 22155009 158814208 31454 4294967295 134512640 135987407 3221224560 3221215004 134636908 0 0 5 16384 0 0 0 17 1 0 0
Raw data (/proc/10672/statm): 38773 31454 364 364 0 38409 0
[pid=10672] vsize: 155092
Current children cumulated CPU time (s) 19.95
Current children cumulated vsize (Kb) 155092

[startup+30.0033 s]
Raw data (loadavg): 0.90 0.93 0.94 2/55 10672
Raw data (/proc/10672/stat): 10672 (pb2sat) R 10671 10672 4070 0 -1 0 78959 0 0 0 2822 168 0 0 25 0 1 0 22155009 134529024 24832 4294967295 134512640 135987407 3221224560 3221223360 134892737 0 0 5 16384 0 0 0 17 1 0 0
Raw data (/proc/10672/statm): 32844 24832 364 364 0 32480 0
[pid=10672] vsize: 131376
Current children cumulated CPU time (s) 29.9
Current children cumulated vsize (Kb) 131376
One traced child (pid=10672) exited with status: 20
All traced children have exited ! Game is over.

Child status: 20
Real time (s): 30.182
CPU time (s): 30.0934
CPU user time (s): 28.3527
CPU system time (s): 1.74073
CPU usage (%): 99.7066
Max. virtual memory (cumulated for all children) (Kb): 155092

Verifier Data

ERROR: no interpretation found !