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-C17.opb
MD5SUM	4b3ab32e1f00bf5464220d8082457829
Bench Category	optimization, small integers (OPTSMALLINT)
Has Objective Function	YES
Satisfiable	YES
(Un)Satisfiability was proved	YES
Best value of the objective function	260
Optimality of the best value was proved	NO
Number of terms in the objective function	15
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	588
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	588
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.004998
Number of variables	15
Total number of constraints	24
Number of constraints which are clauses	24
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	1
Maximum length of a constraint	5

Trace number 42124

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc1 THE 2005-06-16 00:34:02 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=25345 boxname=wulflinc1 idbench=247 idsolver=18 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  4b3ab32e1f00bf5464220d8082457829  /oldhome/oroussel/tmp/wulflinc1/normalized-C17.opb
REAL COMMAND:  pb2sat-v2 /oldhome/oroussel/tmp/wulflinc1/normalized-C17.opb
IDLAUNCH: 25345
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.053
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.053
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:        824024 kB
Buffers:         34092 kB
Cached:         153008 kB
SwapCached:       1192 kB
Active:          76792 kB
Inactive:       112572 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        823772 kB
SwapTotal:     2097136 kB
SwapFree:      2094880 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5364 kB
Slab:            15476 kB
Committed_AS:    92716 kB
PageTables:        332 kB
VmallocTotal:   114680 kB
VmallocUsed:      1388 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-06-16 00:34:03 (client local time) WITH STATUS 30 IN 0.119981 SECONDS
stats: 25345 0 0.119981 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: 588
c small objective detected
c CONFLICT during preprocess 
c [startup+0.061042 s]  setting bit 9 to 0
c got solution with objective value: 318
c [startup+0.067382 s]  setting bit 8 to 1
c CONFLICT during preprocess 
c [startup+0.071219 s]  setting bit 7 to 0
c got solution with objective value: 260
c [startup+0.080071 s]  setting bit 6 to 1
c CONFLICT during preprocess 
c [startup+0.08412 s]  setting bit 5 to 0
c CONFLICT during preprocess 
c [startup+0.088579 s]  setting bit 4 to 0
c [startup+0.093144 s]  setting bit 3 to 0
c got solution with objective value: 260
c [startup+0.100136 s]  setting bit 2 to 1
c got solution with objective value: 260
c [startup+0.105552 s]  setting bit 1 to 1
c got solution with objective value: 260
c [startup+0.110923 s]  setting bit 0 to 1
s OPTIMUM FOUND
v -x1 -x10 x11 x12 -x13 x14 -x15 -x2 -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/55 9331
Raw data (stat): 9331 (runsolver) R 9330 8378 8377 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 909620541 884736 94 4294967295 134512640 135332820 3221224480 3221219660 135092226 0 2147483391 7 90112 0 0 0 17 1 0 0
Raw data (statm): 216 94 205 205 0 11 0
vsize: 864
[startup+0.122511 s]
Raw data (loadavg): 0.91 0.95 0.90 1/54 9331
Raw data (stat): 9331 (runsolver) R 9330 8378 8377 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 909620541 884736 94 4294967295 134512640 135332820 3221224480 3221219660 135092226 0 2147483391 7 90112 0 0 0 17 1 0 0
Raw data (statm): 216 94 205 205 0 11 0
vsize: 0

Child status: 30
Real time (s): 0.122221
CPU time (s): 0.119981
CPU user time (s): 0.107983
CPU system time (s): 0.011998
CPU usage (%): 98.1673
Max. virtual memory (Kb): 864
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	260
#### END VERIFIER DATA ####