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/ftp.netlib.org/lp/data/normalized-mps-v2-13-7-stocfor2.opb
MD5SUM0dc0747c5ead22f2090cd90d5f7e4e43
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of terms in the objective function 21180
Biggest coefficient in the objective function 1811939328000000
Number of bits for the biggest coefficient in the objective function 51
Sum of the numbers in the objective function 384124076253097125
Number of bits of the sum of numbers in the objective function 59
Biggest number in a constraint 1811939328000000
Number of bits of the biggest number in a constraint 51
Biggest sum of numbers in a constraint 384124076253097125
Number of bits of the biggest sum of numbers59
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark15.5966
Number of variables40620
Total number of constraints2157
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints2157
Minimum length of a constraint20
Maximum length of a constraint300

Trace number 5557

Launcher Data

LAUNCH ON wulflinc30 THE 2005-09-20 01:19:40 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=2051 boxname=wulflinc30 idbench=879 idsolver=2 numberseed=0
MD5SUM SOLVER: 1540ae3c74fe6bb56fea7dc39e0baf99  /oldhome/oroussel/solvers/galena
MD5SUM BENCH:  0dc0747c5ead22f2090cd90d5f7e4e43  /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-13-7-stocfor2.opb
REAL COMMAND:  galena /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-13-7-stocfor2.opb
IDLAUNCH: 2051
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.072
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.072
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:        877780 kB
Buffers:         24104 kB
Cached:         103120 kB
SwapCached:        752 kB
Active:          31872 kB
Inactive:        97992 kB
HighTotal:      131008 kB
HighFree:        30968 kB
LowTotal:       903652 kB
LowFree:        846812 kB
SwapTotal:     2097892 kB
SwapFree:      2096620 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5716 kB
Slab:            21444 kB
Committed_AS:    64304 kB
PageTables:        332 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-20 01:19:41 (client local time) WITH STATUS 0 IN 0.06099 SECONDS
stats: 2051 7 0.06099 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/29678/stat): 29678 (galena) R 29677 29678 5245 0 -1 0 18 0 0 0 0 0 0 0 19 0 1 0 1854512773 1015808 2 4294967295 134512640 135412752 3221224560 3221224560 134512896 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/29678/statm): 248 10 241 241 0 7 0
[pid=29678] vsize: 992
open syscall for file /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-13-7-stocfor2.opb
One traced child (pid=29678) 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.067335
CPU time (s): 0.06099
CPU user time (s): 0.057991
CPU system time (s): 0.002999
CPU usage (%): 90.577
Max. virtual memory (cumulated for all children) (Kb): 0



Verifier Data




ERROR: no interpretation found !