Trace number 50099

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
Pueblo 1.3OPT34 13.03 13.0395

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
bounded_golomb_rulers/normalized-bogr_8.opb
MD5SUM7511e7863ac3e00f42a81c49dc15d5a1
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark34
Best CPU time to get the best result obtained on this benchmark13.03
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 34
Optimality of the best value was proved YES
Number of variables386
Total number of constraints680
Number of constraints which are clauses1
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints679
Minimum length of a constraint1
Maximum length of a constraint26
Number of terms in the objective function 7
Biggest coefficient in the objective function 32
Number of bits for the biggest coefficient in the objective function 6
Sum of the numbers in the objective function 91
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 128
Number of bits of the biggest number in a constraint 8
Biggest sum of numbers in a constraint 472
Number of bits of the biggest sum of numbers9
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

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

Verifier Data (download as text)

OK	34

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.1 (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/node87/watcher-50099-1149945319 -o ROOT/results/node87/solver-50099-1149945319 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node87/50099-1149945319/instance-50099-1149945319.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.00 0.00 0.07 2/67 27061
/proc/meminfo: memFree=1827312/2055888 swapFree=4085324/4096564
[pid=27061] ppid=27059 vsize=2336 CPUtime=0
/proc/27061/stat : 27061 (Pueblo13) R 27059 27061 27015 0 -1 4194304 146 0 0 0 0 0 0 0 18 0 1 0 260171036 2392064 128 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 11204761 0 0 4096 0 0 0 0 17 1 0 0
/proc/27061/statm: 584 128 109 16 0 11 0

[startup+10.002 s]
/proc/loadavg: 0.15 0.03 0.08 2/67 27061
/proc/meminfo: memFree=1826360/2055888 swapFree=4085324/4096564
[pid=27061] ppid=27059 vsize=3372 CPUtime=9.99
/proc/27061/stat : 27061 (Pueblo13) R 27059 27061 27015 0 -1 4194304 469 0 0 0 997 2 0 0 25 0 1 0 260171036 3452928 441 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/27061/statm: 843 441 205 16 0 283 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 3372

Child status: 30
Real time (s): 13.0395
CPU time (s): 13.03
CPU user time (s): 13.001
CPU system time (s): 0.028995
CPU usage (%): 99.9276
Max. virtual memory (cumulated for all children) (Kb): 3372
The end

Launcher Data (download as text)

Begin job on node87 on Sat Jun 10 13:15:19 UTC 2006


FILE ID= 50099-1149945319

PBS_JOBID= 385706

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/bounded_golomb_rulers/normalized-bogr_8.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node87/50099-1149945319/instance-50099-1149945319.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node87/watcher-50099-1149945319 -o ROOT/results/node87/solver-50099-1149945319 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node87/50099-1149945319/instance-50099-1149945319.opb

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  7511e7863ac3e00f42a81c49dc15d5a1

RANDOM SEED= 473247806


/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.234
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	: 6006.17
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.234
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	: 5999.44
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1827584 kB
Buffers:         19276 kB
Cached:         140380 kB
SwapCached:       2184 kB
Active:          31292 kB
Inactive:       136740 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1827584 kB
SwapTotal:     4096564 kB
SwapFree:      4085324 kB
Dirty:             136 kB
Writeback:           0 kB
Mapped:          16456 kB
Slab:            46948 kB
Committed_AS:   629372 kB
PageTables:       1280 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node87 on Sat Jun 10 13:15:32 UTC 2006