Trace number 32413

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-skc 0.8.0SAT 0.401938 0.405921

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1111227418.opb
MD5SUM1d0806e8d2a90a81262a0ea6810fc3cb
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.244961
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables169
Total number of constraints101
Number of constraints which are clauses30
Number of constraints which are cardinality constraints (but not clauses)70
Number of constraints which are nor clauses,nor cardinality constraints1
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 38
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 1171
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 
0.00	c wildcat-skc (VERSION 0.8.0-lite-skc-devel)
0.00	c Developed by L. Liu  and M. Truszczynski 
0.00	c Last built on Tue 23 May 2006 09:27:47 PM EDT
0.00	c 
0.00	c ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node39/32413-1149212280/instance-32413-1149212280.opb 487266403 
0.00	c =================================== BEGIN ===================================
0.00	c 
0.00	c Random Number Seed: 487266403
0.00	c Noise: 0.1 (10 : 100) 
0.40	c Starting searching:
0.40	c phase 1 ... vc 
0.40	s SATISFIABLE
0.40	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
0.40	v x29 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 x46 -x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54
0.40	v -x55 -x56 -x57 -x58 -x59 -x60 -x61 x62 -x63 -x64 -x65 -x66 x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80
0.40	v -x81 -x82 -x83 x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105
0.40	v -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124 x125 -x126
0.40	v -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147
0.40	v -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 x156 -x157 -x158 -x159 x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168
0.40	v -x169
0.40	c Total Number of Positive Atoms : 13
0.40	c 
0.40	c During searching:         0.397161 seconds elapsed.
0.40	c CPU time spent:           0.4 seconds.
0.40	c 
0.40	c =================================== END =====================================
0.40	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/node39/watcher-32413-1149212280 -o ROOT/results/node39/solver-32413-1149212280 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node39/32413-1149212280/instance-32413-1149212280.opb 487266403 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.85 0.94 0.90 2/64 30688
/proc/meminfo: memFree=1351336/2055920 swapFree=4180888/4192956
[pid=30688] ppid=30686 vsize=6540 CPUtime=0
/proc/30688/stat : 30688 (wildcat-skc) R 30686 30688 30643 0 -1 4194304 303 0 0 0 0 0 0 0 18 0 1 0 186894279 6696960 287 18446744073709551615 134512640 135438821 4294956656 18446744073709551615 135002082 0 0 4096 16386 0 0 0 17 1 0 0
/proc/30688/statm: 1670 292 111 226 0 1441 0

Child status: 0
Real time (s): 0.405921
CPU time (s): 0.401938
CPU user time (s): 0.399939
CPU system time (s): 0.001999
CPU usage (%): 99.0188
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node39 on Fri Jun  2 01:38:00 UTC 2006


FILE ID= 32413-1149212280

PBS_JOBID= 294236

BENCH NAME= ROOT/tmp/node39/32413-1149212280/instance-32413-1149212280.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node39/32413-1149212280/instance-32413-1149212280.opb 487266403
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node39/watcher-32413-1149212280 -o ROOT/results/node39/solver-32413-1149212280 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node39/32413-1149212280/instance-32413-1149212280.opb 487266403

MD5SUM SOLVER= e3d27fcb27e96c4c5fdaee74465b047d
MD5SUM BENCH=  1d0806e8d2a90a81262a0ea6810fc3cb

RANDOM SEED= 487266403


/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.213
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	: 5931.00
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.213
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:       1351544 kB
Buffers:         43836 kB
Cached:         586416 kB
SwapCached:       4052 kB
Active:         215248 kB
Inactive:       423948 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1351544 kB
SwapTotal:     4192956 kB
SwapFree:      4180888 kB
Dirty:             200 kB
Writeback:           0 kB
Mapped:          14820 kB
Slab:            51184 kB
Committed_AS:   180664 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node39 on Fri Jun  2 01:38:00 UTC 2006