Trace number 31226

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 NameAnswerCPU timeWall clock time
wildcat-rnp 0.8.0SAT 0.849869 0.867212

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
prestwich/armies/normalized-army13.24ls.opb
MD5SUM1a4510076d9024b805728ffe22c0d108
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.849869
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables490
Total number of constraints737
Number of constraints which are clauses397
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints338
Minimum length of a constraint2
Maximum length of a constraint169
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 24
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 193
Number of bits of the biggest sum of numbers8
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 
0.00	c wildcat-rnp (VERSION 0.8.0-lite-rnp-devel)
0.00	c Developed by L. Liu  and M. Truszczynski 
0.00	c Last built on Tue 23 May 2006 09:33:09 PM EDT
0.00	c 
0.00	c ROOT/solvers/PB/PB06final/user3/wildcat-rnp ROOT/tmp/node38/31226-1149206619/instance-31226-1149206619.opb 894798946 
0.00	c =================================== BEGIN ===================================
0.00	c 
0.00	c Random Number Seed: 894798946
0.00	c Noise: 0.7 (70 : 100) 
0.86	c Starting searching:
0.86	c phase 1 ... vc 
0.86	s SATISFIABLE
0.86	v -x1 -x2 x3 -x4 -x5 -x6 x7 -x8 -x9 -x10 x11 -x12 -x13 -x14 x15 -x16 -x17 -x18 x19 -x20 -x21 -x22 x23 -x24 -x25 -x26 x27 -x28 -x29 -x30
0.86	v x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54 x55 -x56
0.86	v -x57 -x58 x59 -x60 -x61 -x62 x63 -x64 -x65 -x66 x67 -x68 -x69 -x70 x71 -x72 -x73 -x74 x75 -x76 -x77 -x78 x79 -x80 -x81 -x82 x83
0.86	v -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107
0.86	v -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 x118 -x119 -x120 -x121 x122 -x123 -x124 -x125 x126 -x127 -x128
0.86	v -x129 x130 x131 -x132 -x133 -x134 x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148 -x149
0.86	v -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 x166 -x167 -x168 -x169 x170
0.86	v -x171 -x172 -x173 x174 -x175 -x176 -x177 x178 -x179 -x180 -x181 x182 x183 -x184 -x185 -x186 x187 -x188 -x189 -x190 -x191 -x192
0.86	v -x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209 -x210 -x211 -x212 -x213
0.86	v -x214 -x215 -x216 -x217 x218 -x219 -x220 -x221 x222 -x223 -x224 -x225 x226 -x227 -x228 -x229 x230 -x231 -x232 -x233 x234 x235
0.86	v -x236 -x237 -x238 x239 -x240 -x241 -x242 -x243 -x244 -x245 -x246 -x247 -x248 -x249 -x250 -x251 -x252 -x253 -x254 -x255 -x256
0.86	v -x257 -x258 -x259 -x260 -x261 -x262 -x263 -x264 -x265 -x266 -x267 -x268 -x269 x270 -x271 -x272 -x273 x274 -x275 -x276 -x277
0.86	v x278 -x279 -x280 -x281 x282 -x283 -x284 -x285 x286 x287 -x288 -x289 -x290 x291 -x292 -x293 -x294 -x295 -x296 -x297 -x298 -x299
0.86	v -x300 -x301 -x302 -x303 -x304 -x305 -x306 -x307 -x308 -x309 -x310 -x311 -x312 -x313 -x314 -x315 -x316 -x317 -x318 -x319 -x320
0.86	v -x321 x322 -x323 -x324 -x325 x326 -x327 -x328 -x329 x330 -x331 -x332 -x333 x334 -x335 -x336 -x337 x338 -x339 x340 -x341 x342
0.86	v -x343 x344 -x345 x346 x347 -x348 -x349 x350 x351 -x352 -x353 x354 x355 -x356 -x357 x358 x359 -x360 -x361 x362 x363 -x364 -x365
0.86	v x366 -x367 x368 -x369 x370 -x371 x372 x373 -x374 -x375 x376 x377 -x378 -x379 x380 x381 -x382 -x383 x384 x385 -x386 -x387 x388
0.86	v x389 -x390 x391 -x392 -x393 x394 x395 -x396 -x397 x398 x399 -x400 -x401 x402 x403 -x404 -x405 x406 x407 -x408 -x409 x410 -x411
0.86	v -x412 -x413 x414 -x415 -x416 -x417 -x418 -x419 x420 -x421 -x422 -x423 x424 -x425 -x426 -x427 x428 -x429 -x430 -x431 x432 -x433
0.86	v -x434 -x435 x436 x437 -x438 -x439 x440 x441 -x442 -x443 x444 x445 -x446 -x447 -x448 x449 -x450 -x451 -x452 x453 -x454 -x455
0.86	v -x456 x457 -x458 -x459 -x460 x461 -x462 -x463 -x464 x465 -x466 -x467 -x468 -x469 x470 -x471 -x472 -x473 x474 x475 -x476 -x477
0.86	v x478 x479 -x480 -x481 x482 x483 -x484 -x485 x486 x487 -x488 -x489 x490
0.86	c Total Number of Positive Atoms : 110
0.86	c 
0.86	c During searching:         0.834831 seconds elapsed.
0.86	c CPU time spent:           0.84 seconds.
0.86	c 
0.86	c =================================== END =====================================
0.86	c

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node38/watcher-31226-1149206619 -o ROOT/results/node38/solver-31226-1149206619 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user3/wildcat-rnp ROOT/tmp/node38/31226-1149206619/instance-31226-1149206619.opb 894798946 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.79 0.94 0.83 2/64 31108
/proc/meminfo: memFree=1423640/2055920 swapFree=4181196/4192956
[pid=31108] ppid=31106 vsize=5964 CPUtime=0
/proc/31108/stat : 31108 (wildcat-rnp) D 31106 31108 31063 0 -1 4194304 126 0 0 0 0 0 0 0 18 0 1 0 186328160 6107136 110 18446744073709551615 134512640 135438821 4294956656 18446744073709551615 135054477 0 2147483391 4096 16386 18446744072099781622 0 0 17 1 0 0
/proc/31108/statm: 1491 110 100 226 0 1262 0

Child status: 0
Real time (s): 0.867212
CPU time (s): 0.849869
CPU user time (s): 0.842871
CPU system time (s): 0.006998
CPU usage (%): 98.0002
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node38 on Fri Jun  2 00:03:39 UTC 2006


FILE ID= 31226-1149206619

PBS_JOBID= 293149

BENCH NAME= ROOT/tmp/node38/31226-1149206619/instance-31226-1149206619.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user3/wildcat-rnp ROOT/tmp/node38/31226-1149206619/instance-31226-1149206619.opb 894798946
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-31226-1149206619 -o ROOT/results/node38/solver-31226-1149206619 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user3/wildcat-rnp ROOT/tmp/node38/31226-1149206619/instance-31226-1149206619.opb 894798946

MD5SUM SOLVER= 433c0d3a0d963188fa818d869a2c809a
MD5SUM BENCH=  1a4510076d9024b805728ffe22c0d108

RANDOM SEED= 894798946


/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.267
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.267
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:       1423912 kB
Buffers:         16692 kB
Cached:         543664 kB
SwapCached:       3636 kB
Active:          78484 kB
Inactive:       490764 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1423912 kB
SwapTotal:     4192956 kB
SwapFree:      4181196 kB
Dirty:             200 kB
Writeback:           0 kB
Mapped:          14892 kB
Slab:            48748 kB
Committed_AS:   190240 kB
PageTables:       1484 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node38 on Fri Jun  2 00:03:40 UTC 2006