Trace number 46534

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.4OPT17 0.093984 0.0998481

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_6.opb
MD5SUMa6fbaa86ad104839735089987b256e67
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark17
Best CPU time to get the best result obtained on this benchmark0.069989
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 17
Optimality of the best value was proved YES
Number of variables141
Total number of constraints215
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 constraints215
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 323
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.02	c starting to Solve
0.02	c #variables read: 141 - #constraints read: 216
0.02	o 32
0.02	o 28
0.02	o 27
0.02	o 26
0.02	o 23
0.02	o 18
0.03	o 17
0.09	c optimum objective found = 17
0.09	c total time              : 0.09 s
0.09	s OPTIMUM FOUND
0.09	v x1 -x2 -x3 -x4 x5 -x6 x25 -x26 -x27 x28 -x29 -x30 -x31 -x32 -x33 -x34 x35 -x36 -x141 -x19 x20 x21 -x22 -x23 -x24 -x140 -x139 -x138
0.09	v x137 x136 -x7 -x8 x9 -x10 -x11 -x12 -x135 -x134 -x133 -x132 x131 x130 x129 x128 -x127 x126 x125 x124 x123 x122 -x13 -x14 -x15
0.09	v -x16 -x17 -x18 -x121 -x120 -x119 -x118 -x117 -x116 -x115 x114 x113 x112 x111 -x110 x109 x108 x107 x106 -x105 x104 x103 -x102
0.09	v -x101 x100 x99 x98 x97 -x96 x95 x94 x93 -x92 -x91 -x90 -x89 -x88 x87 -x86 -x85 -x84 x83 x82 x81 x80 x79 x78 -x77 x76 x75 x74 x73 -x72
0.09	v 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 x44 x43 x42 x41 x40 x39
0.09	v x38 x37

Verifier Data (download as text)

OK	17

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.97 0.97 0.91 2/67 12124
/proc/meminfo: memFree=1469344/2055888 swapFree=4085408/4096564
[pid=12124] ppid=12122 vsize=2336 CPUtime=0
/proc/12124/stat : 12124 (Pueblo) R 12122 12124 12078 0 -1 4194304 135 0 0 0 0 0 0 0 18 0 1 0 243799209 2392064 119 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 11739368 0 0 4096 0 0 0 0 17 1 0 0
/proc/12124/statm: 584 122 107 16 0 11 0

Child status: 30
Real time (s): 0.0998481
CPU time (s): 0.093984
CPU user time (s): 0.092985
CPU system time (s): 0.000999
CPU usage (%): 94.127
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node83 on Thu Jun  8 15:46:39 UTC 2006


FILE ID= 46534-1149781598

PBS_JOBID= 373066

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

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  a6fbaa86ad104839735089987b256e67

RANDOM SEED= 606268519


/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.265
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	: 6006.16
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.265
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	: 5999.44
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1469552 kB
Buffers:         36788 kB
Cached:         478872 kB
SwapCached:       2364 kB
Active:         102352 kB
Inactive:       422028 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1469552 kB
SwapTotal:     4096564 kB
SwapFree:      4085408 kB
Dirty:             248 kB
Writeback:           0 kB
Mapped:          16884 kB
Slab:            48616 kB
Committed_AS:   494396 kB
PageTables:       1284 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node83 on Thu Jun  8 15:46:39 UTC 2006