PB'05 competition: run trace

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:

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.
SOLVER DATA
This is the output of the solver (stdout and stderr).
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.
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

Name	normalized-opb/mps-v2-20-10/ftp.netlib.org/lp/data/normalized-mps-v2-20-10-maros.opb
MD5SUM	e0398e644ed8244eeb84fb20e0ca944b
Bench Category	optimization, big integers (OPTBIGINT)
Has Objective Function	YES
Satisfiable	NO
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of terms in the objective function	10110
Biggest coefficient in the objective function	330175610880000000
Number of bits for the biggest coefficient in the objective function	59
Sum of the numbers in the objective function	-3512679628005298690
Number of bits of the sum of numbers in the objective function	64
Biggest number in a constraint	330175610880000000
Number of bits of the biggest number in a constraint	59
Biggest sum of numbers in a constraint	-3512679628005298690
Number of bits of the biggest sum of numbers	64
Best result obtained on this benchmark	UNSAT
Best CPU time to get the best result obtained on this benchmark	0.363944
Number of variables	42240
Total number of constraints	844
Number of constraints which are clauses	0
Number of constraints which are cardinality constraints (but not clauses)	0
Number of constraints which are nor clauses,nor cardinality constraints	844
Minimum length of a constraint	30
Maximum length of a constraint	4740

Trace number 22740

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc30 THE 2005-04-22 03:59:20 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=10985 boxname=wulflinc30 idbench=845 idsolver=13 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  e0398e644ed8244eeb84fb20e0ca944b  /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-maros.opb
REAL COMMAND:  minisat+ -w /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-maros.opb /oldhome/oroussel/tmp/wulflinc30/normalized-mps-v2-20-10-maros.opb
IDLAUNCH: 10985
/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:        667204 kB
Buffers:         21916 kB
Cached:         319568 kB
SwapCached:        352 kB
Active:          63412 kB
Inactive:       280756 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        666952 kB
SwapTotal:     2097892 kB
SwapFree:      2097328 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5980 kB
Slab:            17588 kB
Committed_AS:    63600 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-04-22 03:59:20 (client local time) WITH STATUS 1 IN 0.014997 SECONDS
stats: 10985 7 0.014997 1
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c Parsing PB file...
PARSE ERROR! [line 1447] Integer overflow. Big numbers not supported yet.
#### END SOLVER DATA ####
#### BEGIN WATCHER DATA ####
Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing VSIZE limit: 943718400 bytes
Raw data (loadavg): 0.95 0.95 0.91 2/54 4100
Raw data (stat): 4100 (runsolver) R 4099 11931 11930 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 550664218 1052672 99 4294967295 134512640 135381576 3221224448 3221219692 135158418 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 1028
[startup+0.022757 s]
Raw data (loadavg): 0.95 0.95 0.91 1/53 4100
Raw data (stat): 4100 (runsolver) R 4099 11931 11930 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 550664218 1052672 99 4294967295 134512640 135381576 3221224448 3221219692 135158418 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 0

Child status: 1
Real time (s): 0.022516
CPU time (s): 0.014997
CPU user time (s): 0.009998
CPU system time (s): 0.004999
CPU usage (%): 66.606
Max. virtual memory (Kb): 1028
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
ERROR: no interpretation found !
#### END VERIFIER DATA ####