Trace number 44270

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
SAT4JPSEUDO 2006.2OPT20 2.52961 1.57683

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/ttp/normalized-circ4_3.opb
MD5SUM6b7a318661ea9d7a03f30f3e64874f46
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark20
Best CPU time to get the best result obtained on this benchmark0.165974
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 20
Optimality of the best value was proved YES
Number of variables144
Total number of constraints704
Number of constraints which are clauses464
Number of constraints which are cardinality constraints (but not clauses)96
Number of constraints which are nor clauses,nor cardinality constraints144
Minimum length of a constraint2
Maximum length of a constraint12
Number of terms in the objective function 48
Biggest coefficient in the objective function 2
Number of bits for the biggest coefficient in the objective function 2
Sum of the numbers in the objective function 64
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 8
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 64
Number of bits of the biggest sum of numbers7
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.14	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.14	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.15	c no version file found!!!
0.15	c sun.arch.data.model	32
0.15	c java.version	1.5.0_06
0.15	c os.name	Linux
0.15	c os.version	2.6.9-34.ELsmp
0.15	c os.arch	i386
0.15	c Free memory 1548419056
0.15	c Max memory 1551040512
0.15	c Total memory 1551040512
0.15	c Number of processors 2
0.20	c Cutting planes based inference
0.20	c --- Begin Solver configuration ---
0.20	c org.sat4j.minisat.uip.FirstUIP@1037c71
0.20	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1df073d
0.20	c org.sat4j.minisat.learning.MiniSATLearning@1546e25
0.20	c conflictBoundIncFactor=1.5 learntBoundIncFactor=1.1 initLearntBoundConstraintFactor=10000.0 initConflictBound=100 
0.20	c VSIDS like heuristics from MiniSAT using a heap
0.20	c No reason simplification
0.20	c --- End Solver configuration ---
0.20	c solving ROOT/tmp/node83/44270-1149400458/instance-44270-1149400458.opb
0.20	c reading problem ... 
0.44	c ... done. Time 0.237 ms.
0.44	c #vars     144
0.44	c #constraints  764
0.46	c SATISFIABLE
0.46	c OPTIMIZING...
0.46	c Got one! Ellapsed CPU time (in seconds):0.263
0.46	o 26
0.70	c Got one! Ellapsed CPU time (in seconds):0.502
0.70	o 22
0.99	c Got one! Ellapsed CPU time (in seconds):0.786
0.99	o 20
1.54	c starts		: 7
1.54	c conflicts		: 629
1.54	c decisions		: 1325
1.54	c propagations		: 20758
1.54	c inspects		: 259389
1.54	c learnt literals	: 0
1.54	c learnt binary clauses	: 0
1.54	c learnt ternary clauses	: 0
1.54	c learnt clauses	: 628
1.54	c root simplifications	: 0
1.54	c removed literals (reason simplification)	: 0
1.54	c reason swapping (by a shorter reason)	: 0
1.54	c Calls to reduceDB	: 0
1.54	c speed (decisions/second)	: 2378.815080789946
1.54	c non guided choices	166
1.54	s OPTIMUM FOUND
1.54	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
1.54	v -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
1.54	v -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
1.54	v -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
1.54	v -x110 x111 x112 x113 -x114 -x115 x116 -x117 -x118 x119 -x120 x121 -x122 -x123 -x124 x125 -x126 -x127 -x128 x129 x130 -x131
1.54	v -x132 x133 -x134 -x135 -x136 x137 -x138 -x139 -x140 x141 x142 -x143 -x144
1.54	c objective function=20
1.54	c Total wall clock time (ms): 1.345

Verifier Data (download as text)

OK	20

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/node83/watcher-44270-1149400458 -o ROOT/results/node83/solver-44270-1149400458 -C 1800 -M 1800 -S 64 java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node83/44270-1149400458/instance-44270-1149400458.opb 844512075 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.84 0.94 0.97 2/67 16475
/proc/meminfo: memFree=1543648/2055888 swapFree=4085408/4096564
[pid=16475] ppid=16473 vsize=1788 CPUtime=0
/proc/16475/stat : 16475 (java) D 16473 16475 16429 0 -1 0 179 0 0 0 0 0 0 0 18 0 1 0 205685133 1830912 147 18446744073709551615 134512640 134570276 4294956624 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099917094 0 0 17 1 0 0
/proc/16475/statm: 447 147 112 14 0 91 0

Child status: 30
Real time (s): 1.57683
CPU time (s): 2.52961
CPU user time (s): 2.38564
CPU system time (s): 0.143978
CPU usage (%): 160.424
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node83 on Sun Jun  4 05:54:18 UTC 2006


FILE ID= 44270-1149400458

PBS_JOBID= 313983

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/ttp/normalized-circ4_3.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node83/44270-1149400458/instance-44270-1149400458.opb 844512075
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node83/watcher-44270-1149400458 -o ROOT/results/node83/solver-44270-1149400458 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node83/44270-1149400458/instance-44270-1149400458.opb 844512075

MD5SUM SOLVER= e9637a7554f3ecdf74c1815f89d00213
MD5SUM BENCH=  6b7a318661ea9d7a03f30f3e64874f46

RANDOM SEED= 844512075


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1543792 kB
Buffers:         30264 kB
Cached:         410868 kB
SwapCached:       2364 kB
Active:         253708 kB
Inactive:       196152 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1543792 kB
SwapTotal:     4096564 kB
SwapFree:      4085408 kB
Dirty:             180 kB
Writeback:           0 kB
Mapped:          16880 kB
Slab:            48888 kB
Committed_AS:   447680 kB
PageTables:       1284 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node83 on Sun Jun  4 05:54:19 UTC 2006