Trace number 47497

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.14OPT421 0.029994 0.035155

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=421-Q=487.opb
MD5SUM1dd301ce14f53b7ddc84b6752affc52d
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark421
Best CPU time to get the best result obtained on this benchmark0.006998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 421
Optimality of the best value was proved YES
Number of variables99
Total number of constraints244
Number of constraints which are clauses243
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 constraint81
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 205027
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 466148
Number of bits of the biggest sum of numbers19
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 245 PB-constraints to clauses...
0.01	c   -- Unit propagations: pp
0.01	c   -- Detecting intervals from adjacent constraints: #################
0.01	c   -- Clauses(.)/Splits(s): ........................................................................................................................................................................................................
0.01	c ---[ 218]---> BDD-cost:    1
0.01	c ---[ 191]---> BDD-cost:    1
0.01	c ---[ 164]---> BDD-cost:    1
0.01	c ---[ 137]---> BDD-cost:    1
0.01	c ---[ 110]---> BDD-cost:    1
0.01	c ---[  83]---> BDD-cost:    1
0.01	c ---[  56]---> BDD-cost:    1
0.01	c ---[  29]---> BDD-cost:    1
0.01	c ---[  26]---> BDD-cost:    1
0.01	c ---[  23]---> BDD-cost:    1
0.01	c ---[  20]---> BDD-cost:    1
0.01	c ---[  17]---> BDD-cost:    1
0.01	c ---[  14]---> BDD-cost:    1
0.01	c ---[  11]---> BDD-cost:    1
0.01	c ---[   8]---> BDD-cost:    1
0.01	c ---[   5]---> BDD-cost:    1
0.01	c ---[   0]---> Sorter-cost: 1155     Base: 2 2 2 2 2 2 2 2 2 2 2 2 2 2
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 |    2890     6880 |     963       0        0     nan |  0.000 % |
0.03	c ==============================================================================
0.03	c Found solution: 421
0.03	o 421
0.03	c ---[   0]---> BDD-cost:    5
0.03	c ==================================[MINISAT+]==================================
0.03	c | Conflicts | Original         | Learnt                           | Progress |
0.03	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.03	c ==============================================================================
0.03	c |        18 |    2841     6767 |     947      16      230    14.4 |  0.000 % |
0.03	c ==============================================================================
0.03	c Optimal solution: 421
0.03	s OPTIMUM FOUND
0.03	v x1 -x2 x3 -x4 -x5 x6 -x7 x8 x9 x19 x10 x20 x11 x21 x12 -x22 -x13 -x23 -x14 x24 x15 x25 x16 x26 x17 x27 x18 -x28 -x29 -x30 -x31 -x32 -x33
0.03	v -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
0.03	v -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
0.03	v x90 x91 x92 x93 -x94 -x95 x96 x97 x98 x99
0.03	c _______________________________________________________________________________
0.03	c 
0.03	c restarts              : 2
0.03	c conflicts             : 28             (966 /sec)
0.03	c decisions             : 60             (2069 /sec)
0.03	c propagations          : 0              (0 /sec)
0.03	c inspects              : 0              (0 /sec)
0.03	c CPU time              : 0.028995 s
0.03	c _______________________________________________________________________________

Verifier Data (download as text)

OK	421

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

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

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node84/watcher-47497-1149845282 -o ROOT/results/node84/solver-47497-1149845282 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/47497-1149845282/instance-47497-1149845282.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.47 0.76 0.83 2/67 10647
/proc/meminfo: memFree=1527080/2055892 swapFree=4085312/4096564
[pid=10647] ppid=10645 vsize=1048 CPUtime=0
/proc/10647/stat : 10647 (minisat+) R 10645 10647 10601 0 -1 4194304 102 0 0 0 0 0 0 0 19 0 1 0 250167469 1073152 88 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 134619209 0 0 4096 16386 0 0 0 17 1 0 0
/proc/10647/statm: 262 88 74 215 0 44 0

Child status: 30
Real time (s): 0.035155
CPU time (s): 0.029994
CPU user time (s): 0.028995
CPU system time (s): 0.000999
CPU usage (%): 85.3192
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node84 on Fri Jun  9 09:28:02 UTC 2006


FILE ID= 47497-1149845282

PBS_JOBID= 382434

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=421-Q=487.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/47497-1149845282/instance-47497-1149845282.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-47497-1149845282 -o ROOT/results/node84/solver-47497-1149845282 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/47497-1149845282/instance-47497-1149845282.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  1dd301ce14f53b7ddc84b6752affc52d

RANDOM SEED= 415628450


/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	: 6006.15
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	: 5999.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1527288 kB
Buffers:         34580 kB
Cached:         428420 kB
SwapCached:       2460 kB
Active:         120860 kB
Inactive:       350820 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1527288 kB
SwapTotal:     4096564 kB
SwapFree:      4085312 kB
Dirty:             328 kB
Writeback:           0 kB
Mapped:          16436 kB
Slab:            43684 kB
Committed_AS:   583680 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Fri Jun  9 09:28:02 UTC 2006