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-200-3_4-yes1-4.opb
MD5SUM6d19a7d23c112f1bd52f27210adeeb3c
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 200
Optimality of the best value was proved YES
Number of terms in the objective function 400
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 400
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 2
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 400
Number of bits of the biggest sum of numbers9
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.090985
Number of variables400
Total number of constraints880
Number of constraints which are clauses878
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints2
Minimum length of a constraint2
Maximum length of a constraint3

Trace number 9544

Launcher Data

LAUNCH ON wulflinc10 THE 2005-09-23 14:23:30 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8303 boxname=wulflinc10 idbench=99 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  6d19a7d23c112f1bd52f27210adeeb3c  /oldhome/oroussel/tmp/wulflinc10/normalized-aim-200-3_4-yes1-4.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc10/normalized-aim-200-3_4-yes1-4.opb
IDLAUNCH: 8303
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.193
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.193
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:        944692 kB
Buffers:         10932 kB
Cached:          62304 kB
SwapCached:          0 kB
Active:          44368 kB
Inactive:        31772 kB
HighTotal:      131008 kB
HighFree:        64680 kB
LowTotal:       903652 kB
LowFree:        880012 kB
SwapTotal:     2097136 kB
SwapFree:      2097136 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6976 kB
Slab:             8268 kB
Committed_AS:    63624 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-23 14:23:36 (client local time) WITH STATUS 30 IN 6.33304 SECONDS
stats: 8303 0 6.33304 30

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 200
c small objective detected
c CONFLICT during preprocess 
c [startup+3.10485 s]  setting bit 8 to 0
c [startup+3.52355 s]  setting bit 7 to 0
c CONFLICT during preprocess 
c [startup+3.89528 s]  setting bit 6 to 0
c CONFLICT during preprocess 
c [startup+4.24579 s]  setting bit 5 to 0
c CONFLICT during preprocess 
c [startup+4.59135 s]  setting bit 4 to 0
c CONFLICT during preprocess 
c [startup+4.93833 s]  setting bit 3 to 0
c CONFLICT during preprocess 
c [startup+5.2848 s]  setting bit 2 to 0
c CONFLICT during preprocess 
c [startup+5.62951 s]  setting bit 1 to 0
c CONFLICT during preprocess 
c [startup+5.97733 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 x201 -x202 -x203 x204 x205 -x206 x207 -x208 -x209 -x21 x210 x211 -x212 -x213 x214 x215 -x216 -x217 x218 x219 x22 -x220 x221 -x222 x223 -x224 x225 -x226 -x227 x228 x229 -x23 -x230 x231 -x232 x233 -x234 x235 -x236 -x237 x238 x239 x24 -x240 -x241 x242 x243 -x244 -x245 x246 x247 -x248 x249 -x25 -x250 -x251 x252 x253 -x254 -x255 x256 -x257 x258 x259 x26 -x260 x261 -x262 -x263 x264 -x265 x266 x267 -x268 -x269 -x27 x270 x271 -x272 -x273 x274 x275 -x276 -x277 x278 -x279 x28 x280 x281 -x282 x283 -x284 -x285 x286 x287 -x288 x289 x29 -x290 -x291 x292 -x293 x294 -x295 x296 -x297 x298 x299 x3 -x30 -x300 x301 -x302 -x303 x304 -x305 x306 x307 -x308 x309 -x31 -x310 -x311 x312 -x313 x314 -x315 x316 -x317 x318 x319 x32 -x320 -x321 x322 -x323 x324 x325 -x326 x327 -x328 -x329 x33 x330 -x331 x332 x333 -x334 x335 -x336 -x337 x338 x339 -x34 -x340 -x341 x342 -x343 x344 -x345 x346 x347 -x348 x349 x35 -x350 x351 -x352 -x353 x354 x355 -x356 x357 -x358 x359 -x36 -x360 x361 -x362 x363 -x364 -x365 x366 -x367 x368 -x369 -x37 x370 -x371 x372 -x373 x374 -x375 x376 x377 -x378 x379 x38 -x380 -x381 x382 -x383 x384 -x385 x386 x387 -x388 x389 x39 -x390 -x391 x392 x393 -x394 -x395 x396 -x397 x398 x399 -x4 -x40 -x400 -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/6115/stat): 6115 (pb2sat) R 6114 6115 4061 0 -1 0 18 0 0 0 0 0 0 0 22 0 1 0 20881771 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/6115/statm): 373 2 364 364 0 9 0
[pid=6115] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc10/normalized-aim-200-3_4-yes1-4.opb
One traced child (pid=6115) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 6.3534
CPU time (s): 6.33304
CPU user time (s): 6.08807
CPU system time (s): 0.244962
CPU usage (%): 99.6794
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	200