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).
  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

Namenormalized-opb/submitted/sorensson/garden/normalized-g4x4.opb
MD5SUM86076c854d7a3787e909491096d2ae43
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 4
Optimality of the best value was proved NO
Number of terms in the objective function 16
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 16
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 16
Number of bits of the biggest sum of numbers5
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.008998
Number of variables16
Total number of constraints16
Number of constraints which are clauses16
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint3
Maximum length of a constraint5

Trace number 25035

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc31 THE 2005-05-16 04:36:42 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=4921 boxname=wulflinc31 idbench=379 idsolver=7 numberseed=0
MD5SUM SOLVER: d9a5994a76be78982e492b397ce73911  /oldhome/oroussel/solvers/Pueblo
MD5SUM BENCH:  86076c854d7a3787e909491096d2ae43  /oldhome/oroussel/tmp/wulflinc31/normalized-g4x4.opb
REAL COMMAND:  Pueblo /oldhome/oroussel/tmp/wulflinc31/normalized-g4x4.opb
IDLAUNCH: 4921
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.153
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	: 888.83

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.153
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	: 901.12

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        802500 kB
Buffers:         48496 kB
Cached:         161528 kB
SwapCached:       1932 kB
Active:         169448 kB
Inactive:        43752 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        802248 kB
SwapTotal:     2097892 kB
SwapFree:      2095228 kB
Dirty:               4 kB
Writeback:           0 kB
Mapped:           5368 kB
Slab:            13368 kB
Committed_AS:    63848 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-05-16 04:36:43 (client local time) WITH STATUS 30 IN 0.028994 SECONDS
stats: 4921 0 0.028994 30
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c Pueblo version 1.2 (Sept 2004)
c Developed @ University of Michigan, Ann Arbor, MI
c  by Hossein Sheini
c Solving: /oldhome/oroussel/tmp/wulflinc31/normalized-g4x4.opb
c #variables read: 16 - #constraints read: 17
c optimum objective found = 4
s OPTIMUM FOUND
v -x1 -x2 x3 -x4 x5 -x6 -x7 -x8 -x9 -x10 -x11 x12 -x13 x14 -x15 -x16 
#### END SOLVER DATA ####
#### BEGIN WATCHER DATA ####
Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing VSIZE limit: 943718400 bytes
Raw data (loadavg): 0.71 0.89 0.95 2/55 8944
Raw data (stat): 8944 (runsolver) R 8943 7876 7672 0 -1 64 5 0 0 0 0 0 0 0 19 0 1 0 758261208 1056768 100 4294967295 134512640 135381576 3221221696 3221216920 135158418 0 2147483391 1 90112 0 0 0 17 0 0 0
Raw data (statm): 258 100 215 215 0 43 0
vsize: 1032
[startup+0.054599 s]
Raw data (loadavg): 0.71 0.89 0.95 1/54 8944
Raw data (stat): 8944 (runsolver) R 8943 7876 7672 0 -1 64 5 0 0 0 0 0 0 0 19 0 1 0 758261208 1056768 100 4294967295 134512640 135381576 3221221696 3221216920 135158418 0 2147483391 1 90112 0 0 0 17 0 0 0
Raw data (statm): 258 100 215 215 0 43 0
vsize: 0

Child status: 30
Real time (s): 0.054351
CPU time (s): 0.028994
CPU user time (s): 0.007998
CPU system time (s): 0.020996
CPU usage (%): 53.3458
Max. virtual memory (Kb): 1032
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	4
#### END VERIFIER DATA ####