Trace number 34767

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 NameAnswerCPU timeWall clock time
minisat+ 1.14SAT 0.027995 0.031875

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga13_12_sat_pb.cnf.cr.opb
MD5SUM774e61576b805c95b87ab57992a33004
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.002999
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables234
Total number of constraints193
Number of constraints which are clauses168
Number of constraints which are cardinality constraints (but not clauses)25
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint6
Maximum length of a constraint13
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 14
Number of bits of the biggest sum of numbers4
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c Parsing PB file...
0.02	c Converting 193 PB-constraints to clauses...
0.02	c   -- Unit propagations: (none)
0.02	c   -- Detecting intervals from adjacent constraints: (none)
0.02	c   -- Clauses(.)/Splits(s): ........................................................................................................................................................................
0.02	c ---[  24]---> BDD-cost:   21
0.02	c ---[  23]---> BDD-cost:   21
0.02	c ---[  22]---> BDD-cost:   21
0.02	c ---[  21]---> BDD-cost:   21
0.02	c ---[  20]---> BDD-cost:   21
0.02	c ---[  19]---> BDD-cost:   21
0.02	c ---[  18]---> BDD-cost:   21
0.02	c ---[  17]---> BDD-cost:   21
0.02	c ---[  16]---> BDD-cost:   21
0.02	c ---[  15]---> BDD-cost:   21
0.02	c ---[  14]---> BDD-cost:   21
0.02	c ---[  13]---> BDD-cost:   21
0.02	c ---[  12]---> BDD-cost:   21
0.02	c ---[  11]---> BDD-cost:    9
0.02	c ---[  10]---> BDD-cost:    9
0.02	c ---[   9]---> BDD-cost:    9
0.02	c ---[   8]---> BDD-cost:    9
0.02	c ---[   7]---> BDD-cost:    9
0.02	c ---[   6]---> BDD-cost:    9
0.02	c ---[   5]---> BDD-cost:   11
0.02	c ---[   4]---> BDD-cost:   11
0.02	c ---[   3]---> BDD-cost:   11
0.02	c ---[   2]---> BDD-cost:   11
0.02	c ---[   1]---> BDD-cost:   11
0.02	c ---[   0]---> BDD-cost:   11
0.02	c ==================================[MINISAT+]==================================
0.02	c | Conflicts | Original         | Learnt                           | Progress |
0.02	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.02	c ==============================================================================
0.02	c |         0 |    1113     3715 |     371       0        0     nan |  0.000 % |
0.02	c |       101 |    1113     3715 |     408     101     6279    62.2 |  3.987 % |
0.03	c ==============================================================================
0.03	c SATISFIABLE: No goal function specified.
0.03	s SATISFIABLE
0.03	v -x67 -x163 -x164 x165 -x166 -x167 -x168 -x18 x181 -x182 -x183 -x184 -x185 -x186 -x53 -x157 -x158 -x159 -x160 -x161 x162 -x139
0.03	v -x205 -x206 -x207 -x208 -x209 x210 -x137 -x193 -x194 -x195 x196 -x197 -x198 -x46 -x119 -x130 -x229 x230 -x231 -x232 -x233
0.03	v -x234 -x141 -x217 -x218 -x219 -x220 -x221 -x222 -x14 -x15 -x16 -x17 -x19 -x20 -x21 -x22 x23 -x24 -x25 -x26 -x37 -x31 x7 -x63
0.03	v x74 x93 -x128 x134 -x175 -x176 -x177 -x178 x179 -x180 -x77 x223 -x224 -x225 -x226 -x227 -x228 -x79 -x97 -x187 -x188 -x189 x190
0.03	v -x191 -x192 -x110 x44 -x48 -x52 -x64 -x87 -x117 -x71 -x113 -x66 -x58 -x4 -x33 -x103 -x156 -x49 -x211 -x212 -x213 -x214 x215
0.03	v -x216 -x11 -x140 -x35 -x68 -x69 -x70 -x72 -x73 -x75 -x76 -x78 -x3 -x169 x170 -x171 -x172 -x173 -x174 -x132 -x32 -x152 -x99 -x199
0.03	v -x200 x201 -x202 -x203 -x204 -x57 -x27 -x28 -x29 -x30 x34 -x36 -x38 -x39 x55 -x125 -x84 -x131 -x133 -x135 -x136 -x138 -x142
0.03	v -x143 -x109 -x50 -x65 -x80 -x150 -x105 -x106 -x107 -x108 -x111 -x112 -x114 -x115 x116 -x51 -x129 -x121 -x145 -x41 -x10 -x86
0.03	v -x12 -x81 -x82 -x83 -x85 -x88 -x89 -x90 x91 -x40 -x42 -x43 -x45 -x47 -x154 -x148 -x92 -x126 -x60 -x54 -x56 -x59 -x61 -x62 -x124
0.03	v -x118 -x120 -x122 x123 -x127 -x96 -x102 -x1 -x151 -x155 -x95 -x94 -x98 -x100 -x101 -x104 -x153 -x6 -x13 -x5 x144 -x2 -x146 -x147
0.03	v -x149 -x8 -x9
0.03	c _______________________________________________________________________________
0.03	c 
0.03	c restarts              : 2
0.03	c conflicts             : 147            (5881 /sec)
0.03	c decisions             : 512            (20483 /sec)
0.03	c propagations          : 0              (0 /sec)
0.03	c inspects              : 0              (0 /sec)
0.03	c CPU time              : 0.024996 s
0.03	c _______________________________________________________________________________

Verifier Data (download as text)

OK	0

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node20/watcher-34767-1149227804 -o ROOT/results/node20/solver-34767-1149227804 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node20/34767-1149227804/instance-34767-1149227804.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.74 0.93 0.92 2/64 7129
/proc/meminfo: memFree=1506968/2055920 swapFree=4181488/4192956
[pid=7129] ppid=7127 vsize=1048 CPUtime=0
/proc/7129/stat : 7129 (minisat+) R 7127 7129 7084 0 -1 4194304 107 0 0 0 0 0 0 0 19 0 1 0 188443498 1073152 92 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 134618754 0 0 4096 16386 0 0 0 17 1 0 0
/proc/7129/statm: 262 92 74 215 0 44 0

Child status: 10
Real time (s): 0.031875
CPU time (s): 0.027995
CPU user time (s): 0.024996
CPU system time (s): 0.002999
CPU usage (%): 87.8275
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node20 on Fri Jun  2 05:56:44 UTC 2006


FILE ID= 34767-1149227804

PBS_JOBID= 296159

BENCH NAME= ROOT/tmp/node20/34767-1149227804/instance-34767-1149227804.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node20/34767-1149227804/instance-34767-1149227804.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node20/watcher-34767-1149227804 -o ROOT/results/node20/solver-34767-1149227804 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node20/34767-1149227804/instance-34767-1149227804.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  774e61576b805c95b87ab57992a33004

RANDOM SEED= 808234378


/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.236
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.236
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:       1507184 kB
Buffers:         39712 kB
Cached:         432788 kB
SwapCached:       3296 kB
Active:         170504 kB
Inactive:       310788 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1507184 kB
SwapTotal:     4192956 kB
SwapFree:      4181488 kB
Dirty:             340 kB
Writeback:           0 kB
Mapped:          14748 kB
Slab:            53468 kB
Committed_AS:   228300 kB
PageTables:       1432 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node20 on Fri Jun  2 05:56:44 UTC 2006