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

Namesubmitted/manquinho/synthesis-ptl-cmos-circuits/normalized-b1.opb
MD5SUM36b626a2866033d54ab226ba7c2cf010
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 128
Optimality of the best value was proved YES
Number of terms in the objective function 24
Biggest coefficient in the objective function 61
Number of bits for the biggest coefficient in the objective function 6
Sum of the numbers in the objective function 925
Number of bits of the sum of numbers in the objective function 10
Biggest number in a constraint 61
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 925
Number of bits of the biggest sum of numbers10
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.008998
Number of variables24
Total number of constraints45
Number of constraints which are clauses45
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint9

Trace number 9694

Launcher Data

LAUNCH ON wulflinc25 THE 2005-09-23 15:07:26 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8459 boxname=wulflinc25 idbench=255 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  36b626a2866033d54ab226ba7c2cf010  /oldhome/oroussel/tmp/wulflinc25/normalized-b1.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc25/normalized-b1.opb
IDLAUNCH: 8459
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.002
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	: 3
cpu MHz		: 451.002
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	: 901.12

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        929044 kB
Buffers:         16848 kB
Cached:          69716 kB
SwapCached:          0 kB
Active:          44496 kB
Inactive:        44940 kB
HighTotal:      131008 kB
HighFree:        57400 kB
LowTotal:       903652 kB
LowFree:        871644 kB
SwapTotal:     2097892 kB
SwapFree:      2097892 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6980 kB
Slab:            10624 kB
Committed_AS:    63620 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-23 15:07:26 (client local time) WITH STATUS 30 IN 0.667897 SECONDS
stats: 8459 0 0.667897 30

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 925
c small objective detected
c got solution with objective value: 396
c [startup+0.334614 s]  setting bit 9 to 1
c got solution with objective value: 128
c [startup+0.400842 s]  setting bit 8 to 1
c CONFLICT during preprocess 
c [startup+0.42443 s]  setting bit 7 to 0
c [startup+0.456613 s]  setting bit 6 to 0
c [startup+0.497926 s]  setting bit 5 to 0
c got solution with objective value: 128
c [startup+0.537858 s]  setting bit 4 to 1
c got solution with objective value: 128
c [startup+0.576595 s]  setting bit 3 to 1
c got solution with objective value: 128
c [startup+0.61062 s]  setting bit 2 to 1
c CONFLICT during preprocess 
c [startup+0.633787 s]  setting bit 1 to 0
c CONFLICT during preprocess 
c [startup+0.661354 s]  setting bit 0 to 0
s OPTIMUM FOUND
v -x1 x10 -x11 x12 -x13 -x14 -x15 -x16 -x17 -x18 -x19 -x2 -x20 -x21 -x22 -x23 -x24 x3 -x4 -x5 -x6 x7 -x8 -x9

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/7177/stat): 7177 (pb2sat) R 7176 7177 4004 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 21107605 1527808 2 4294967295 134512640 135987407 3221224576 3221224576 134512928 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/7177/statm): 373 2 364 364 0 9 0
[pid=7177] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc25/normalized-b1.opb
One traced child (pid=7177) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 0.681025
CPU time (s): 0.667897
CPU user time (s): 0.639902
CPU system time (s): 0.027995
CPU usage (%): 98.0723
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	128