Trace number 47489

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.14OPT79 0.038993 0.0416301

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=79-Q=173.opb
MD5SUM3166c16bf40fe60f901286b7275e91ad
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark79
Best CPU time to get the best result obtained on this benchmark0.009997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 79
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 65536
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 274788
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

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

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: (none)
0.01	c   -- Detecting intervals from adjacent constraints: #
0.01	c   -- Clauses(.)/Splits(s): .......................................................................................................................................................................................................................................
0.01	c ---[   0]---> Sorter-cost: 1121     Base: 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 |    2827     6706 |     942       0        0     nan |  0.000 % |
0.03	c ==============================================================================
0.03	c Found solution: 173
0.03	o 173
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 |        29 |    2523     6015 |     841      24      186     7.8 |  0.000 % |
0.03	c ==============================================================================
0.03	c Found solution: 79
0.03	o 79
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 |        48 |    2328     5566 |     776      37      425    11.5 |  0.000 % |
0.04	c ==============================================================================
0.04	c Optimal solution: 79
0.04	s OPTIMUM FOUND
0.04	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
0.04	v 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
0.04	v -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
0.04	v -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99
0.04	c _______________________________________________________________________________
0.04	c 
0.04	c restarts              : 3
0.04	c conflicts             : 89             (2406 /sec)
0.04	c decisions             : 150            (4055 /sec)
0.04	c propagations          : 0              (0 /sec)
0.04	c inspects              : 0              (0 /sec)
0.04	c CPU time              : 0.036994 s
0.04	c _______________________________________________________________________________

Verifier Data (download as text)

OK	79

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/node68/watcher-47489-1149844976 -o ROOT/results/node68/solver-47489-1149844976 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node68/47489-1149844976/instance-47489-1149844976.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.93 0.90 3/64 31803
/proc/meminfo: memFree=1640440/2055920 swapFree=4182328/4192956
[pid=31803] ppid=31801 vsize=1048 CPUtime=0
/proc/31803/stat : 31803 (minisat+) R 31801 31803 31757 0 -1 4194304 107 0 0 0 0 0 0 0 19 0 1 0 250167121 1073152 92 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 134618678 0 0 4096 16386 0 0 0 17 1 0 0
/proc/31803/statm: 262 92 74 215 0 44 0

Child status: 30
Real time (s): 0.0416301
CPU time (s): 0.038993
CPU user time (s): 0.036994
CPU system time (s): 0.001999
CPU usage (%): 93.6655
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node68 on Fri Jun  9 09:22:56 UTC 2006


FILE ID= 47489-1149844976

PBS_JOBID= 382328

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

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  3166c16bf40fe60f901286b7275e91ad

RANDOM SEED= 202368700


/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.279
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.279
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:       1640648 kB
Buffers:         41000 kB
Cached:         299472 kB
SwapCached:       2384 kB
Active:         112096 kB
Inactive:       237144 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1640648 kB
SwapTotal:     4192956 kB
SwapFree:      4182328 kB
Dirty:             292 kB
Writeback:           0 kB
Mapped:          15560 kB
Slab:            52080 kB
Committed_AS:   528964 kB
PageTables:       1400 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node68 on Fri Jun  9 09:22:56 UTC 2006