Trace number 36076

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
Pueblo 1.4SAT 42.0976 42.1169

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900669309.opb
MD5SUMe3a1beab9d06c0cee32a93d550c9a1ac
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 benchmark4.87226
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 645
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	c Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.04	c starting to Solve
0.04	c #variables read: 231 - #constraints read: 2707
42.11	c total time              : 42.09 s
42.11	s SATISFIABLE
42.11	v -x1 -x12 -x2 -x13 -x3 x14 -x4 -x15 -x5 -x16 -x6 -x17 x7 -x18 -x8 -x19 -x9 -x20 -x10 -x21 -x11 -x22 -x23 -x24 -x25 -x26 -x27 -x28
42.11	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
42.11	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
42.11	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
42.11	v -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 x121 -x132 -x142 x152 -x162 -x172
42.11	v -x182 -x192 -x202 -x212 -x222 -x122 -x143 -x153 -x163 -x173 -x183 -x193 -x203 x213 -x223 -x123 -x133 -x154 -x164 -x174 x184
42.11	v -x194 -x204 -x214 -x224 -x124 -x134 -x144 -x165 -x175 -x185 -x195 x205 -x215 -x225 -x125 -x135 -x145 -x155 -x176 -x186 x196
42.11	v -x206 -x216 -x226 x126 -x136 -x146 -x156 -x166 -x187 -x197 -x207 -x217 -x227 -x127 -x137 -x147 -x157 -x167 -x177 -x198 -x208
42.11	v -x218 x228 -x128 -x138 -x148 -x158 -x168 x178 -x188 -x209 -x219 -x229 -x129 -x139 x149 -x159 -x169 -x179 -x189 -x199 -x220
42.11	v -x230 -x130 -x140 -x150 -x160 x170 -x180 -x190 -x200 -x210 -x231 -x131 x141 -x151 -x161 -x171 -x181 -x191 -x201 -x211 -x221

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-36076-1149214622 -o ROOT/results/node38/solver-36076-1149214622 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node38/36076-1149214622/instance-36076-1149214622.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.84 0.94 0.90 2/64 412
/proc/meminfo: memFree=1418832/2055920 swapFree=4181196/4192956
[pid=412] ppid=410 vsize=2328 CPUtime=0
/proc/412/stat : 412 (Pueblo) R 410 412 367 0 -1 4194304 143 0 0 0 0 0 0 0 18 0 1 0 187128538 2383872 124 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 8574646 0 0 4096 0 0 0 0 17 1 0 0
/proc/412/statm: 582 127 108 16 0 11 0

[startup+10.0026 s]
/proc/loadavg: 0.87 0.94 0.90 2/64 412
/proc/meminfo: memFree=1416728/2055920 swapFree=4181196/4192956
[pid=412] ppid=410 vsize=4468 CPUtime=9.99
/proc/412/stat : 412 (Pueblo) R 410 412 367 0 -1 4194304 762 0 0 0 999 0 0 0 25 0 1 0 187128538 4575232 733 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134527547 0 0 4096 0 0 0 0 17 1 0 0
/proc/412/statm: 1117 733 205 16 0 558 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 4468

[startup+20.0095 s]
/proc/loadavg: 0.89 0.94 0.90 2/64 412
/proc/meminfo: memFree=1416408/2055920 swapFree=4181196/4192956
[pid=412] ppid=410 vsize=4792 CPUtime=19.99
/proc/412/stat : 412 (Pueblo) R 410 412 367 0 -1 4194304 845 0 0 0 1999 0 0 0 25 0 1 0 187128538 4907008 816 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134527772 0 0 4096 0 0 0 0 17 1 0 0
/proc/412/statm: 1198 816 205 16 0 639 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 4792

[startup+30.0165 s]
/proc/loadavg: 0.90 0.94 0.90 2/64 412
/proc/meminfo: memFree=1416152/2055920 swapFree=4181196/4192956
[pid=412] ppid=410 vsize=5028 CPUtime=30
/proc/412/stat : 412 (Pueblo) R 410 412 367 0 -1 4194304 910 0 0 0 3000 0 0 0 25 0 1 0 187128538 5148672 881 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 9041612 0 0 4096 0 0 0 0 17 1 0 0
/proc/412/statm: 1257 881 205 16 0 698 0
Current children cumulated CPU time (s) 30
Current children cumulated vsize (Kb) 5028

[startup+40.0224 s]
/proc/loadavg: 0.92 0.94 0.90 2/64 412
/proc/meminfo: memFree=1415960/2055920 swapFree=4181196/4192956
[pid=412] ppid=410 vsize=5200 CPUtime=40
/proc/412/stat : 412 (Pueblo) R 410 412 367 0 -1 4194304 949 0 0 0 4000 0 0 0 25 0 1 0 187128538 5324800 920 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134527715 0 0 4096 0 0 0 0 17 1 0 0
/proc/412/statm: 1300 920 205 16 0 741 0
Current children cumulated CPU time (s) 40
Current children cumulated vsize (Kb) 5200

Child status: 10
Real time (s): 42.1169
CPU time (s): 42.0976
CPU user time (s): 42.0896
CPU system time (s): 0.007998
CPU usage (%): 99.9542
Max. virtual memory (cumulated for all children) (Kb): 5200

Launcher Data (download as text)

Begin job on node38 on Fri Jun  2 02:17:03 UTC 2006


FILE ID= 36076-1149214622

PBS_JOBID= 294595

BENCH NAME= ROOT/tmp/node38/36076-1149214622/instance-36076-1149214622.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node38/36076-1149214622/instance-36076-1149214622.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-36076-1149214622 -o ROOT/results/node38/solver-36076-1149214622 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node38/36076-1149214622/instance-36076-1149214622.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  e3a1beab9d06c0cee32a93d550c9a1ac

RANDOM SEED= 166714772


/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:       1419040 kB
Buffers:         19184 kB
Cached:         545864 kB
SwapCached:       3636 kB
Active:          86624 kB
Inactive:       487360 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1419040 kB
SwapTotal:     4192956 kB
SwapFree:      4181196 kB
Dirty:             180 kB
Writeback:           0 kB
Mapped:          14892 kB
Slab:            48820 kB
Committed_AS:   212132 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 02:17:45 UTC 2006