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/ttp/normalized-circ4_3.opb
MD5SUM	4a7e7b149407cd13657a201380066d1b
Bench Category	optimization, small integers (OPTSMALLINT)
Has Objective Function	YES
Satisfiable	YES
(Un)Satisfiability was proved	YES
Best value of the objective function	20
Optimality of the best value was proved	NO
Number of terms in the objective function	48
Biggest coefficient in the objective function	2
Number of bits for the biggest coefficient in the objective function	2
Sum of the numbers in the objective function	64
Number of bits of the sum of numbers in the objective function	7
Biggest number in a constraint	8
Number of bits of the biggest number in a constraint	4
Biggest sum of numbers in a constraint	64
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.626903
Number of variables	144
Total number of constraints	704
Number of constraints which are clauses	464
Number of constraints which are cardinality constraints (but not clauses)	96
Number of constraints which are nor clauses,nor cardinality constraints	144
Minimum length of a constraint	2
Maximum length of a constraint	12

Trace number 24424

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc31 THE 2005-05-10 07:53:11 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=2307 boxname=wulflinc31 idbench=257 idsolver=3 numberseed=0
MD5SUM SOLVER: 03a6a792daea978e4202f78851741568  /oldhome/oroussel/solvers/bsolo_mis
MD5SUM BENCH:  4a7e7b149407cd13657a201380066d1b  /oldhome/oroussel/tmp/wulflinc31/normalized-circ4_3.opb
REAL COMMAND:  bsolo_mis /oldhome/oroussel/tmp/wulflinc31/normalized-circ4_3.opb
IDLAUNCH: 2307
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.153
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.153
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:        297992 kB
Buffers:         46224 kB
Cached:         656728 kB
SwapCached:        644 kB
Active:         306624 kB
Inactive:       398668 kB
HighTotal:      131008 kB
HighFree:        33824 kB
LowTotal:       903652 kB
LowFree:        264168 kB
SwapTotal:     2097892 kB
SwapFree:      2096612 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5608 kB
Slab:            25644 kB
Committed_AS:    63652 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-05-10 07:53:17 (client local time) WITH STATUS 30 IN 5.45317 SECONDS
stats: 2307 0 5.45317 30
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c Initial problem consists of 144 variables and 764 constraints.
c After prepocess the problem consists of 144 variables and 692 constraints.
c preprocess terminated 0.363 s
c Initial Lower Bound: 14
c Lower Bound Elapsed time: 0
c Not use computed LB before first solution.
c NEW SOLUTION FOUND: 24 @ 0.597
c NEW SOLUTION FOUND: 22 @ 0.662
c NEW SOLUTION FOUND: 20 @ 0.665
s OPTIMUM FOUND
v v97 -v98 -v99 -v100 -v101 v102 v103 -v104 -v105 -v106 -v107 v108 v109 -v110 -v111 -v112 v113 -v114 -v115 -v116 v117 v118 -v119 -v120 -v121 -v122 v123 v124 -v125 -v126 -v127 v128 -v129 -v130 -v131 v132 v133 -v134 -v135 -v136 -v137 v138 -v139 -v140 v141 v142 -v143 v144 -v2 -v18 v34 -v50 -v66 -v82 -v3 -v19 -v35 -v51 v67 -v83 -v4 -v20 -v36 v52 -v68 -v84 -v5 -v21 -v37 -v53 -v69 v85 -v7 -v23 -v39 v55 -v71 -v87 -v8 -v24 -v40 -v56 v72 -v88 -v9 v25 -v41 -v57 -v73 -v89 v10 -v26 -v42 -v58 -v74 -v90 -v12 -v28 v44 -v60 -v76 -v92 v13 -v29 -v45 -v61 -v77 -v93 -v14 v30 -v46 -v62 -v78 -v94 -v15 -v31 -v47 -v63 -v79 v95 v6 v22 v38 -v54 -v70 -v86 -v11 -v27 -v43 v59 v75 v91 -v16 -v32 v48 v64 v80 -v96 v1 v17 -v33 -v49 -v65 v81 
c Exit Code: 30
c Total time: 5.431 s
#### 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
Raw data (loadavg): 0.89 0.95 0.91 2/54 8574
Raw data (stat): 8574 (runsolver) R 8573 7876 7672 0 -1 64 5 0 0 0 0 0 0 0 19 0 1 0 707594235 1056768 100 4294967295 134512640 135381576 3221221696 3221216916 135158418 0 2147483391 1 90112 0 0 0 17 0 0 0
Raw data (statm): 258 100 215 215 0 43 0
vsize: 1032
[startup+5.49215 s]
Raw data (loadavg): 0.90 0.95 0.91 1/53 8574
Raw data (stat): 8574 (runsolver) R 8573 7876 7672 0 -1 64 5 0 0 0 0 0 0 0 19 0 1 0 707594235 1056768 100 4294967295 134512640 135381576 3221221696 3221216916 135158418 0 2147483391 1 90112 0 0 0 17 0 0 0
Raw data (statm): 258 100 215 215 0 43 0
vsize: 0

Child status: 30
Real time (s): 5.49182
CPU time (s): 5.45317
CPU user time (s): 5.40118
CPU system time (s): 0.051992
CPU usage (%): 99.2962
Max. virtual memory (Kb): 1032
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	20
#### END VERIFIER DATA ####