Trace number 1883622

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
BoolVar 2009-04-26SAT 0.332949 0.252498

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga13_12_sat_pb.cnf.cr.opb
MD5SUM774e61576b805c95b87ab57992a33004
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
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.007998
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

0.27/0.22	------------------------
0.27/0.22	Encoding : LINEAR, DIRECT, BDD, POLYW, GLOBC
0.27/0.22	Size : 0, 3396, 0, 0, 0
0.27/0.22	Count : 0, 193, 0, 0, 0
0.27/0.22	
0.27/0.22	Command line : minisat tmp.dimacs %var 
0.27/0.23	
0.27/0.23	------------------------
0.27/0.23	This is MiniSat 2.0 beta
0.27/0.23	WARNING: for repeatability, setting FPU to use double precision
0.27/0.23	============================[ Problem Statistics ]=============================
0.27/0.23	|                                                                             |
0.27/0.23	|  Number of variables:  234                                                  |
0.27/0.23	|  Number of clauses:    1242                                                 |
0.27/0.23	|  Parsing time:         0.00         s                                       |
0.27/0.23	============================[ Search Statistics ]==============================
0.27/0.23	| Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.27/0.23	|           |    Vars  Clauses Literals |    Limit  Clauses Lit/Cl |          |
0.27/0.23	===============================================================================
0.27/0.23	|         0 |     222     1230     4824 |      410        0    nan |  0.000 % |
0.27/0.24	|       100 |     222     1230     4824 |      451      100     45 |  0.002 % |
0.27/0.24	===============================================================================
0.27/0.24	restarts              : 2
0.27/0.24	conflicts             : 100            (16669 /sec)
0.27/0.24	decisions             : 301            (0.66 % random) (50175 /sec)
0.27/0.24	propagations          : 2787           (464577 /sec)
0.27/0.24	conflict literals     : 4479           (1.41 % deleted)
0.27/0.24	Memory used           : 1.92 MB
0.27/0.24	CPU time              : 0.005999 s
0.27/0.24	
0.27/0.24	s SATISFIABLE
0.27/0.24	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 -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 -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 -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105 -x106 x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 x118 -x119 -x120 -x121 -x122 -x123 -x124 -x125 -x126 -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 x165 -x166 -x167 -x168 -x169 x170 -x171 -x172 -x173 -x174 -x175 -x176 -x177 -x178 x179 -x180 -x181 -x182 -x183 -x184 -x185 x186 -x187 -x188 -x189 x190 -x191 -x192 x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209 x210 -x211 x212 -x213 -x214 -x215 -x216 -x217 -x218 x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 x227 -x228 -x229 -x230 -x231 -x232 -x233 -x234 

Verifier Data

OK	0

Watcher Data

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1883622-1245194995/watcher-1883622-1245194995 -o /tmp/evaluation-result-1883622-1245194995/solver-1883622-1245194995 -C 1800 -W 2000 -M 1800 java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1883622-1245194995.opb minisat %dimacs %var 

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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 9966
/proc/meminfo: memFree=1867728/2055920 swapFree=4191900/4192956
[pid=9966] ppid=9964 vsize=152 CPUtime=0
/proc/9966/stat : 9966 (java) R 9964 9966 8935 0 -1 0 221 0 0 0 0 0 0 0 18 0 1 0 72232428 155648 26 1992294400 134512640 134550932 4294956032 18446744073709551615 10944811 0 0 4096 0 0 0 0 17 0 0 0
/proc/9966/statm: 38 26 19 9 0 4 0

[startup+0.0935469 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 9966
/proc/meminfo: memFree=1867728/2055920 swapFree=4191900/4192956
[pid=9966] ppid=9964 vsize=1684400 CPUtime=0.1
/proc/9966/stat : 9966 (java) S 9964 9966 8935 0 -1 0 2826 0 1 0 9 1 0 0 18 0 9 0 72232428 1724825600 2321 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/9966/statm: 421100 2321 1215 9 0 416011 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 1684400

[startup+0.102315 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 9966
/proc/meminfo: memFree=1867728/2055920 swapFree=4191900/4192956
[pid=9966] ppid=9964 vsize=1684400 CPUtime=0.11
/proc/9966/stat : 9966 (java) S 9964 9966 8935 0 -1 0 2931 0 1 0 10 1 0 0 18 0 9 0 72232428 1724825600 2421 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/9966/statm: 421100 2421 1226 9 0 416011 0
Current children cumulated CPU time (s) 0.11
Current children cumulated vsize (KiB) 1684400

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

[startup+0.201333 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 9966
/proc/meminfo: memFree=1867728/2055920 swapFree=4191900/4192956
[pid=9966] ppid=9964 vsize=1684552 CPUtime=0.27
/proc/9966/stat : 9966 (java) S 9964 9966 8935 0 -1 0 3369 0 1 0 25 2 0 0 18 0 9 0 72232428 1724981248 2844 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/9966/statm: 421138 2844 1258 9 0 416049 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 1684552

Child status: 0
Real time (s): 0.252498
CPU time (s): 0.332949
CPU user time (s): 0.300954
CPU system time (s): 0.031995
CPU usage (%): 131.862
Max. virtual memory (cumulated for all children) (KiB): 1684552

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.300954
system time used= 0.031995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4090
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 164
involuntary context switches= 62

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data

Begin job on node33 at 2009-06-17 01:29:55
IDJOB=1883622
IDBENCH=1399
IDSOLVER=688
FILE ID=node33/1883622-1245194995
PBS_JOBID= 9368299
Free space on /tmp= 65952 MiB

SOLVER NAME= BoolVar 2009-04-26
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga13_12_sat_pb.cnf.cr.opb
COMMAND LINE= java -Xmx1500m -jar pb2cnfsolver.jar 6 BENCHNAME minisat %dimacs %var
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1883622-1245194995/watcher-1883622-1245194995 -o /tmp/evaluation-result-1883622-1245194995/solver-1883622-1245194995 -C 1800 -W 2000 -M 1800  java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1883622-1245194995.opb minisat %dimacs %var

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 774e61576b805c95b87ab57992a33004
RANDOM SEED=74659406

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

/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.261
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.261
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:       1868344 kB
Buffers:         44408 kB
Cached:          87672 kB
SwapCached:        384 kB
Active:          81024 kB
Inactive:        64532 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1868344 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:             976 kB
Writeback:           0 kB
Mapped:          21808 kB
Slab:            28112 kB
Committed_AS:   139500 kB
PageTables:       1392 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-1883622-1245194995.opb

Free space on /tmp at the end= 65952 MiB
End job on node33 at 2009-06-17 01:29:55