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/miplib3/normalized-mps-v2-20-10-enigma.opb
MD5SUM438e2455c0b7b4efdea6a7e48ef2555a
Bench Categoryoptimization, medium integers (OPTMEDINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 0
Optimality of the best value was proved YES
Number of terms in the objective function 9
Biggest coefficient in the objective function 9
Number of bits for the biggest coefficient in the objective function 4
Sum of the numbers in the objective function 45
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 900207
Number of bits of the biggest number in a constraint 20
Biggest sum of numbers in a constraint 9508275
Number of bits of the biggest sum of numbers24
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark2.20366
Number of variables100
Total number of constraints121
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)120
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint1
Maximum length of a constraint90

Trace number 4628

Launcher Data

LAUNCH ON wulflinc30 THE 2005-09-19 19:24:52 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=4189 boxname=wulflinc30 idbench=673 idsolver=4 numberseed=0
MD5SUM SOLVER: 21c3ffd7205c96d5f0784fd273b92938  /oldhome/oroussel/solvers/PBS4
MD5SUM BENCH:  438e2455c0b7b4efdea6a7e48ef2555a  /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-enigma.opb
REAL COMMAND:  PBS4 /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-enigma.opb
IDLAUNCH: 4189
/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:        902848 kB
Buffers:         32736 kB
Cached:          70472 kB
SwapCached:        764 kB
Active:          39236 kB
Inactive:        66608 kB
HighTotal:      131008 kB
HighFree:        59780 kB
LowTotal:       903652 kB
LowFree:        843068 kB
SwapTotal:     2097892 kB
SwapFree:      2096620 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5712 kB
Slab:            20412 kB
Committed_AS:    64304 kB
PageTables:        332 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-19 19:24:55 (client local time) WITH STATUS 30 IN 2.20366 SECONDS
stats: 4189 0 2.20366 30

Solver Data

c PBS v4 by Bashar Al-Rawi & Fadi Aloul
c Solving /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-enigma.opb ......
c The optimum solution is:0
s OPTIMUM FOUND
v A0_bit0 -A1_bit0 -A2_bit0 -A3_bit0 -A4_bit0 -A5_bit0 -A6_bit0 -A7_bit0 -A8_bit0 -A9_bit0 -B0_bit0 -B1_bit0 -B2_bit0 -B3_bit0 -B4_bit0 -B5_bit0 -B6_bit0 -B7_bit0 B8_bit0 -B9_bit0 -C0_bit0 -C1_bit0 -C2_bit0 -C3_bit0 -C4_bit0 C5_bit0 -C6_bit0 -C7_bit0 -C8_bit0 -C9_bit0 -D0_bit0 -D1_bit0 -D2_bit0 -D3_bit0 -D4_bit0 -D5_bit0 D6_bit0 -D7_bit0 -D8_bit0 -D9_bit0 -E0_bit0 -E1_bit0 -E2_bit0 -E3_bit0 E4_bit0 -E5_bit0 -E6_bit0 -E7_bit0 -E8_bit0 -E9_bit0 -F0_bit0 -F1_bit0 -F2_bit0 -F3_bit0 -F4_bit0 -F5_bit0 -F6_bit0 -F7_bit0 -F8_bit0 F9_bit0 -G0_bit0 G1_bit0 -G2_bit0 -G3_bit0 -G4_bit0 -G5_bit0 -G6_bit0 -G7_bit0 -G8_bit0 -G9_bit0 -H0_bit0 -H1_bit0 -H2_bit0 -H3_bit0 -H4_bit0 -H5_bit0 -H6_bit0 H7_bit0 -H8_bit0 -H9_bit0 -I0_bit0 -I1_bit0 I2_bit0 -I3_bit0 -I4_bit0 -I5_bit0 -I6_bit0 -I7_bit0 -I8_bit0 -I9_bit0 -L0_bit0 -L1_bit0 -L2_bit0 L3_bit0 -L4_bit0 -L5_bit0 -L6_bit0 -L7_bit0 -L8_bit0 -L9_bit0 
c Done, CPU Time=2.19067

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/22964/stat): 22964 (PBS4) R 22963 22964 5245 0 -1 0 18 0 0 0 0 0 0 0 22 0 1 0 1852383658 978944 2 4294967295 134512640 135450776 3221224560 3221224560 134512960 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/22964/statm): 239 2 232 232 0 7 0
[pid=22964] vsize: 956
open syscall for file /dev/null
open syscall for file /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-enigma.opb
open syscall for file /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-enigma.opb
One traced child (pid=22964) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 2.31724
CPU time (s): 2.20366
CPU user time (s): 2.10768
CPU system time (s): 0.095985
CPU usage (%): 95.0987
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	0