Trace number 359768

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 2007-03-21SAT 0.022995 0.0245911

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900670756.opb
MD5SUM11371eec29d871c470e0cb7778802319
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.022995
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables231
Total number of constraints2707
Number of constraints which are clauses2684
Number of constraints which are cardinality constraints (but not clauses)22
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint110
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 25
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 683
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

Solver Data (download as text)

0.00/0.00	c 
0.00/0.00	c wildcat-skc (VERSION 0.8.0-lite-skc-devel)
0.00/0.00	c Developed by L. Liu  and M. Truszczynski 
0.00/0.00	c Last built on Sun 18 Mar 2007 03:03:20 PM EDT
0.00/0.00	c 
0.00/0.00	c /tmp/evaluation/359768-1176942081/wildcat-skc /tmp/evaluation/359768-1176942081/instance-359768-1176942081.opb 567810331 
0.00/0.00	c =================================== BEGIN ===================================
0.00/0.00	c 
0.00/0.00	c Random Number Seed: 567810331
0.00/0.00	c Noise: 0.1 (10 : 100) 
0.00/0.02	c Starting searching:
0.00/0.02	c phase 1 ... vc 
0.00/0.02	s SATISFIABLE
0.00/0.02	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
0.00/0.02	v -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 -x55
0.00/0.02	v -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 -x81
0.00/0.02	v -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.00/0.02	v -x106 x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 x121 -x122 x123 -x124 -x125 -x126
0.00/0.02	v -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147
0.00/0.02	v x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 x160 -x161 -x162 x163 -x164 -x165 -x166 -x167 -x168
0.00/0.02	v -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176 x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188 x189
0.00/0.02	v -x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 x201 -x202 -x203 -x204 x205 -x206 -x207 -x208 -x209 -x210
0.00/0.02	v -x211 x212 -x213 -x214 -x215 -x216 -x217 -x218 -x219 -x220 -x221 -x222 -x223 -x224 -x225 x226 -x227 -x228 -x229 -x230 -x231
0.00/0.02	c Total Number of Positive Atoms : 22
0.00/0.02	c 
0.00/0.02	c During searching:         0.014031 seconds elapsed.
0.00/0.02	c CPU time spent:           0.02 seconds.
0.00/0.02	c 
0.00/0.02	c =================================== END =====================================
0.00/0.02	c

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node21/watcher-359768-1176942081 -o ROOT/results/node21/solver-359768-1176942081 -C 1800 -W 3600 -M 1800 --output-limit 1,15 /tmp/evaluation/359768-1176942081/wildcat-skc /tmp/evaluation/359768-1176942081/instance-359768-1176942081.opb 567810331 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.12 1.09 1.02 3/77 15771
/proc/meminfo: memFree=1502592/2055920 swapFree=4160292/4192956
[pid=15771] ppid=15769 vsize=6236 CPUtime=0
/proc/15771/stat : 15771 (wildcat-skc) R 15769 15771 15025 0 -1 4194304 226 0 0 0 0 0 0 0 18 0 1 0 142125362 6385664 210 18446744073709551615 134512640 135438881 4294956608 18446744073709551615 135002146 0 0 4096 16386 0 0 0 17 1 0 0
/proc/15771/statm: 1559 211 106 226 0 1330 0

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.0245911
CPU time (s): 0.022995
CPU user time (s): 0.020996
CPU system time (s): 0.001999
CPU usage (%): 93.5095
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.020996
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 385
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 8
involuntary context switches= 0

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node21 on Thu Apr 19 00:21:21 UTC 2007

IDJOB= 359768
IDBENCH= 1319
IDSOLVER= 162
FILE ID= node21/359768-1176942081

PBS_JOBID= 4605718

Free space on /tmp= 66389 MiB

SOLVER NAME= wildcat-skc 2007-03-21
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/tsp/normalized-t3002.11tsp11.1900670756.opb
COMMAND LINE= /tmp/evaluation/359768-1176942081/wildcat-skc /tmp/evaluation/359768-1176942081/instance-359768-1176942081.opb 567810331
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node21/watcher-359768-1176942081 -o ROOT/results/node21/solver-359768-1176942081 -C 1800 -W 3600 -M 1800 --output-limit 1,15  /tmp/evaluation/359768-1176942081/wildcat-skc /tmp/evaluation/359768-1176942081/instance-359768-1176942081.opb 567810331

META MD5SUM SOLVER= 05d21ee76b90579709a9929b8e99937a
MD5SUM BENCH=  11371eec29d871c470e0cb7778802319

RANDOM SEED= 567810331

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node21.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.232
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.232
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:       1503064 kB
Buffers:         33356 kB
Cached:         451620 kB
SwapCached:      10880 kB
Active:         113228 kB
Inactive:       398236 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1503064 kB
SwapTotal:     4192956 kB
SwapFree:      4160292 kB
Dirty:            2396 kB
Writeback:           0 kB
Mapped:          30196 kB
Slab:            26952 kB
Committed_AS:  1047200 kB
PageTables:       1784 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66389 MiB

End job on node21 on Thu Apr 19 00:21:21 UTC 2007