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/ftp.netlib.org/lp/data/normalized-mps-v2-20-10-cycle.opb
MD5SUMe48dda95f8e39d614f3e3f822031bbe2
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 0
Optimality of the best value was proved NO
Number of terms in the objective function 9240
Biggest coefficient in the objective function 53687091200000
Number of bits for the biggest coefficient in the objective function 46
Sum of the numbers in the objective function 1737924154969464
Number of bits of the sum of numbers in the objective function 51
Biggest number in a constraint 48888431614361600
Number of bits of the biggest number in a constraint 56
Biggest sum of numbers in a constraint 779202693141814557
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 benchmark1263.24
Number of variables84737
Total number of constraints1961
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 constraints1961
Minimum length of a constraint11
Maximum length of a constraint1470

Trace number 2732

Launcher Data

LAUNCH ON wulflinc20 THE 2005-09-18 21:31:28 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=3934 boxname=wulflinc20 idbench=418 idsolver=4 numberseed=0
MD5SUM SOLVER: 21c3ffd7205c96d5f0784fd273b92938  /oldhome/oroussel/solvers/PBS4
MD5SUM BENCH:  e48dda95f8e39d614f3e3f822031bbe2  /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-cycle.opb
REAL COMMAND:  PBS4 /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-cycle.opb
IDLAUNCH: 3934
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.215
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.215
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:        887156 kB
Buffers:         35708 kB
Cached:          82188 kB
SwapCached:        832 kB
Active:          84484 kB
Inactive:        36120 kB
HighTotal:      131008 kB
HighFree:        45416 kB
LowTotal:       903652 kB
LowFree:        841740 kB
SwapTotal:     2097892 kB
SwapFree:      2096604 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5732 kB
Slab:            21256 kB
Committed_AS:    64168 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-18 21:32:07 (client local time) WITH STATUS 20 IN 37.8442 SECONDS
stats: 3934 7 37.8442 20

Solver Data

c PBS v4 by Bashar Al-Rawi & Fadi Aloul
c Solving /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-cycle.opb ......
s UNSATISFIABLE
c Done, CPU Time=0.244963

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/16013/stat): 16013 (PBS4) R 16012 16013 2660 0 -1 0 18 0 0 0 0 0 0 0 23 0 1 0 1844514730 978944 2 4294967295 134512640 135450776 3221224560 3221224560 134512960 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/16013/statm): 239 2 232 232 0 7 0
[pid=16013] vsize: 956
open syscall for file /dev/null
open syscall for file /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-cycle.opb
open syscall for file /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-cycle.opb

[startup+10.0022 s]
Raw data (loadavg): 0.85 0.94 0.90 2/56 16013
Raw data (/proc/16013/stat): 16013 (PBS4) R 16012 16013 2660 0 -1 0 5169 0 0 0 981 16 0 0 25 0 1 0 1844514730 20176896 4647 4294967295 134512640 135450776 3221224560 3221223072 134601245 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/16013/statm): 4926 4647 232 232 0 4694 0
[pid=16013] vsize: 19704
Current children cumulated CPU time (s) 9.97
Current children cumulated vsize (Kb) 19704

[startup+20.0019 s]
Raw data (loadavg): 0.87 0.94 0.90 2/56 16013
Raw data (/proc/16013/stat): 16013 (PBS4) R 16012 16013 2660 0 -1 0 8994 0 0 0 1966 29 0 0 25 0 1 0 1844514730 35418112 8365 4294967295 134512640 135450776 3221224560 3221223072 134600357 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/16013/statm): 8647 8365 232 232 0 8415 0
[pid=16013] vsize: 34588
Current children cumulated CPU time (s) 19.95
Current children cumulated vsize (Kb) 34588

[startup+30.0026 s]
Raw data (loadavg): 0.89 0.94 0.90 2/56 16013
Raw data (/proc/16013/stat): 16013 (PBS4) R 16012 16013 2660 0 -1 0 8994 0 0 0 2960 33 0 0 25 0 1 0 1844514730 35418112 8365 4294967295 134512640 135450776 3221224560 3221223072 134601299 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/16013/statm): 8647 8365 232 232 0 8415 0
[pid=16013] vsize: 34588
Current children cumulated CPU time (s) 29.93
Current children cumulated vsize (Kb) 34588
One traced child (pid=16013) exited with status: 20
All traced children have exited ! Game is over.

Child status: 20
Real time (s): 37.9246
CPU time (s): 37.8442
CPU user time (s): 37.3773
CPU system time (s): 0.466929
CPU usage (%): 99.788
Max. virtual memory (cumulated for all children) (Kb): 34588

Verifier Data

ERROR: no interpretation found !