Trace number 48631

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.2 HeuristicsOPT283 9.75452 8.67397

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=283-Q=293.opb
MD5SUMa3c66b6c441287c299c77d1532171943
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark283
Best CPU time to get the best result obtained on this benchmark0.015997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 283
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 82919
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 344040
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.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-22.EL.rootsmp
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.21	c Cutting planes based inference
0.21	c --- Begin Solver configuration ---
0.21	c org.sat4j.minisat.uip.FirstUIP@1df073d
0.21	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1546e25
0.21	c org.sat4j.minisat.learning.MiniSATLearning@b66cc
0.21	c conflictBoundIncFactor=1.5 learntBoundIncFactor=1.1 initLearntBoundConstraintFactor=10000.0 initConflictBound=100 
0.21	c VSIDS like heuristics from MiniSAT using a heap
0.21	c No reason simplification
0.21	c --- End Solver configuration ---
0.21	c solving ROOT/tmp/node74/48631-1149843400/instance-48631-1149843400.opb
0.21	c reading problem ... 
0.32	c ... done. Time 0.106 ms.
0.32	c #vars     99
0.32	c #constraints  245
7.65	c SATISFIABLE
7.65	c OPTIMIZING...
7.65	c Got one! Ellapsed CPU time (in seconds):7.438
7.65	o 293
8.29	c Got one! Ellapsed CPU time (in seconds):8.073
8.29	o 283
8.59	c starts		: 8
8.59	c conflicts		: 1493
8.59	c decisions		: 1741
8.59	c propagations		: 28705
8.59	c inspects		: 2609509
8.59	c learnt literals	: 0
8.59	c learnt binary clauses	: 0
8.59	c learnt ternary clauses	: 0
8.59	c learnt clauses	: 1492
8.59	c root simplifications	: 0
8.59	c removed literals (reason simplification)	: 0
8.59	c reason swapping (by a shorter reason)	: 0
8.59	c Calls to reduceDB	: 0
8.59	c speed (decisions/second)	: 5652.597402597403
8.59	c non guided choices	0
8.59	s OPTIMUM FOUND
8.59	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 -x31 -x32
8.59	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
8.59	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
8.59	v -x87 -x88 -x89 -x90 x91 -x92 x93 -x94 -x95 x96 -x97 -x98 x99
8.60	c objective function=283
8.60	c Total wall clock time (ms): 8.383

Verifier Data (download as text)

OK	283

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/node74/watcher-48631-1149843400 -o ROOT/results/node74/solver-48631-1149843400 -C 1800 -M 1800 -S 64 java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node74/48631-1149843400/instance-48631-1149843400.opb 391159417 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.73 0.90 0.89 3/64 22318
/proc/meminfo: memFree=1642696/2055920 swapFree=4182256/4192956
[pid=22318] ppid=22316 vsize=168 CPUtime=0
/proc/22318/stat : 22318 (java) R 22316 22318 22272 0 -1 0 39 0 0 0 0 0 0 0 19 0 1 0 250004314 172032 23 18446744073709551615 134512640 134570276 4294956608 18446744073709551615 7393579 0 0 4096 0 0 0 0 17 1 0 0
/proc/22318/statm: 42 23 18 14 0 2 0

Child status: 30
Real time (s): 8.67397
CPU time (s): 9.75452
CPU user time (s): 9.48956
CPU system time (s): 0.264959
CPU usage (%): 112.457
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node74 on Fri Jun  9 08:56:40 UTC 2006


FILE ID= 48631-1149843400

PBS_JOBID= 382205

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=283-Q=293.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node74/48631-1149843400/instance-48631-1149843400.opb 391159417
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node74/watcher-48631-1149843400 -o ROOT/results/node74/solver-48631-1149843400 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node74/48631-1149843400/instance-48631-1149843400.opb 391159417

MD5SUM SOLVER= 3cef94aa015dc0dd234d31843a257d70
MD5SUM BENCH=  a3c66b6c441287c299c77d1532171943

RANDOM SEED= 391159417


/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.274
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.274
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:       1642904 kB
Buffers:         40320 kB
Cached:         296748 kB
SwapCached:       2456 kB
Active:          96196 kB
Inactive:       249624 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1642904 kB
SwapTotal:     4192956 kB
SwapFree:      4182256 kB
Dirty:             300 kB
Writeback:           0 kB
Mapped:          15840 kB
Slab:            53228 kB
Committed_AS:   475032 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node74 on Fri Jun  9 08:56:49 UTC 2006