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/mps-v2-20-10/MIPLIB/miplib3/normalized-mps-v2-20-10-bell5.opb
MD5SUM69f4cc43076dd783d9debfd1c0708aef
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2147483647
Optimality of the best value was proved NO
Number of terms in the objective function 1268
Biggest coefficient in the objective function 50331648000000000
Number of bits for the biggest coefficient in the objective function 56
Sum of the numbers in the objective function 888722133694353611
Number of bits of the sum of numbers in the objective function 60
Biggest number in a constraint 50331648000000000
Number of bits of the biggest number in a constraint 56
Biggest sum of numbers in a constraint 888722133694353611
Number of bits of the biggest sum of numbers60
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark1234.3
Number of variables1704
Total number of constraints149
Number of constraints which are clauses15
Number of constraints which are cardinality constraints (but not clauses)30
Number of constraints which are nor clauses,nor cardinality constraints104
Minimum length of a constraint1
Maximum length of a constraint135

Trace number 16421 

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc29 THE 2005-04-21 07:30:25 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=13234 boxname=wulflinc29 idbench=1018 idsolver=13 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  69f4cc43076dd783d9debfd1c0708aef  /oldhome/oroussel/tmp/wulflinc29/normalized-mps-v2-20-10-bell5.opb
REAL COMMAND:  minisat+ -w /oldhome/oroussel/tmp/wulflinc29/normalized-mps-v2-20-10-bell5.opb /oldhome/oroussel/tmp/wulflinc29/normalized-mps-v2-20-10-bell5.opb
IDLAUNCH: 13234
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.020
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.020
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:        698948 kB
Buffers:         25556 kB
Cached:         281884 kB
SwapCached:        464 kB
Active:          56824 kB
Inactive:       252804 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        698696 kB
SwapTotal:     2097892 kB
SwapFree:      2096700 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5296 kB
Slab:            20436 kB
Committed_AS:    63604 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-04-21 07:30:25 (client local time) WITH STATUS 1 IN 0.010998 SECONDS
stats: 13234 7 0.010998 1
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c Parsing PB file...
PARSE ERROR! [line 108] Integer overflow. Big numbers not supported yet.
#### 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.57 0.83 0.87 2/54 26213
Raw data (stat): 26213 (runsolver) R 26212 27222 27221 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 543289722 1052672 99 4294967295 134512640 135381576 3221224448 3221219692 135158418 0 2147483391 7 90112 0 0 0 17 1 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 1028
[startup+0.019786 s]
Raw data (loadavg): 0.57 0.83 0.87 1/53 26213
Raw data (stat): 26213 (runsolver) R 26212 27222 27221 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 543289722 1052672 99 4294967295 134512640 135381576 3221224448 3221219692 135158418 0 2147483391 7 90112 0 0 0 17 1 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 0

Child status: 1
Real time (s): 0.019547
CPU time (s): 0.010998
CPU user time (s): 0.004999
CPU system time (s): 0.005999
CPU usage (%): 56.2644
Max. virtual memory (Kb): 1028
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
ERROR: no interpretation found !
#### END VERIFIER DATA ####