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-g2x2.opb
MD5SUM276f089932f6c452fdc3e3b93f688af7
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved NO
Number of terms in the objective function 4
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 4
Number of bits of the sum of numbers in the objective function 3
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 4
Number of bits of the biggest sum of numbers3
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.004998
Number of variables4
Total number of constraints4
Number of constraints which are clauses4
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 constraint3

Trace number 7917 

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc10 THE 2005-04-17 17:35:20 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=4907 boxname=wulflinc10 idbench=378 idsolver=6 numberseed=0
MD5SUM SOLVER: 2225cba0d9b2c30e235f6cafc823d7ac  /oldhome/oroussel/solvers/PBS4
MD5SUM BENCH:  276f089932f6c452fdc3e3b93f688af7  /oldhome/oroussel/tmp/wulflinc10/normalized-g2x2.opb
REAL COMMAND:  PBS4 /oldhome/oroussel/tmp/wulflinc10/normalized-g2x2.opb
IDLAUNCH: 4907
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 450.999
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	: 2
cpu MHz		: 450.999
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:        808204 kB
Buffers:         36692 kB
Cached:         168776 kB
SwapCached:        164 kB
Active:          80936 kB
Inactive:       127572 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        807952 kB
SwapTotal:     2097136 kB
SwapFree:      2096972 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6928 kB
Slab:            12296 kB
Committed_AS:    63472 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-04-17 17:35:20 (client local time) WITH STATUS 30 IN 0.006998 SECONDS
stats: 4907 0 0.006998 30
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c PBS v4 by Bashar Al-Rawi & Fadi Aloul
c Solving /oldhome/oroussel/tmp/wulflinc10/normalized-g2x2.opb ......
c The optimum solution is:2
s OPTIMUM FOUND
v -x1 -x2 x3 x4 
c Done, CPU Time=0
#### 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.92 0.98 0.95 2/54 18763
Raw data (stat): 18763 (runsolver) R 18762 25347 25346 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 454144132 1052672 99 4294967295 134512640 135381576 3221224544 3221219792 135158418 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 1028
[startup+0.009316 s]
Raw data (loadavg): 0.92 0.98 0.95 1/53 18763
Raw data (stat): 18763 (runsolver) R 18762 25347 25346 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 454144132 1052672 99 4294967295 134512640 135381576 3221224544 3221219792 135158418 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 0

Child status: 30
Real time (s): 0.009098
CPU time (s): 0.006998
CPU user time (s): 0
CPU system time (s): 0.006998
CPU usage (%): 76.918
Max. virtual memory (Kb): 1028
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	2
#### END VERIFIER DATA ####