Trace number 46538

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.4OPT25 1.34679 1.35232

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_7.opb
MD5SUMa28f5b3e9b4b12f9ccee04abccbf9327
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark25
Best CPU time to get the best result obtained on this benchmark0.928857
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 25
Optimality of the best value was proved YES
Number of variables238
Total number of constraints398
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 constraints398
Minimum length of a constraint12
Maximum length of a constraint25
Number of terms in the objective function 6
Biggest coefficient in the objective function 32
Number of bits for the biggest coefficient in the objective function 6
Sum of the numbers in the objective function 63
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 64
Number of bits of the biggest number in a constraint 7
Biggest sum of numbers in a constraint 349
Number of bits of the biggest sum of numbers9
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.03	c starting to Solve
0.03	c #variables read: 238 - #constraints read: 399
0.05	o 32
0.06	o 30
0.07	o 25
1.35	c optimum objective found = 25
1.35	c total time              : 1.34 s
1.35	s OPTIMUM FOUND
1.35	v x1 -x2 -x3 x4 x5 -x6 -x31 -x32 -x33 -x34 x35 -x36 x37 -x38 x39 -x40 x41 -x42 -x238 -x25 x26 -x27 x28 -x29 -x30 -x237 -x236 -x235
1.35	v x234 -x233 x19 x20 -x21 -x22 -x23 -x24 -x232 -x231 -x230 -x229 -x228 -x227 x226 -x225 -x224 x223 -x222 x221 x220 -x219 -x7 x8
1.35	v -x9 -x10 -x11 -x12 -x218 -x217 -x216 x215 -x214 -x213 -x212 x211 -x210 x209 x208 -x207 x206 -x205 x204 x203 -x202 x201 x200
1.35	v x199 x198 x197 x196 x195 x194 x193 x192 x191 x190 x189 -x13 -x14 -x15 -x16 -x17 -x18 -x188 -x187 -x186 x185 x184 -x183 -x182
1.35	v -x181 -x180 -x179 x178 x177 x176 x175 -x174 -x173 -x172 x171 x170 -x169 x168 x167 x166 x165 x164 x163 x162 x161 x160 x159 x158
1.35	v x157 x156 x155 x154 x153 x152 x151 x150 x149 x148 x147 x146 x145 x144 x143 x142 x141 x140 x139 x138 x137 x136 x135 -x134 -x133
1.35	v -x132 -x131 x130 x129 x128 -x127 -x126 -x125 -x124 -x123 x122 x121 x120 x119 x118 x117 -x116 -x115 -x114 x113 x112 -x111 x110
1.35	v x109 x108 x107 x106 x105 x104 x103 x102 x101 x100 x99 x98 x97 x96 x95 x94 x93 x92 x91 x90 x89 x88 x87 x86 x85 x84 x83 x82 x81 x80 x79
1.35	v x78 x77 x76 x75 x74 x73 x72 x71 x70 -x69 x68 x67 x66 x65 x64 x63 x62 x61 x60 x59 x58 x57 x56 x55 x54 x53 x52 x51 x50 x49 x48 x47 x46 x45
1.35	v x44 x43

Verifier Data (download as text)

OK	25

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.92 0.97 0.92 3/64 1742
/proc/meminfo: memFree=1665000/2055920 swapFree=4181756/4192956
[pid=1742] ppid=1740 vsize=2328 CPUtime=0
/proc/1742/stat : 1742 (Pueblo) R 1740 1742 1693 0 -1 4194304 99 0 0 0 0 0 0 0 18 0 1 0 243985561 2383872 82 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 6893656 0 0 4096 0 0 0 0 17 1 0 0
/proc/1742/statm: 582 99 85 16 0 11 0

Child status: 30
Real time (s): 1.35232
CPU time (s): 1.34679
CPU user time (s): 1.3438
CPU system time (s): 0.002999
CPU usage (%): 99.5914
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node67 on Thu Jun  8 16:12:42 UTC 2006


FILE ID= 46538-1149783162

PBS_JOBID= 373118

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

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  a28f5b3e9b4b12f9ccee04abccbf9327

RANDOM SEED= 409623903


/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.264
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.264
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:       1665208 kB
Buffers:         32064 kB
Cached:         297104 kB
SwapCached:       2944 kB
Active:         103152 kB
Inactive:       234856 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1665208 kB
SwapTotal:     4192956 kB
SwapFree:      4181756 kB
Dirty:             184 kB
Writeback:           0 kB
Mapped:          14788 kB
Slab:            38684 kB
Committed_AS:   469360 kB
PageTables:       1472 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node67 on Thu Jun  8 16:12:43 UTC 2006