Trace number 49683

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
minisat+ 1.14OPT5 1.3188 1.32524

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/
manquiho/logic_synthesis/normalized-ex4inp.r.opb
MD5SUMbc692dc92013616c4d370a3b9a33f673
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark5
Best CPU time to get the best result obtained on this benchmark0.183971
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 5
Optimality of the best value was proved YES
Number of variables240
Total number of constraints91
Number of constraints which are clauses91
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint8
Maximum length of a constraint176
Number of terms in the objective function 240
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 240
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 240
Number of bits of the biggest sum of numbers8
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 Parsing PB file...
0.09	c Converting 91 PB-constraints to clauses...
0.10	c   -- Unit propagations: (none)
0.10	c   -- Detecting intervals from adjacent constraints: (none)
0.10	c   -- Clauses(.)/Splits(s): ...........................................................................................
0.10	c ==================================[MINISAT+]==================================
0.10	c | Conflicts | Original         | Learnt                           | Progress |
0.10	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.10	c ==============================================================================
0.10	c |         0 |      91    10053 |      30       0        0     nan |  0.000 % |
0.10	c ==============================================================================
0.10	c Found solution: 8
0.10	o 8
0.10	c ---[   0]---> Sorter-cost: 7168     Base:
0.15	c ==================================[MINISAT+]==================================
0.15	c | Conflicts | Original         | Learnt                           | Progress |
0.15	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.15	c ==============================================================================
0.15	c |         0 |    5495    22640 |    1831       0        0     nan |  0.000 % |
0.16	c |       104 |    5495    22640 |    2014     104     8075    77.6 | 24.488 % |
0.17	c ==============================================================================
0.17	c Found solution: 6
0.17	o 6
0.17	c ---[   0]---> Sorter-cost:    0     Base:
0.21	c ==================================[MINISAT+]==================================
0.21	c | Conflicts | Original         | Learnt                           | Progress |
0.21	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.21	c ==============================================================================
0.21	c |       131 |    5485    22620 |    1828     131    10900    83.2 | 24.488 % |
0.22	c |       231 |    5485    22620 |    2010     231    22392    96.9 | 24.852 % |
0.24	c |       384 |    5485    22620 |    2211     384    43244   112.6 | 24.852 % |
0.27	c |       611 |    5485    22620 |    2433     611    69429   113.6 | 24.852 % |
0.32	c |       948 |    5485    22620 |    2676     948   106044   111.9 | 24.852 % |
0.40	c |      1455 |    5485    22620 |    2944    1455   154670   106.3 | 24.852 % |
0.47	c ==============================================================================
0.47	c Found solution: 5
0.47	o 5
0.47	c ---[   0]---> Sorter-cost:    0     Base:
0.51	c ==================================[MINISAT+]==================================
0.51	c | Conflicts | Original         | Learnt                           | Progress |
0.51	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.51	c ==============================================================================
0.51	c |      1843 |    5486    22624 |    1828    1842   179188    97.3 | 24.852 % |
0.53	c |      1943 |    5486    22624 |    2010    1942   182290    93.9 | 24.872 % |
0.56	c |      2094 |    5475    22598 |    2211    1174   118067   100.6 | 25.015 % |
0.60	c |      2320 |    5475    22598 |    2433    1400   133028    95.0 | 25.015 % |
0.66	c |      2657 |    5475    22598 |    2676    1737   157690    90.8 | 25.015 % |
0.77	c |      3164 |    5475    22598 |    2944    2244   192827    85.9 | 25.015 % |
0.92	c |      3924 |    5475    22598 |    3238    3004   239248    79.6 | 25.015 % |
1.16	c |      5066 |    5475    22598 |    3562    4146   300062    72.4 | 25.015 % |
1.32	c ==============================================================================
1.32	c Optimal solution: 5
1.32	s OPTIMUM FOUND
1.32	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
1.32	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
1.32	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
1.32	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
1.32	v -x105 -x106 x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124 -x125
1.32	v -x126 -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146
1.32	v -x147 -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167
1.32	v -x168 -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176 -x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 x187 -x188
1.32	v -x189 -x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 x209
1.32	v -x210 -x211 -x212 -x213 -x214 -x215 -x216 -x217 -x218 -x219 x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229 -x230
1.32	v -x231 -x232 -x233 -x234 -x235 -x236 -x237 -x238 -x239 -x240
1.32	c _______________________________________________________________________________
1.32	c 
1.32	c restarts              : 17
1.32	c conflicts             : 5827           (4432 /sec)
1.32	c decisions             : 15626          (11885 /sec)
1.32	c propagations          : 0              (0 /sec)
1.32	c inspects              : 0              (0 /sec)
1.32	c CPU time              : 1.3148 s
1.32	c _______________________________________________________________________________

Verifier Data (download as text)

OK	5

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/node86/watcher-49683-1149883714 -o ROOT/results/node86/solver-49683-1149883714 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node86/49683-1149883714/instance-49683-1149883714.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/68 3801
/proc/meminfo: memFree=1551320/2055892 swapFree=4084792/4096564
[pid=3801] ppid=3799 vsize=1048 CPUtime=0
/proc/3801/stat : 3801 (minisat+) R 3799 3801 3755 0 -1 4194304 118 0 0 0 0 0 0 0 19 0 1 0 254010588 1073152 104 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135003237 0 0 4096 16386 0 0 0 17 1 0 0
/proc/3801/statm: 262 104 72 215 0 44 0

Child status: 30
Real time (s): 1.32524
CPU time (s): 1.3188
CPU user time (s): 1.3148
CPU system time (s): 0.003999
CPU usage (%): 99.5143
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node86 on Fri Jun  9 20:08:34 UTC 2006


FILE ID= 49683-1149883714

PBS_JOBID= 384768

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-ex4inp.r.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node86/49683-1149883714/instance-49683-1149883714.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node86/watcher-49683-1149883714 -o ROOT/results/node86/solver-49683-1149883714 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node86/49683-1149883714/instance-49683-1149883714.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  bc692dc92013616c4d370a3b9a33f673

RANDOM SEED= 271530336


/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.214
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.19
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.214
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:      2055892 kB
MemFree:       1551720 kB
Buffers:         32380 kB
Cached:         404856 kB
SwapCached:       2928 kB
Active:         112360 kB
Inactive:       333544 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1551720 kB
SwapTotal:     4096564 kB
SwapFree:      4084792 kB
Dirty:             172 kB
Writeback:           0 kB
Mapped:          15160 kB
Slab:            44880 kB
Committed_AS:   600248 kB
PageTables:       1300 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node86 on Fri Jun  9 20:08:35 UTC 2006