Trace number 34793

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.018997 0.024014

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga11_9_sat_pb.cnf.cr.opb
MD5SUM5b191b5d2c07d480e8b2d3e38d895026
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.001999
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables149
Total number of constraints128
Number of constraints which are clauses108
Number of constraints which are cardinality constraints (but not clauses)20
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint5
Maximum length of a constraint11
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 12
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.01	c Converting 128 PB-constraints to clauses...
0.01	c   -- Unit propagations: (none)
0.01	c   -- Detecting intervals from adjacent constraints: (none)
0.01	c   -- Clauses(.)/Splits(s): ............................................................................................................
0.01	c ---[  19]---> BDD-cost:   15
0.01	c ---[  18]---> BDD-cost:   15
0.01	c ---[  17]---> BDD-cost:   15
0.01	c ---[  16]---> BDD-cost:   15
0.01	c ---[  15]---> BDD-cost:   15
0.01	c ---[  14]---> BDD-cost:   15
0.01	c ---[  13]---> BDD-cost:   15
0.01	c ---[  12]---> BDD-cost:   15
0.01	c ---[  11]---> BDD-cost:   15
0.01	c ---[  10]---> BDD-cost:   15
0.01	c ---[   9]---> BDD-cost:   15
0.01	c ---[   8]---> BDD-cost:    7
0.01	c ---[   7]---> BDD-cost:    7
0.01	c ---[   6]---> BDD-cost:    7
0.01	c ---[   5]---> BDD-cost:    7
0.01	c ---[   4]---> BDD-cost:    9
0.01	c ---[   3]---> BDD-cost:    9
0.01	c ---[   2]---> BDD-cost:    9
0.01	c ---[   1]---> BDD-cost:    9
0.01	c ---[   0]---> BDD-cost:    9
0.01	c ==================================[MINISAT+]==================================
0.01	c | Conflicts | Original         | Learnt                           | Progress |
0.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.01	c ==============================================================================
0.01	c |         0 |     673     2125 |     224       0        0     nan |  0.000 % |
0.01	c |       103 |     673     2125 |     246     103     4301    41.8 |  5.169 % |
0.02	c ==============================================================================
0.02	c SATISFIABLE: No goal function specified.
0.02	s SATISFIABLE
0.02	v -x30 x130 -x131 -x132 -x133 -x134 -x42 -x135 x136 -x137 -x138 -x139 -x26 -x112 x113 -x114 -x115 -x28 -x120 -x121 x122 -x123
0.02	v -x124 -x5 x116 -x117 -x118 -x119 -x1 -x100 -x101 x102 -x103 -x12 -x58 -x108 -x109 -x110 -x111 -x4 -x34 x35 -x36 -x37 -x38 -x39
0.02	v -x40 -x41 -x43 -x44 -x73 -x125 -x126 -x127 x128 -x129 -x91 x63 -x84 -x7 -x47 -x24 -x104 -x105 -x106 x107 x82 -x64 x92 -x14 -x56
0.02	v -x18 -x99 -x145 -x146 -x147 -x148 -x149 -x97 -x25 -x49 -x94 -x67 -x68 -x69 -x70 -x71 -x72 -x74 x75 -x76 -x77 -x9 -x33 -x57 -x59
0.02	v -x60 -x61 -x62 -x65 -x66 -x80 -x20 -x54 -x140 -x141 -x142 -x143 x144 -x15 -x89 -x90 -x93 -x95 -x96 -x98 -x31 -x51 -x79 -x53 -x2
0.02	v -x3 x6 -x8 -x10 -x11 -x22 x29 -x46 -x88 -x27 -x87 -x13 -x52 -x23 -x32 -x16 -x17 -x86 -x55 -x48 -x85 -x78 -x83 -x19 x21 x45 -x50
0.02	v -x81
0.02	c _______________________________________________________________________________
0.02	c 
0.02	c restarts              : 2
0.02	c conflicts             : 221            (11633 /sec)
0.02	c decisions             : 499            (26267 /sec)
0.02	c propagations          : 0              (0 /sec)
0.02	c inspects              : 0              (0 /sec)
0.02	c CPU time              : 0.018997 s
0.02	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/node16/watcher-34793-1149231722 -o ROOT/results/node16/solver-34793-1149231722 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node16/34793-1149231722/instance-34793-1149231722.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.84 0.94 0.96 2/64 10367
/proc/meminfo: memFree=1426752/2055920 swapFree=4181468/4192956
[pid=10367] ppid=10365 vsize=1048 CPUtime=0
/proc/10367/stat : 10367 (minisat+) R 10365 10367 10322 0 -1 4194304 106 0 0 0 0 0 0 0 19 0 1 0 188835040 1073152 91 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135007481 0 0 4096 16386 0 0 0 17 1 0 0
/proc/10367/statm: 262 91 74 215 0 44 0

Child status: 10
Real time (s): 0.024014
CPU time (s): 0.018997
CPU user time (s): 0.018997
CPU system time (s): 0
CPU usage (%): 79.1079
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node16 on Fri Jun  2 07:02:02 UTC 2006


FILE ID= 34793-1149231722

PBS_JOBID= 296497

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

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  5b191b5d2c07d480e8b2d3e38d895026

RANDOM SEED= 976857820


/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.231
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.231
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:       1426960 kB
Buffers:         38728 kB
Cached:         518504 kB
SwapCached:       3292 kB
Active:         205020 kB
Inactive:       360976 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1426960 kB
SwapTotal:     4192956 kB
SwapFree:      4181468 kB
Dirty:             296 kB
Writeback:           0 kB
Mapped:          14720 kB
Slab:            49080 kB
Committed_AS:   211264 kB
PageTables:       1468 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node16 on Fri Jun  2 07:02:02 UTC 2006