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 in four parts:
  1. 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 provide some useful information on the computer.
  2. 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 !
  3. 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 1200 seconds. 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 1230 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (900Mb).
    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.
  4. 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.

General information on the benchmark

Namesubmitted/een/normalized-p0033.opb
MD5SUMaadd007771d1c99eca3f8fae045a6c02
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3089
Optimality of the best value was proved YES
Number of terms in the objective function 33
Biggest coefficient in the objective function 517
Number of bits for the biggest coefficient in the objective function 10
Sum of the numbers in the objective function 7276
Number of bits of the sum of numbers in the objective function 13
Biggest number in a constraint 1656
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 7276
Number of bits of the biggest sum of numbers13
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.070989
Number of variables33
Total number of constraints15
Number of constraints which are clauses1
Number of constraints which are cardinality constraints (but not clauses)3
Number of constraints which are nor clauses,nor cardinality constraints11
Minimum length of a constraint2
Maximum length of a constraint19

Trace number 2386

Launcher Data

LAUNCH ON wulflinc22 THE 2005-09-18 19:46:29 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=3791 boxname=wulflinc22 idbench=275 idsolver=4 numberseed=0
MD5SUM SOLVER: 21c3ffd7205c96d5f0784fd273b92938  /oldhome/oroussel/solvers/PBS4
MD5SUM BENCH:  aadd007771d1c99eca3f8fae045a6c02  /oldhome/oroussel/tmp/wulflinc22/normalized-p0033.opb
REAL COMMAND:  PBS4 /oldhome/oroussel/tmp/wulflinc22/normalized-p0033.opb
IDLAUNCH: 3791
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.031
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 890.88

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.031
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        912532 kB
Buffers:         34708 kB
Cached:          60364 kB
SwapCached:        536 kB
Active:          67072 kB
Inactive:        30552 kB
HighTotal:      131008 kB
HighFree:        68656 kB
LowTotal:       903652 kB
LowFree:        843876 kB
SwapTotal:     2097892 kB
SwapFree:      2096832 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5864 kB
Slab:            18944 kB
Committed_AS:    64168 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-18 19:46:29 (client local time) WITH STATUS 30 IN 0.094984 SECONDS
stats: 3791 0 0.094984 30

Solver Data

c PBS v4 by Bashar Al-Rawi & Fadi Aloul
c Solving /oldhome/oroussel/tmp/wulflinc22/normalized-p0033.opb ......
c The optimum solution is:3089
s OPTIMUM FOUND
v x0 -x1 -x10 -x11 -x12 x13 -x14 -x15 -x16 x17 -x18 -x19 -x2 x20 x21 x22 x23 -x24 x25 x26 x27 x28 x29 -x3 -x30 -x31 -x32 -x4 -x5 x6 x7 -x8 x9 
c Done, CPU Time=0.087986

Watcher Data

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGTERM then SIGKILL): 921600 Kb
Enforcing VSIZE limit: 994918400 bytes
Current StackSize limit: 67108864 bytes
Raw data (/proc/630/stat): 630 (PBS4) R 629 630 21452 0 -1 0 18 0 0 0 0 0 0 0 23 0 1 0 1843885325 978944 2 4294967295 134512640 135450776 3221224576 3221224576 134512960 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/630/statm): 239 2 232 232 0 7 0
[pid=630] vsize: 956
open syscall for file /dev/null
open syscall for file /oldhome/oroussel/tmp/wulflinc22/normalized-p0033.opb
open syscall for file /oldhome/oroussel/tmp/wulflinc22/normalized-p0033.opb
One traced child (pid=630) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 0.119506
CPU time (s): 0.094984
CPU user time (s): 0.073988
CPU system time (s): 0.020996
CPU usage (%): 79.4805
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	3089