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-bell3b.opb
MD5SUMeaa1b6e946f643598c767cbea970679c
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 1320
Biggest coefficient in the objective function 6291456000000000
Number of bits for the biggest coefficient in the objective function 53
Sum of the numbers in the objective function 122055965815457650
Number of bits of the sum of numbers in the objective function 57
Biggest number in a constraint 6291456000000000
Number of bits of the biggest number in a constraint 53
Biggest sum of numbers in a constraint 122055965815457650
Number of bits of the biggest sum of numbers57
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark2.11268
Number of variables1663
Total number of constraints194
Number of constraints which are clauses22
Number of constraints which are cardinality constraints (but not clauses)39
Number of constraints which are nor clauses,nor cardinality constraints133
Minimum length of a constraint1
Maximum length of a constraint135

Trace number 10329

Launcher Data

LAUNCH ON wulflinc7 THE 2005-09-23 17:52:46 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=9089 boxname=wulflinc7 idbench=885 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  eaa1b6e946f643598c767cbea970679c  /oldhome/oroussel/tmp/wulflinc7/normalized-mps-v2-13-7-bell3b.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc7/normalized-mps-v2-13-7-bell3b.opb
IDLAUNCH: 9089
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.220
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	: 890.88

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.220
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:        917648 kB
Buffers:         12884 kB
Cached:          87144 kB
SwapCached:          0 kB
Active:          45816 kB
Inactive:        57152 kB
HighTotal:      131008 kB
HighFree:        43540 kB
LowTotal:       903652 kB
LowFree:        874108 kB
SwapTotal:     2097136 kB
SwapFree:      2097136 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6984 kB
Slab:             8488 kB
Committed_AS:    63660 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 31.6882 SECONDS
stats: 9089 7 31.6882 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/10919/stat): 10919 (pb2sat) R 10918 10919 4059 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 22149585 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/10919/statm): 373 2 364 364 0 9 0
[pid=10919] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc7/normalized-mps-v2-13-7-bell3b.opb

[startup+10.0012 s]
Raw data (loadavg): 0.93 0.95 0.90 2/55 10919
Raw data (/proc/10919/stat): 10919 (pb2sat) R 10918 10919 4059 0 -1 0 27338 0 0 0 935 63 0 0 25 0 1 0 22149585 81817600 16179 4294967295 134512640 135987407 3221224560 3221212128 134556288 0 0 5 16384 0 0 0 17 0 0 0
Raw data (/proc/10919/statm): 19975 16179 364 364 0 19611 0
[pid=10919] vsize: 79900
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 79900

[startup+20.0019 s]
Raw data (loadavg): 0.94 0.96 0.91 2/55 10919
Raw data (/proc/10919/stat): 10919 (pb2sat) R 10918 10919 4059 0 -1 0 53871 0 0 0 1881 116 0 0 25 0 1 0 22149585 158990336 31472 4294967295 134512640 135987407 3221224560 3221210592 134802877 0 0 5 16384 0 0 0 17 0 0 0
Raw data (/proc/10919/statm): 38816 31472 364 364 0 38452 0
[pid=10919] vsize: 155264
Current children cumulated CPU time (s) 19.97
Current children cumulated vsize (Kb) 155264

[startup+30.0025 s]
Raw data (loadavg): 0.95 0.96 0.91 2/55 10919
Raw data (/proc/10919/stat): 10919 (pb2sat) R 10918 10919 4059 0 -1 0 81012 0 0 0 2820 174 0 0 25 0 1 0 22149585 233402368 47535 4294967295 134512640 135987407 3221224560 3221223248 134811770 0 0 5 16384 0 0 0 17 0 0 0
Raw data (/proc/10919/statm): 56983 47535 364 364 0 56619 0
[pid=10919] vsize: 227932
Current children cumulated CPU time (s) 29.94
Current children cumulated vsize (Kb) 227932
One traced child (pid=10919) exited with status: 20
All traced children have exited ! Game is over.

Child status: 20
Real time (s): 31.7547
CPU time (s): 31.6882
CPU user time (s): 29.8315
CPU system time (s): 1.85672
CPU usage (%): 99.7904
Max. virtual memory (cumulated for all children) (Kb): 227932

Verifier Data

ERROR: no interpretation found !