Trace number 85442

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 into four (or five) parts:
  1. 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 ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. 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.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. 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 X seconds (see the parameters in the trace). 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 X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    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.
  5. 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 provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerObjective functionCPU timeWall clock time
glpPB 0.2OPT0 1.01384 1.02042

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/
benchmarks/radar/normalized-10:10:4.5:0.95:100.opb
MD5SUMb258fc1dc8cb1827e842a0b9558712c7
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark1.01384
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 0
Optimality of the best value was proved YES
Number of variables435
Total number of constraints501
Number of constraints which are clauses403
Number of constraints which are cardinality constraints (but not clauses)98
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint16
Number of terms in the objective function 435
Biggest coefficient in the objective function 282
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 1168
Number of bits of the sum of numbers in the objective function 11
Biggest number in a constraint 282
Number of bits of the biggest number in a constraint 9
Biggest sum of numbers in a constraint 1168
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c glpPB 0.2 (July 2006)
0.00	c An Application of GLPK 4.10 for PB Constraints
0.00	c Done @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
1.01	c starting to Solve
1.01	c total time = 1.01
1.01	o 0
1.01	c quality of integer solution is H
1.01	s OPTIMUM FOUND
1.01	v x359 x235 -x63 x6 x341 -x236 x400 x363 x340 -x240 -x7 x399 x361 -x239 -x8 x401 x342 -x237 -x144 -x11 x434 x362 x344 -x238 -x143
1.01	v -x9 -x417 x366 -x145 -x10 -x421 x345 x435 x358 -x234 x183 -x62 x3 -x337 x233 -x187 x5 x364 -x336 -x321 -x244 x4 -x12 x367 x343
1.01	v x402 x365 x346 x416 -x410 x420 x406 -x146 x405 -x387 -x154 -x27 x150 -x31 -x356 x317 -x252 -x247 x182 -x64 x360 -x256 -x248
1.01	v -x186 x2 x357 x320 -x243 -x20 x368 x338 -x16 -x407 x339 -x241 -x161 -x68 -x15 -x409 -x165 x418 -x383 x350 -x151 -x129 x422 -x153
1.01	v x403 -x386 -x302 -x26 -x149 -x30 x316 -x274 -x251 -x245 x184 x65 -x17 x355 -x278 x255 -x188 -x19 x376 x322 -x84 -x69 x412 -x408
1.01	v -x372 -x88 -x67 x411 -x371 x353 -x242 -x190 -x160 -x125 -x48 -x13 x354 -x191 -x164 -x152 x419 -x382 x349 -x325 -x298 -x128
1.01	v -x14 x423 x424 x404 -x388 x347 -x301 -x28 x425 -x147 -x32 -x373 x318 -x273 -x253 -x246 x185 x66 -x18 x375 -x277 x257 -x189 -x70
1.01	v -x352 x323 -x193 -x83 -x44 -x351 -x192 -x87 x378 -x369 x326 -x259 -x162 -x124 -x47 x413 x324 -x260 -x166 -x22 x414 -x384 -x370
1.01	v -x297 x130 -x21 x415 x429 x389 x348 -x303 -x168 -x29 -x169 -x148 x33 -x374 x314 -x275 x254 x181 -x78 x319 -x279 x258 x180 -x156
1.01	v -x74 x315 x262 x197 -x155 -x120 -x85 -x73 -x43 x327 x261 -x89 -x293 -x281 -x221 -x163 -x126 -x112 -x49 x377 -x282 -x225 -x167
1.01	v -x432 x379 -x299 -x171 x131 -x91 x433 -x385 -x170 -x92 -x23 x428 x381 -x304 -x211 x132 -x52 -x24 -x390 x133 x25 x276 -x250 x200
1.01	v -x80 -x77 -x39 x313 -x280 x249 x201 -x335 x284 x266 x196 -x108 -x86 -x71 -x45 -x331 -x283 -x157 -x119 -x90 -x431 -x330 x220
1.01	v -x194 -x158 -x121 -x111 x94 -x72 -x50 -x430 -x292 -x224 x159 -x127 -x93 -x294 -x207 x175 x123 -x53 x380 x300 x134 -x51 -x426
1.01	v x398 x296 -x210 -x36 x394 -x305 x37 -x332 x272 x269 x198 -x75 -x334 x271 x270 -x79 -x38 x288 x265 -x107 -x81 -x40 x82 -x46 -x328
1.01	v -x263 x222 -x195 -x178 x113 -x98 -x42 x226 -x179 x122 -x54 x395 -x329 -x206 x174 -x142 -x35 x397 -x295 x138 -x34 -x427 x312
1.01	v -x228 x212 -x172 -x137 -x116 x393 x308 -x229 -x333 x289 x267 -x199 x105 -x76 x291 -x216 x287 x215 -x177 -x109 x101 -x176 x102
1.01	v -x41 x285 -x264 x223 -x204 -x139 x114 -x97 -x61 x396 x227 -x141 -x58 x309 -x231 x208 -x117 -x95 -x57 x311 -x230 -x115 x213 -x173
1.01	v -x135 x391 x306 x290 x268 -x100 x104 -x99 x103 -x60 x217 -x140 -x110 -x59 x286 x218 x106 x310 x219 -x203 -x118 x232 x202 -x96
1.01	v -x55 x209 x205 -x136 -x56 x392 x307 x214 x1

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes

runsolver version 3.0.3 (c) roussel@cril.univ-artois.fr

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node51/watcher-85442-1154171683 -o ROOT/results/node51/solver-85442-1154171683 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node51/85442-1154171683/instance-85442-1154171683.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.99 0.97 0.91 3/64 15148
/proc/meminfo: memFree=896488/2055920 swapFree=4183068/4192956
[pid=15148] ppid=15146 vsize=1012 CPUtime=0
/proc/15148/stat : 15148 (glpPBv3) R 15146 15148 15099 0 -1 0 45 0 0 0 0 0 0 0 18 0 1 0 164038908 1036288 28 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 2618148 0 0 4096 0 0 0 0 17 1 0 0
/proc/15148/statm: 253 28 20 40 0 8 0

Child status: 30
Real time (s): 1.02042
CPU time (s): 1.01384
CPU user time (s): 1.00985
CPU system time (s): 0.003999
CPU usage (%): 99.3559
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node51 on Sat Jul 29 11:14:43 UTC 2006


FILE ID= 85442-1154171683

PBS_JOBID= 893216

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/radar/normalized-10:10:4.5:0.95:100.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node51/85442-1154171683/instance-85442-1154171683.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node51/watcher-85442-1154171683 -o ROOT/results/node51/solver-85442-1154171683 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node51/85442-1154171683/instance-85442-1154171683.opb

MD5SUM SOLVER= 29ce95346658d7502ba983059bfb8cff
MD5SUM BENCH=  b258fc1dc8cb1827e842a0b9558712c7

RANDOM SEED= 334948242

TIMEOUT= 1800 seconds


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.231
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.231
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        896760 kB
Buffers:         40788 kB
Cached:        1038932 kB
SwapCached:       3588 kB
Active:         104852 kB
Inactive:       983428 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        896760 kB
SwapTotal:     4192956 kB
SwapFree:      4183068 kB
Dirty:             160 kB
Writeback:           0 kB
Mapped:          14496 kB
Slab:            56952 kB
Committed_AS:   737100 kB
PageTables:       1420 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node51 on Sat Jul 29 11:14:44 UTC 2006