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/primes-dimacs-cnf/normalized-aim-50-6_0-yes1-2.opb
MD5SUM	d50859cfd8ffc5545d6ebbb3993e5418
Bench Category	optimization, small integers (OPTSMALLINT)
Has Objective Function	YES
Satisfiable	YES
(Un)Satisfiability was proved	YES
Best value of the objective function	50
Optimality of the best value was proved	NO
Number of terms in the objective function	100
Biggest coefficient in the objective function	1
Number of bits for the biggest coefficient in the objective function	1
Sum of the numbers in the objective function	100
Number of bits of the sum of numbers in the objective function	7
Biggest number in a constraint	2
Number of bits of the biggest number in a constraint	2
Biggest sum of numbers in a constraint	100
Number of bits of the biggest sum of numbers	7
Best result obtained on this benchmark	SAT
Best CPU time to get the best result obtained on this benchmark	0.016997
Number of variables	100
Total number of constraints	350
Number of constraints which are clauses	347
Number of constraints which are cardinality constraints (but not clauses)	0
Number of constraints which are nor clauses,nor cardinality constraints	3
Minimum length of a constraint	2
Maximum length of a constraint	3

Trace number 34738

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc25 THE 2005-05-28 10:32:15 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=24046 boxname=wulflinc25 idbench=120 idsolver=17 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  d50859cfd8ffc5545d6ebbb3993e5418  /oldhome/oroussel/tmp/wulflinc25/normalized-aim-50-6_0-yes1-2.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc25/normalized-aim-50-6_0-yes1-2.opb
IDLAUNCH: 24046
/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	: 888.83

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
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	: 901.12

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        652080 kB
Buffers:         36920 kB
Cached:         325468 kB
SwapCached:       1004 kB
Active:          65932 kB
Inactive:       298556 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        651828 kB
SwapTotal:     2097892 kB
SwapFree:      2095984 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5064 kB
Slab:            12400 kB
Committed_AS:    63592 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-05-28 10:32:15 (client local time) WITH STATUS 30 IN 0.446931 SECONDS
stats: 24046 0 0.446931 30
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c [startup+0.27469 s]  setting bit 6 to 0
c got solution with objective value: 50
c [startup+0.30307 s]  setting bit 5 to 1
c got solution with objective value: 50
c [startup+0.328674 s]  setting bit 4 to 1
c [startup+0.355098 s]  setting bit 3 to 0
c [startup+0.382305 s]  setting bit 2 to 0
c got solution with objective value: 50
c [startup+0.408183 s]  setting bit 1 to 1
c [startup+0.435092 s]  setting bit 0 to 0
s OPTIMUM FOUND
v -x1 -x10 -x100 x11 -x12 -x13 x14 x15 -x16 -x17 x18 -x19 x2 x20 -x21 x22 -x23 x24 x25 -x26 -x27 x28 -x29 -x3 x30 -x31 x32 -x33 x34 x35 -x36 -x37 x38 -x39 x4 x40 x41 -x42 x43 -x44 -x45 x46 -x47 x48 x49 x5 -x50 x51 -x52 -x53 x54 x55 -x56 -x57 x58 -x59 -x6 x60 -x61 x62 x63 -x64 x65 -x66 x67 -x68 x69 -x7 -x70 -x71 x72 x73 -x74 x75 -x76 -x77 x78 x79 x8 -x80 -x81 x82 x83 -x84 -x85 x86 -x87 x88 x89 x9 -x90 -x91 x92 x93 -x94 -x95 x96 -x97 x98 x99 
#### 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.73 0.90 0.69 2/54 8081
Raw data (stat): 8081 (runsolver) R 8080 1586 1585 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 864121618 884736 94 4294967295 134512640 135332820 3221224464 3221219644 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.451184 s]
Raw data (loadavg): 0.75 0.90 0.69 1/53 8081
Raw data (stat): 8081 (runsolver) R 8080 1586 1585 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 864121618 884736 94 4294967295 134512640 135332820 3221224464 3221219644 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.450905
CPU time (s): 0.446931
CPU user time (s): 0.422935
CPU system time (s): 0.023996
CPU usage (%): 99.1187
Max. virtual memory (Kb): 864
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	50
#### END VERIFIER DATA ####