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-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-rgn.opb
MD5SUM56e0ae8659c33a6c7b55390a12db116b
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 537600
Optimality of the best value was proved NO
Number of terms in the objective function 1160
Biggest coefficient in the objective function 196608
Number of bits for the biggest coefficient in the objective function 18
Sum of the numbers in the objective function 15892320
Number of bits of the sum of numbers in the objective function 24
Biggest number in a constraint 25600000000
Number of bits of the biggest number in a constraint 35
Biggest sum of numbers in a constraint 232836875088
Number of bits of the biggest sum of numbers38
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark1249.24
Number of variables1260
Total number of constraints204
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)104
Number of constraints which are nor clauses,nor cardinality constraints100
Minimum length of a constraint1
Maximum length of a constraint127

Trace number 3753

Launcher Data

LAUNCH ON wulflinc13 THE 2005-09-19 03:03:24 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=1711 boxname=wulflinc13 idbench=539 idsolver=2 numberseed=0
MD5SUM SOLVER: 1540ae3c74fe6bb56fea7dc39e0baf99  /oldhome/oroussel/solvers/galena
MD5SUM BENCH:  56e0ae8659c33a6c7b55390a12db116b  /oldhome/oroussel/tmp/wulflinc13/normalized-mps-v2-20-10-rgn.opb
REAL COMMAND:  galena /oldhome/oroussel/tmp/wulflinc13/normalized-mps-v2-20-10-rgn.opb
IDLAUNCH: 1711
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.242
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	: 2
cpu MHz		: 451.242
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:        864892 kB
Buffers:         35092 kB
Cached:         108156 kB
SwapCached:        708 kB
Active:          67284 kB
Inactive:        78592 kB
HighTotal:      131008 kB
HighFree:        49840 kB
LowTotal:       903652 kB
LowFree:        815052 kB
SwapTotal:     2097136 kB
SwapFree:      2095936 kB
Dirty:              40 kB
Writeback:           0 kB
Mapped:           5740 kB
Slab:            18272 kB
Committed_AS:    64128 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-19 03:03:24 (client local time) WITH STATUS 0 IN 0.079987 SECONDS
stats: 1711 7 0.079987 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/9846/stat): 9846 (galena) R 9845 9846 1333 0 -1 0 18 0 0 0 0 0 0 0 22 0 1 0 1788298555 1015808 2 4294967295 134512640 135412752 3221224560 3221224560 134512896 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/9846/statm): 248 2 241 241 0 7 0
[pid=9846] vsize: 992
open syscall for file /oldhome/oroussel/tmp/wulflinc13/normalized-mps-v2-20-10-rgn.opb
One traced child (pid=9846) 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.083515
CPU time (s): 0.079987
CPU user time (s): 0.075988
CPU system time (s): 0.003999
CPU usage (%): 95.7756
Max. virtual memory (cumulated for all children) (Kb): 0



Verifier Data




ERROR: no interpretation found !