Trace number 2655618

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
wbo 1.4aSAT 0.003999 0.00884191

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga13_11_sat_pb.cnf.cr.opb
MD5SUM7ce2e3bbe25363ec7cf5ebf31ed09feb
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.003999
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables215
Total number of constraints178
Number of constraints which are clauses154
Number of constraints which are cardinality constraints (but not clauses)24
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.00/0.00	c wbo 1.4 beta - 20100517
0.00/0.00	c Parsing opb file format. File HOME/instance-2655618-1276321852.opb.
0.00/0.00	c Instance file HOME/instance-2655618-1276321852.opb
0.00/0.00	c File size is 11491 bytes.
0.00/0.00	c Highest Coefficient sum: 14
0.00/0.00	c ============================[ Problem Statistics ]=============================
0.00/0.00	c |                                                                             |
0.00/0.00	c |  Parsing time:          0.00         s                                      |
0.00/0.00	c |  Number Variables:      215                                                 |
0.00/0.00	c |  Number Clauses:        154                                                 |
0.00/0.00	c |  Number Cardinality:    24                                                  |
0.00/0.00	c |  Number PB Constraints: 0                                                   |
0.00/0.00	c ============================[ Search Statistics ]==============================
0.00/0.00	c | Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.00/0.00	c |           |    Vars     Ctrs     Lits |    Limit  Clauses Lit/Cl |          |
0.00/0.00	c ===============================================================================
0.00/0.00	c |         0 |     215      178     1293 |     5000        0    nan |  0.000 % |
0.00/0.00	c ===============================================================================
0.00/0.00	c #cores: 0
0.00/0.00	c Final Weight: 0
0.00/0.00	s SATISFIABLE
0.00/0.00	v -x13 -x210 -x211 -x212 x213 -x214 -x215 -x71 -x169 -x170 x171 -x172 -x173 x142 -x204 -x205 -x206 -x207 x208 -x209 -x44 -x164 -x165 -x166 -x167 x168 x34 -x180 x181 -x182 -x183 -x184 -x185 -x119 -x149 -x150 -x151 x152 -x153 x101 -x192 -x193 x194 -x195 -x196 -x197 -x117 -x62 -x80 -x77 x61 x186 -x187 -x188 -x189 -x190 -x191 -x29 -x154 x155 -x156 -x157 -x158 -x82 -x159 -x160 -x161 -x162 -x163 x52 -x136 -x83 -x30 -x35 -x33 -x174 -x175 -x176 -x177 -x178 x179 -x49 x2 -x127 -x38 -x106 -x41 -x103 x105 x144 -x145 -x146 -x147 -x148 -x4 -x56 x19 x124 -x25 -x55 -x92 x81 x70 -x57 -x135 -x28 -x12 -x111 -x68 -x27 -x31 -x32 -x36 -x37 -x39 -x132 -x20 -x118 -x16 -x137 -x43 -x98 -x123 -x114 -x89 -x198 -x199 -x200 -x201 -x202 -x203 -x102 -x88 -x8 -x141 -x21 -x54 -x22 -x67 -x79 -x47 -x74 -x78 -x131 -x14 -x72 -x138 -x107 -x99 -x17 -x108 -x3 -x97 -x100 -x112 -x129 -x116 -x23 -x110 -x6 -x109 -x113 -x115 -x48 -x90 -x7 -x18 -x86 -x40 -x10 -x58 -x53 -x59 -x60 -x63 -x64 -x65 -x45 -x15 -x24 -x26 -x139 -x122 -x93 -x94 -x95 -x96 -x104 -x91 -x140 -x120 -x133 -x134 -x143 -x84 -x73 -x130 -x75 -x11 -x42 -x46 -x50 -x51 -x69 -x76 -x128 -x121 -x66 -x9 -x5 -x126 -x125 -x1 -x85 -x87
0.00/0.00	c Total CPU time: 0.003999 s

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-2655618-1276321852/watcher-2655618-1276321852 -o /tmp/evaluation-result-2655618-1276321852/solver-2655618-1276321852 -C 1800 -W 2000 -M 1800 wbo1.4a -file-format=opb -time-limit=1800 HOME/instance-2655618-1276321852.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): 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.86 0.97 0.99 3/106 10484
/proc/meminfo: memFree=1411520/2059040 swapFree=4192956/4192956
[pid=10484] ppid=10482 vsize=0 CPUtime=0
/proc/10484/stat : 10484 (wbo1.4a) Z 10482 10484 10335 0 -1 4202524 276 0 0 0 0 0 0 0 20 0 1 0 5841548 0 0 1992294400 0 0 0 0 0 0 0 4096 3 18446744073709551615 0 0 17 1 0 0 0
/proc/10484/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.00884191
CPU time (s): 0.003999
CPU user time (s): 0.003999
CPU system time (s): 0
CPU usage (%): 45.2278
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.003999
system time used= 0
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 276
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= 1
involuntary context switches= 1

runsolver used 0.000999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node018 at 2010-06-12 07:50:52
IDJOB=2655618
IDBENCH=1398
IDSOLVER=1160
FILE ID=node018/2655618-1276321852
PBS_JOBID= 11173162
Free space on /tmp= 62292 MiB

SOLVER NAME= wbo 1.4a
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga13_11_sat_pb.cnf.cr.opb
COMMAND LINE= wbo1.4a -file-format=opb -time-limit=TIMEOUT BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2655618-1276321852/watcher-2655618-1276321852 -o /tmp/evaluation-result-2655618-1276321852/solver-2655618-1276321852 -C 1800 -W 2000 -M 1800  wbo1.4a -file-format=opb -time-limit=1800 HOME/instance-2655618-1276321852.opb

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

MD5SUM BENCH= 7ce2e3bbe25363ec7cf5ebf31ed09feb
RANDOM SEED=1972644694

node018.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.248
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.49
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.248
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.47
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1411924 kB
Buffers:         98756 kB
Cached:         405420 kB
SwapCached:          0 kB
Active:         197684 kB
Inactive:       365584 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1411924 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            3060 kB
Writeback:           0 kB
AnonPages:       59132 kB
Mapped:          15388 kB
Slab:            62116 kB
PageTables:       3988 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   179548 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62292 MiB
End job on node018 at 2010-06-12 07:50:52