Trace number 366929

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.14OPT1 0.170973 0.17207

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/
factor/normalized-factor-sizeN=20-sizeP=11-sizeQ=20-496708.opb
MD5SUMd30c59413d5aa00e4d7af3dc32259ce0
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark1
Best CPU time to get the best result obtained on this benchmark0.017996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 1
Optimality of the best value was proved YES
Number of variables251
Total number of constraints661
Number of constraints which are clauses660
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint220
Number of terms in the objective function 11
Biggest coefficient in the objective function 1024
Number of bits for the biggest coefficient in the objective function 11
Sum of the numbers in the objective function 2047
Number of bits of the sum of numbers in the objective function 11
Biggest number in a constraint 536870912
Number of bits of the biggest number in a constraint 30
Biggest sum of numbers in a constraint 2146929733
Number of bits of the biggest sum of numbers31
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/0.00	c Parsing PB file...
0.00/0.02	c Converting 662 PB-constraints to clauses...
0.00/0.02	c   -- Unit propagations: (none)
0.00/0.02	c   -- Detecting intervals from adjacent constraints: #
0.00/0.02	c   -- Clauses(.)/Splits(s): ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
0.00/0.02	c ---[   0]---> Sorter-cost: 2910     Base: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
0.00/0.07	c ==================================[MINISAT+]==================================
0.00/0.07	c | Conflicts | Original         | Learnt                           | Progress |
0.00/0.07	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00/0.07	c ==============================================================================
0.00/0.07	c |         0 |    8100    19083 |    2700       0        0     nan |  0.000 % |
0.00/0.08	c |       100 |    8100    19083 |    2970     100     3636    36.4 |  6.150 % |
0.09/0.11	c |       250 |    7910    18651 |    3267     232     7446    32.1 |  7.985 % |
0.09/0.16	c ==============================================================================
0.09/0.16	c Found solution: 2
0.09/0.16	o 2
0.09/0.16	c ==================================[MINISAT+]==================================
0.09/0.16	c | Conflicts | Original         | Learnt                           | Progress |
0.09/0.16	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.09/0.16	c ==============================================================================
0.09/0.16	c |       435 |       0        0 |       0       0        0     nan |  7.985 % |
0.09/0.16	c ==============================================================================
0.09/0.16	c Found solution: 1
0.09/0.16	o 1
0.09/0.17	c Optimal solution: 1
0.09/0.17	s OPTIMUM FOUND
0.09/0.17	v x1 -x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x32 -x12 -x33 -x13 x34 x14 -x35 -x15 -x36 -x16 -x37 -x17 x38 x18 -x39 -x19 -x40 -x20
0.09/0.17	v -x41 -x21 x42 x22 -x43 -x23 x44 x24 -x45 -x25 -x46 -x26 x47 x27 x48 x28 x49 x29 x50 x30 -x51 -x31 -x72 -x73 -x74 -x75 -x76 -x77 -x78
0.09/0.17	v -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103
0.09/0.17	v -x104 -x105 -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124
0.09/0.17	v -x125 -x126 -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145
0.09/0.17	v -x146 -x147 -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166
0.09/0.17	v -x167 -x168 -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176 -x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187
0.09/0.17	v -x188 -x189 -x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208
0.09/0.17	v -x209 -x210 -x211 -x212 -x213 -x214 -x215 -x216 -x217 -x218 -x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229
0.09/0.17	v -x230 -x231 -x232 -x233 -x234 -x235 -x236 -x237 -x238 -x239 -x240 -x241 -x242 -x243 -x244 -x245 -x246 -x247 -x248 -x249 -x250
0.09/0.17	v -x251 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71
0.09/0.17	c _______________________________________________________________________________
0.09/0.17	c 
0.09/0.17	c restarts              : 4
0.09/0.17	c conflicts             : 435            (2590 /sec)
0.09/0.17	c decisions             : 741            (4411 /sec)
0.09/0.17	c propagations          : 0              (0 /sec)
0.09/0.17	c inspects              : 0              (0 /sec)
0.09/0.17	c CPU time              : 0.167974 s
0.09/0.17	c _______________________________________________________________________________

Verifier Data (download as text)

OK	1

Conversion Script Data (download as text)

/tmp/evaluation/366929-1177068105/instance-366929-1177068105.opb is already a linear file

Watcher Data (download as text)

runsolver version 3.2.2 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node37/watcher-366929-1177068105 -o ROOT/results/node37/solver-366929-1177068105 -C 1800 -W 3600 -M 1800 --output-limit 1,15 /tmp/evaluation/366929-1177068105/minisat+ /tmp/evaluation/366929-1177068105/instance-366929-1177068105.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.78 0.95 0.98 3/78 15066
/proc/meminfo: memFree=1751120/2055920 swapFree=4159012/4192956
[pid=15066] ppid=15064 vsize=1048 CPUtime=0
/proc/15066/stat : 15066 (minisat+) R 15064 15066 14959 0 -1 4194304 114 0 0 0 0 0 0 0 18 0 1 0 154722937 1073152 99 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135007481 0 0 4096 16386 0 0 0 17 1 0 0
/proc/15066/statm: 262 99 74 215 0 44 0

[startup+0.012169 s]
/proc/loadavg: 0.78 0.95 0.98 3/78 15066
/proc/meminfo: memFree=1751120/2055920 swapFree=4159012/4192956
[pid=15066] ppid=15064 vsize=1180 CPUtime=0
/proc/15066/stat : 15066 (minisat+) R 15064 15066 14959 0 -1 4194304 133 0 0 0 0 0 0 0 18 0 1 0 154722937 1208320 118 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 134618819 0 0 4096 16386 0 0 0 17 1 0 0
/proc/15066/statm: 295 118 74 215 0 77 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 1180

[startup+0.101184 s]
/proc/loadavg: 0.78 0.95 0.98 3/78 15066
/proc/meminfo: memFree=1751120/2055920 swapFree=4159012/4192956
[pid=15066] ppid=15064 vsize=1972 CPUtime=0.09
/proc/15066/stat : 15066 (minisat+) R 15064 15066 14959 0 -1 4194304 360 0 0 0 9 0 0 0 18 0 1 0 154722937 2019328 345 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135011021 0 0 4096 16386 0 0 0 17 1 0 0
/proc/15066/statm: 493 345 109 215 0 275 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1972

Solver just ended. Dumping a history of the last processes samples

Child status: 30
Real time (s): 0.17207
CPU time (s): 0.170973
CPU user time (s): 0.167974
CPU system time (s): 0.002999
CPU usage (%): 99.3625
Max. virtual memory (cumulated for all children) (KiB): 1972

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.167974
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 388
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 10
involuntary context switches= 3

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node37 on Fri Apr 20 11:21:45 UTC 2007

IDJOB= 366929
IDBENCH= 2959
IDSOLVER= 156
FILE ID= node37/366929-1177068105

PBS_JOBID= 4640266

Free space on /tmp= 66414 MiB

SOLVER NAME= minisat+ 1.14
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=20-sizeP=11-sizeQ=20-496708.opb
COMMAND LINE= /tmp/evaluation/366929-1177068105/minisat+ /tmp/evaluation/366929-1177068105/instance-366929-1177068105.opb            
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node37/convwatcher-366929-1177068105 -o ROOT/results/node37/conversion-366929-1177068105 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/366929-1177068105/instance-366929-1177068105.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node37/watcher-366929-1177068105 -o ROOT/results/node37/solver-366929-1177068105 -C 1800 -W 3600 -M 1800 --output-limit 1,15  /tmp/evaluation/366929-1177068105/minisat+ /tmp/evaluation/366929-1177068105/instance-366929-1177068105.opb            

META MD5SUM SOLVER= e46aded85e5f265b61da9cdcce06370e
MD5SUM BENCH=  d30c59413d5aa00e4d7af3dc32259ce0

RANDOM SEED= 35245758

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node37.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.281
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.281
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:       1751592 kB
Buffers:         40328 kB
Cached:         173076 kB
SwapCached:       2292 kB
Active:         127248 kB
Inactive:       109780 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1751592 kB
SwapTotal:     4192956 kB
SwapFree:      4159012 kB
Dirty:            2508 kB
Writeback:           0 kB
Mapped:          31248 kB
Slab:            52632 kB
Committed_AS:  1986208 kB
PageTables:       2000 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66414 MiB

End job on node37 on Fri Apr 20 11:21:45 UTC 2007