Trace number 46548

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.4OPT34 17.7143 17.7264

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_8.opb
MD5SUM6d3802f2f17c83a21ccf6c0752b41678
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 benchmark11.3293
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 variables392
Total number of constraints679
Number of constraints which are clauses0
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 constraint14
Maximum length of a constraint29
Number of terms in the objective function 7
Biggest coefficient in the objective function 64
Number of bits for the biggest coefficient in the objective function 7
Sum of the numbers in the objective function 127
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 635
Number of bits of the biggest sum of numbers10
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.06	c starting to Solve
0.06	c #variables read: 392 - #constraints read: 680
0.13	o 51
0.17	o 46
0.19	o 43
0.20	o 42
0.21	o 41
0.23	o 37
0.95	o 36
2.73	o 35
4.87	o 34
17.72	c optimum objective found = 34
17.72	c total time              : 17.71 s
17.72	s OPTIMUM FOUND
17.72	v -x1 x2 -x3 -x4 -x5 x6 -x7 -x43 x44 x45 x46 x47 -x48 -x49 x50 -x51 -x52 -x53 -x54 x55 -x56 -x392 x36 -x37 -x38 x39 x40 -x41 -x42 -x391
17.72	v -x390 -x389 -x388 -x387 x29 x30 -x31 -x32 x33 -x34 -x35 -x386 -x385 -x384 -x383 -x382 -x381 -x380 -x379 -x378 -x377 -x376 x375
17.72	v x374 -x373 -x22 -x23 x24 x25 -x26 -x27 -x28 -x372 -x371 -x370 -x369 -x368 -x367 -x366 -x365 -x364 -x363 -x362 -x361 -x360 -x359
17.72	v -x358 -x357 -x356 x355 x354 -x353 -x352 -x351 -x350 x349 x348 -x347 x346 x345 x344 -x343 -x8 x9 -x10 -x11 -x12 -x13 -x14 -x342
17.72	v -x341 -x340 -x339 -x338 -x337 -x336 -x335 -x334 -x333 -x332 -x331 -x330 -x329 -x328 -x327 -x326 -x325 -x324 -x323 -x322 -x321
17.72	v -x320 -x319 -x318 -x317 -x316 -x315 -x314 -x313 -x312 -x311 -x310 -x309 -x308 -x307 x306 x305 x304 -x303 -x302 -x301 -x300
17.72	v -x299 -x298 -x297 x296 x295 x294 -x293 x292 x291 x290 x289 -x288 -x15 -x16 -x17 -x18 -x19 -x20 -x21 -x287 -x286 -x285 -x284
17.72	v -x283 -x282 -x281 -x280 -x279 -x278 -x277 -x276 -x275 -x274 -x273 x272 x271 -x270 -x269 -x268 -x267 -x266 -x265 -x264 -x263
17.72	v -x262 -x261 -x260 -x259 x258 x257 x256 -x255 -x254 -x253 -x252 -x251 -x250 -x249 -x248 -x247 -x246 x245 x244 -x243 -x242 x241
17.72	v x240 x239 x238 -x237 -x236 -x235 -x234 -x233 -x232 x231 x230 -x229 -x228 x227 x226 x225 x224 -x223 x222 x221 x220 x219 x218
17.72	v -x217 x216 x215 x214 x213 x212 x211 x210 x209 x208 x207 x206 x205 x204 x203 x202 x201 x200 x199 x198 x197 -x196 -x195 -x194 -x193
17.72	v -x192 -x191 x190 -x189 -x188 -x187 -x186 -x185 -x184 -x183 -x182 -x181 x180 x179 x178 x177 -x176 -x175 -x174 -x173 -x172 -x171
17.72	v -x170 -x169 -x168 -x167 -x166 -x165 x164 x163 x162 x161 x160 x159 -x158 -x157 -x156 -x155 -x154 -x153 -x152 -x151 -x150 -x149
17.72	v x148 x147 -x146 -x145 x144 x143 x142 x141 x140 x139 x138 x137 -x136 -x135 -x134 -x133 -x132 -x131 x130 x129 -x128 -x127 x126
17.72	v x125 x124 x123 -x122 x121 x120 x119 x118 x117 x116 x115 x114 x113 x112 -x111 x110 x109 x108 x107 x106 x105 x104 x103 x102 x101
17.72	v x100 x99 x98 x97 x96 x95 x94 x93 x92 x91 x90 x89 x88 x87 x86 x85 x84 x83 x82 x81 x80 x79 x78 x77 x76 x75 x74 x73 x72 x71 x70 x69 x68 x67
17.72	v x66 x65 x64 x63 x62 x61 x60 x59 x58 x57

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/node68/watcher-46548-1149789105 -o ROOT/results/node68/solver-46548-1149789105 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node68/46548-1149789105/instance-46548-1149789105.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.92 0.98 0.91 2/64 26283
/proc/meminfo: memFree=1719704/2055920 swapFree=4182328/4192956
[pid=26283] ppid=26281 vsize=2324 CPUtime=0
/proc/26283/stat : 26283 (Pueblo) R 26281 26283 26237 0 -1 4194304 63 0 0 0 0 0 0 0 18 0 1 0 244579990 2379776 48 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 10479343 0 0 4096 0 0 0 0 17 1 0 0
/proc/26283/statm: 582 55 43 16 0 11 0

[startup+10.0028 s]
/proc/loadavg: 0.93 0.98 0.91 2/64 26283
/proc/meminfo: memFree=1718640/2055920 swapFree=4182328/4192956
[pid=26283] ppid=26281 vsize=3468 CPUtime=9.99
/proc/26283/stat : 26283 (Pueblo) R 26281 26283 26237 0 -1 4194304 508 0 0 0 998 1 0 0 25 0 1 0 244579990 3551232 479 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134528344 0 0 4096 0 0 0 0 17 1 0 0
/proc/26283/statm: 867 479 205 16 0 308 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 3468

Child status: 30
Real time (s): 17.7264
CPU time (s): 17.7143
CPU user time (s): 17.6893
CPU system time (s): 0.024996
CPU usage (%): 99.9319
Max. virtual memory (cumulated for all children) (Kb): 3468
The end

Launcher Data (download as text)

Begin job on node68 on Thu Jun  8 17:51:45 UTC 2006


FILE ID= 46548-1149789105

PBS_JOBID= 373248

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/golomb-rulers/normalized-OGR_8.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node68/46548-1149789105/instance-46548-1149789105.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node68/watcher-46548-1149789105 -o ROOT/results/node68/solver-46548-1149789105 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node68/46548-1149789105/instance-46548-1149789105.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  6d3802f2f17c83a21ccf6c0752b41678

RANDOM SEED= 929347200


/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.279
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.279
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:       1719912 kB
Buffers:         33136 kB
Cached:         241172 kB
SwapCached:       2384 kB
Active:         102296 kB
Inactive:       180776 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1719912 kB
SwapTotal:     4192956 kB
SwapFree:      4182328 kB
Dirty:             152 kB
Writeback:           0 kB
Mapped:          15560 kB
Slab:            38968 kB
Committed_AS:   485780 kB
PageTables:       1400 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node68 on Thu Jun  8 17:52:02 UTC 2006