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/primes-dimacs-cnf/normalized-aim-100-2_0-yes1-3.opb
MD5SUMe13da91e0882f7b8f155a22ef7144d8e
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 100
Optimality of the best value was proved YES
Number of terms in the objective function 200
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 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 2
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 200
Number of bits of the biggest sum of numbers8
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.029995
Number of variables200
Total number of constraints300
Number of constraints which are clauses299
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint3

Trace number 9520

Launcher Data

LAUNCH ON wulflinc7 THE 2005-09-23 14:22:42 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8284 boxname=wulflinc7 idbench=80 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  e13da91e0882f7b8f155a22ef7144d8e  /oldhome/oroussel/tmp/wulflinc7/normalized-aim-100-2_0-yes1-3.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc7/normalized-aim-100-2_0-yes1-3.opb
IDLAUNCH: 8284
/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	: 890.88

processor	: 1
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	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        931232 kB
Buffers:         11412 kB
Cached:          75016 kB
SwapCached:          0 kB
Active:          45400 kB
Inactive:        43876 kB
HighTotal:      131008 kB
HighFree:        52164 kB
LowTotal:       903652 kB
LowFree:        879068 kB
SwapTotal:     2097136 kB
SwapFree:      2097136 kB
Dirty:              40 kB
Writeback:           0 kB
Mapped:           6976 kB
Slab:             8476 kB
Committed_AS:    63660 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-23 14:22:44 (client local time) WITH STATUS 30 IN 1.35479 SECONDS
stats: 8284 0 1.35479 30

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 100
c small objective detected
c CONFLICT during preprocess 
c [startup+0.726071 s]  setting bit 7 to 0
c CONFLICT during preprocess 
c [startup+0.805298 s]  setting bit 6 to 0
c CONFLICT during preprocess 
c [startup+0.888142 s]  setting bit 5 to 0
c CONFLICT during preprocess 
c [startup+0.969972 s]  setting bit 4 to 0
c CONFLICT during preprocess 
c [startup+1.0496 s]  setting bit 3 to 0
c CONFLICT during preprocess 
c [startup+1.12926 s]  setting bit 2 to 0
c CONFLICT during preprocess 
c [startup+1.20831 s]  setting bit 1 to 0
c CONFLICT during preprocess 
c [startup+1.28761 s]  setting bit 0 to 0
c CONFLICT during preprocess 
s OPTIMUM FOUND
v x1 x10 x100 -x101 x102 x103 -x104 -x105 x106 -x107 x108 x109 x11 -x110 x111 -x112 -x113 x114 x115 -x116 -x117 x118 -x119 -x12 x120 x121 -x122 -x123 x124 -x125 x126 x127 -x128 x129 x13 -x130 x131 -x132 x133 -x134 -x135 x136 -x137 x138 x139 -x14 -x140 -x141 x142 -x143 x144 -x145 x146 -x147 x148 x149 -x15 -x150 x151 -x152 -x153 x154 x155 -x156 -x157 x158 x159 x16 -x160 -x161 x162 x163 -x164 x165 -x166 -x167 x168 x169 -x17 -x170 x171 -x172 -x173 x174 -x175 x176 -x177 x178 x179 x18 -x180 -x181 x182 -x183 x184 -x185 x186 -x187 x188 x189 -x19 -x190 -x191 x192 -x193 x194 -x195 x196 x197 -x198 x199 -x2 x20 -x200 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

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/6947/stat): 6947 (pb2sat) R 6946 6947 4059 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 20889040 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/6947/statm): 373 2 364 364 0 9 0
[pid=6947] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc7/normalized-aim-100-2_0-yes1-3.opb
One traced child (pid=6947) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 1.37986
CPU time (s): 1.35479
CPU user time (s): 1.2998
CPU system time (s): 0.054991
CPU usage (%): 98.1836
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	100