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/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 YES
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 benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.003998
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 1985

Launcher Data

LAUNCH ON wulflinc21 THE 2005-09-18 18:00:19 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=1442 boxname=wulflinc21 idbench=270 idsolver=2 numberseed=0
MD5SUM SOLVER: 1540ae3c74fe6bb56fea7dc39e0baf99  /oldhome/oroussel/solvers/galena
MD5SUM BENCH:  276f089932f6c452fdc3e3b93f688af7  /oldhome/oroussel/tmp/wulflinc21/normalized-g2x2.opb
REAL COMMAND:  galena /oldhome/oroussel/tmp/wulflinc21/normalized-g2x2.opb
IDLAUNCH: 1442
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.161
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.161
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:        899372 kB
Buffers:         34804 kB
Cached:          72884 kB
SwapCached:        908 kB
Active:          78768 kB
Inactive:        31548 kB
HighTotal:      131008 kB
HighFree:        62048 kB
LowTotal:       903652 kB
LowFree:        837324 kB
SwapTotal:     2097892 kB
SwapFree:      2096472 kB
Dirty:               4 kB
Writeback:           0 kB
Mapped:           5804 kB
Slab:            19284 kB
Committed_AS:    64332 kB
PageTables:        340 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-18 18:00:20 (client local time) WITH STATUS 30 IN 0.003998 SECONDS
stats: 1442 0 0.003998 30

Solver Data

c Decisions:	6
c Implications:	15
c RUNTIME:	0.000999s
v -x1 -x2 x3 x4 
s OPTIMUM FOUND

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/28165/stat): 28165 (galena) R 28164 28165 20602 0 -1 0 18 0 0 0 0 0 0 0 23 0 1 0 1720517552 1015808 2 4294967295 134512640 135412752 3221224576 3221224576 134512896 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/28165/statm): 248 2 241 241 0 7 0
[pid=28165] vsize: 992
open syscall for file /oldhome/oroussel/tmp/wulflinc21/normalized-g2x2.opb
One traced child (pid=28165) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 0.010231
CPU time (s): 0.003998
CPU user time (s): 0.000999
CPU system time (s): 0.002999
CPU usage (%): 39.0773
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	2