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

Namemps-v2-13-7/MIPLIB/miplib3/normalized-mps-v2-13-7-gen.opb
MD5SUM650632b92fbb7592f9a040d6375b78e9
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of terms in the objective function 8814
Biggest coefficient in the objective function 3375324200960
Number of bits for the biggest coefficient in the objective function 42
Sum of the numbers in the objective function 2061624536571104
Number of bits of the sum of numbers in the objective function 51
Biggest number in a constraint 3375324200960
Number of bits of the biggest number in a constraint 42
Biggest sum of numbers in a constraint 2061624536571104
Number of bits of the biggest sum of numbers51
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Number of variables12846
Total number of constraints1074
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)144
Number of constraints which are nor clauses,nor cardinality constraints930
Minimum length of a constraint1
Maximum length of a constraint192

Trace number 5690

Launcher Data

LAUNCH ON wulflinc7 THE 2005-09-20 01:22:12 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=2185 boxname=wulflinc7 idbench=1013 idsolver=2 numberseed=0
MD5SUM SOLVER: 1540ae3c74fe6bb56fea7dc39e0baf99  /oldhome/oroussel/solvers/galena
MD5SUM BENCH:  650632b92fbb7592f9a040d6375b78e9  /oldhome/oroussel/tmp/wulflinc7/normalized-mps-v2-13-7-gen.opb
REAL COMMAND:  galena /oldhome/oroussel/tmp/wulflinc7/normalized-mps-v2-13-7-gen.opb
IDLAUNCH: 2185
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.050
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		: 451.050
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:        918688 kB
Buffers:          3616 kB
Cached:          87024 kB
SwapCached:        752 kB
Active:          30172 kB
Inactive:        63124 kB
HighTotal:      131008 kB
HighFree:        39788 kB
LowTotal:       903652 kB
LowFree:        878900 kB
SwapTotal:     2097136 kB
SwapFree:      2095876 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5664 kB
Slab:            16864 kB
Committed_AS:    64132 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-20 01:22:12 (client local time) WITH STATUS 0 IN 0.031994 SECONDS
stats: 2185 7 0.031994 0

Solver Data



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/7621/stat): 7621 (galena) R 7620 7621 15400 0 -1 0 18 0 0 0 0 0 0 0 19 0 1 0 1796336942 1015808 2 4294967295 134512640 135412752 3221224560 3221224560 134512896 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/7621/statm): 248 2 241 241 0 7 0
[pid=7621] vsize: 992
open syscall for file /oldhome/oroussel/tmp/wulflinc7/normalized-mps-v2-13-7-gen.opb
One traced child (pid=7621) ended because it received signal 6 (SIGABRT)
All traced children have exited ! Game is over.

Child ended because it received signal 6 (SIGABRT)
Real time (s): 0.048951
CPU time (s): 0.031994
CPU user time (s): 0.029995
CPU system time (s): 0.001999
CPU usage (%): 65.3592
Max. virtual memory (cumulated for all children) (Kb): 0



Verifier Data




ERROR: no interpretation found !