PB'05 competition: run trace

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:

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.
SOLVER DATA
This is the output of the solver (stdout and stderr).
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.
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

Name	normalized-opb/submitted/manquinho/synthesis-ptl-cmos-circuits/normalized-b1.opb
MD5SUM	36b626a2866033d54ab226ba7c2cf010
Bench Category	optimization, small integers (OPTSMALLINT)
Has Objective Function	YES
Satisfiable	YES
(Un)Satisfiability was proved	YES
Best value of the objective function	128
Optimality of the best value was proved	NO
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 numbers	10
Best result obtained on this benchmark	SAT
Best CPU time to get the best result obtained on this benchmark	0.009998
Number of variables	24
Total number of constraints	45
Number of constraints which are clauses	45
Number of constraints which are cardinality constraints (but not clauses)	0
Number of constraints which are nor clauses,nor cardinality constraints	0
Minimum length of a constraint	2
Maximum length of a constraint	9

Trace number 34856

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc24 THE 2005-05-28 11:06:29 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=24175 boxname=wulflinc24 idbench=249 idsolver=17 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  36b626a2866033d54ab226ba7c2cf010  /oldhome/oroussel/tmp/wulflinc24/normalized-b1.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc24/normalized-b1.opb
IDLAUNCH: 24175
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.080
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	: 3
cpu MHz		: 451.080
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:        732156 kB
Buffers:         36032 kB
Cached:         244920 kB
SwapCached:        636 kB
Active:          19824 kB
Inactive:       263116 kB
HighTotal:      131008 kB
HighFree:        33376 kB
LowTotal:       903652 kB
LowFree:        698780 kB
SwapTotal:     2097892 kB
SwapFree:      2096360 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5148 kB
Slab:            13812 kB
Committed_AS:    63604 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-05-28 11:06:30 (client local time) WITH STATUS 30 IN 0.696893 SECONDS
stats: 24175 0 0.696893 30
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 389
c [startup+0.314971 s]  setting bit 9 to 1
c got solution with objective value: 128
c [startup+0.371173 s]  setting bit 8 to 1
c CONFLICT during preprocess 
c [startup+0.396357 s]  setting bit 7 to 0
c [startup+0.432182 s]  setting bit 6 to 0
c [startup+0.47471 s]  setting bit 5 to 0
c got solution with objective value: 128
c [startup+0.524994 s]  setting bit 4 to 1
c got solution with objective value: 128
c [startup+0.564591 s]  setting bit 3 to 1
c got solution with objective value: 128
c [startup+0.60001 s]  setting bit 2 to 1
c CONFLICT during preprocess 
c [startup+0.63193 s]  setting bit 1 to 0
c got solution with objective value: 128
c [startup+0.667262 s]  setting bit 0 to 1
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 
#### END SOLVER DATA ####
#### BEGIN WATCHER DATA ####
Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing VSIZE limit: 943718400 bytes
Enforcing Stack size limit: 67108864 bytes
Current StackSize limit: 67108864 bytes
Raw data (loadavg): 0.91 0.95 0.90 2/54 18933
Raw data (stat): 18933 (runsolver) R 18932 4613 4612 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 864310073 884736 94 4294967295 134512640 135332820 3221224480 3221219660 135092226 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 216 94 205 205 0 11 0
vsize: 864
[startup+0.697887 s]
Raw data (loadavg): 0.92 0.95 0.90 1/53 18933
Raw data (stat): 18933 (runsolver) R 18932 4613 4612 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 864310073 884736 94 4294967295 134512640 135332820 3221224480 3221219660 135092226 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 216 94 205 205 0 11 0
vsize: 0

Child status: 30
Real time (s): 0.69758
CPU time (s): 0.696893
CPU user time (s): 0.668898
CPU system time (s): 0.027995
CPU usage (%): 99.9015
Max. virtual memory (Kb): 864
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	128
#### END VERIFIER DATA ####