Trace number 50350

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
bsolo 2006/05OPT17 0.503922 0.517987

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
bounded_golomb_rulers/normalized-bogr_6.opb
MD5SUMda335afc6b5d5727dca7fb9193531871
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.047991
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 variables139
Total number of constraints216
Number of constraints which are clauses1
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 constraint1
Maximum length of a constraint24
Number of terms in the objective function 6
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 46
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 324
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 Time Limit set via PBTIMEOUT to 1800
0.02	c INFO: OSL Context initialized.
0.03	c Initial problem consists of 139 variables and 216 constraints.
0.03	c No problem reductions applied in OPT. instance.
0.03	c	preprocess terminated. Elapsed time: 0.024
0.03	c After prepocess the problem consists of 138 variables and 215 constraints.
0.03	c Initial Lower Bound: 15
0.04	c Sol. found (all assignments made)...
0.04	o 30
0.04	c NEW SOLUTION FOUND: 30 @ 0.025
0.04	c Sol. found (all assignments made)...
0.04	o 22
0.04	c NEW SOLUTION FOUND: 22 @ 0.027
0.05	c Sol. found (all assignments made)...
0.05	o 20
0.05	c NEW SOLUTION FOUND: 20 @ 0.039
0.06	c Sol. found (all assignments made)...
0.06	o 18
0.06	c NEW SOLUTION FOUND: 18 @ 0.049
0.11	c Restart #1 #Var: 138 LB: 15 @ 0.098
0.20	c Sol. found (all assignments made)...
0.20	o 17
0.20	c NEW SOLUTION FOUND: 17 @ 0.193
0.30	c Restart #2 #Var: 125 LB: 15 @ 0.29
0.48	c Restart #3 #Var: 123 LB: 15 @ 0.47
0.51	s OPTIMUM FOUND
0.51	c Cost: 17
0.51	v -x1 x2 -x3 -x4 -x5 x139 x24 x25 x26 -x27 -x28 -x29 x30 x31 -x32 -x33 -x138 -x18 -x19 x20 -x21 -x22 -x23 -x137 -x136 -x135 -x134
0.51	v -x133 -x6 -x7 x8 -x9 -x10 -x11 -x132 -x131 -x130 -x129 -x128 -x127 x126 x125 -x124 x123 x122 x121 x120 x119 -x12 -x13 -x14 -x15
0.51	v -x16 -x17 -x118 -x117 -x116 -x115 -x114 -x113 -x112 -x111 -x110 -x109 -x108 -x107 -x106 -x105 x104 x103 -x102 x101 x100 x99
0.51	v -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 x71
0.51	v 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.51	v x38 x37 x36 x35 x34
0.51	c Exit Code: 30
0.51	c Total time: 0.5 s

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/node80/watcher-50350-1149941891 -o ROOT/results/node80/solver-50350-1149941891 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node80/50350-1149941891/instance-50350-1149941891.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.89 0.49 0.23 3/67 8393
/proc/meminfo: memFree=1739408/2055888 swapFree=4085444/4096564
[pid=8393] ppid=8391 vsize=18548 CPUtime=0
/proc/8393/stat : 8393 (runsolver) R 8391 8393 8347 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 259827689 18993152 278 18446744073709551615 4194304 4264532 548682069056 18446744073709551615 268451771415 0 0 4096 24578 0 0 0 17 1 0 0
/proc/8393/statm: 4637 278 242 17 0 2626 0

Child status: 30
Real time (s): 0.517987
CPU time (s): 0.503922
CPU user time (s): 0.495924
CPU system time (s): 0.007998
CPU usage (%): 97.2847
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node80 on Sat Jun 10 12:18:11 UTC 2006


FILE ID= 50350-1149941891

PBS_JOBID= 385799

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/bounded_golomb_rulers/normalized-bogr_6.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node80/50350-1149941891/instance-50350-1149941891.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node80/watcher-50350-1149941891 -o ROOT/results/node80/solver-50350-1149941891 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node80/50350-1149941891/instance-50350-1149941891.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  da335afc6b5d5727dca7fb9193531871

RANDOM SEED= 525728017


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1739616 kB
Buffers:         30344 kB
Cached:         213700 kB
SwapCached:       2388 kB
Active:          62884 kB
Inactive:       189844 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1739616 kB
SwapTotal:     4096564 kB
SwapFree:      4085444 kB
Dirty:             148 kB
Writeback:           0 kB
Mapped:          16648 kB
Slab:            50228 kB
Committed_AS:   684828 kB
PageTables:       1276 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node80 on Sat Jun 10 12:18:12 UTC 2006