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/www.csit.fsu.edu/~burkardt/datasets/mps/normalized-mps-v2-20-10-testprob.opb
MD5SUMda2667b4c8b643a355efc1f418e48913
Bench Categoryoptimization, big integers (OPTBIGINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 9663726592
Optimality of the best value was proved YES
Number of terms in the objective function 56
Biggest coefficient in the objective function 9663676416
Number of bits for the biggest coefficient in the objective function 34
Sum of the numbers in the objective function 19327377394
Number of bits of the sum of numbers in the objective function 35
Biggest number in a constraint 9663676416
Number of bits of the biggest number in a constraint 34
Biggest sum of numbers in a constraint 19327377394
Number of bits of the biggest sum of numbers35
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.096985
Number of variables56
Total number of constraints5
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 constraints5
Minimum length of a constraint12
Maximum length of a constraint44

Trace number 10225

Launcher Data

LAUNCH ON wulflinc20 THE 2005-09-23 17:42:02 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8988 boxname=wulflinc20 idbench=784 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  da2667b4c8b643a355efc1f418e48913  /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-testprob.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-testprob.opb
IDLAUNCH: 8988
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.012
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.012
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:        935232 kB
Buffers:         12224 kB
Cached:          70532 kB
SwapCached:          0 kB
Active:          45764 kB
Inactive:        39864 kB
HighTotal:      131008 kB
HighFree:        56084 kB
LowTotal:       903652 kB
LowFree:        879148 kB
SwapTotal:     2097892 kB
SwapFree:      2097892 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6980 kB
Slab:             8240 kB
Committed_AS:    63660 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-23 17:42:03 (client local time) WITH STATUS 30 IN 0.483925 SECONDS
stats: 8988 0 0.483925 30

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 9663744996
c small objective detected
c CONFLICT during preprocess 
c [startup+0.130404 s]  setting bit 34 to 0
c CONFLICT during preprocess 
c [startup+0.138237 s]  setting bit 33 to 0
c CONFLICT during preprocess 
c [startup+0.146142 s]  setting bit 32 to 0
c CONFLICT during preprocess 
c [startup+0.154272 s]  setting bit 31 to 0
c CONFLICT during preprocess 
c [startup+0.162489 s]  setting bit 30 to 0
c CONFLICT during preprocess 
c [startup+0.170802 s]  setting bit 29 to 0
c CONFLICT during preprocess 
c [startup+0.179208 s]  setting bit 28 to 0
c CONFLICT during preprocess 
c [startup+0.187701 s]  setting bit 27 to 0
c CONFLICT during preprocess 
c [startup+0.196287 s]  setting bit 26 to 0
c CONFLICT during preprocess 
c [startup+0.204997 s]  setting bit 25 to 0
c CONFLICT during preprocess 
c [startup+0.213807 s]  setting bit 24 to 0
c CONFLICT during preprocess 
c [startup+0.222598 s]  setting bit 23 to 0
c CONFLICT during preprocess 
c [startup+0.231506 s]  setting bit 22 to 0
c CONFLICT during preprocess 
c [startup+0.240434 s]  setting bit 21 to 0
c CONFLICT during preprocess 
c [startup+0.24946 s]  setting bit 20 to 0
c CONFLICT during preprocess 
c [startup+0.258506 s]  setting bit 19 to 0
c CONFLICT during preprocess 
c [startup+0.267599 s]  setting bit 18 to 0
c CONFLICT during preprocess 
c [startup+0.276759 s]  setting bit 17 to 0
c CONFLICT during preprocess 
c [startup+0.286163 s]  setting bit 16 to 0
c CONFLICT during preprocess 
c [startup+0.295509 s]  setting bit 15 to 0
c got solution with objective value: 9663728228
c [startup+0.311891 s]  setting bit 14 to 1
c CONFLICT during preprocess 
c [startup+0.321605 s]  setting bit 13 to 0
c CONFLICT during preprocess 
c [startup+0.331668 s]  setting bit 12 to 0
c CONFLICT during preprocess 
c [startup+0.344167 s]  setting bit 11 to 0
c got solution with objective value: 9663726981
c [startup+0.359111 s]  setting bit 10 to 1
c got solution with objective value: 9663726773
c [startup+0.37301 s]  setting bit 9 to 1
c got solution with objective value: 9663726773
c [startup+0.386738 s]  setting bit 8 to 1
c got solution with objective value: 9663726690
c [startup+0.400345 s]  setting bit 7 to 1
c got solution with objective value: 9663726616
c [startup+0.414193 s]  setting bit 6 to 1
c got solution with objective value: 9663726592
c [startup+0.430592 s]  setting bit 5 to 1
c CONFLICT during preprocess 
c [startup+0.440873 s]  setting bit 4 to 0
c CONFLICT during preprocess 
c [startup+0.450974 s]  setting bit 3 to 0
c CONFLICT during preprocess 
c [startup+0.461014 s]  setting bit 2 to 0
c got solution with objective value: 9663726592
c [startup+0.474308 s]  setting bit 1 to 1
c got solution with objective value: 9663726592
c [startup+0.487376 s]  setting bit 0 to 1
s OPTIMUM FOUND
v -X1_bit0 -X1_bit1 X1_bit2 -X1_bit_1 -X1_bit_10 -X1_bit_2 -X1_bit_3 -X1_bit_4 -X1_bit_5 -X1_bit_6 -X1_bit_7 -X1_bit_8 -X1_bit_9 -X2_bit0 -X2_bit1 -X2_bit_1 -X2_bit_10 -X2_bit_2 -X2_bit_3 -X2_bit_4 -X2_bit_5 -X2_bit_6 -X2_bit_7 -X2_bit_8 -X2_bit_9 X3_bit0 -X3_bit1 -X3_bit10 -X3_bit11 -X3_bit12 -X3_bit13 -X3_bit14 -X3_bit15 -X3_bit16 -X3_bit17 -X3_bit18 -X3_bit19 X3_bit2 X3_bit20 -X3_bit3 -X3_bit4 -X3_bit5 -X3_bit6 -X3_bit7 -X3_bit8 -X3_bit9 -X3_bit_1 -X3_bit_10 -X3_bit_2 -X3_bit_3 -X3_bit_4 -X3_bit_5 -X3_bit_6 -X3_bit_7 -X3_bit_8 -X3_bit_9

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/8919/stat): 8919 (pb2sat) R 8918 8919 4059 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 22070247 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/8919/statm): 373 2 364 364 0 9 0
[pid=8919] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc20/normalized-mps-v2-20-10-testprob.opb
One traced child (pid=8919) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 0.50097
CPU time (s): 0.483925
CPU user time (s): 0.467928
CPU system time (s): 0.015997
CPU usage (%): 96.5976
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	9663726592