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/web/uclid_pb_benchmarks/normalized-blast-floppy1-7.ucl.opb
MD5SUM	0c52c70d5adb3b80d9053fcb18f76b68
Bench Category	no optimization function (SAT)
Has Objective Function	NO
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	0
Biggest coefficient in the objective function	0
Number of bits for the biggest coefficient in the objective function	0
Sum of the numbers in the objective function	0
Number of bits of the sum of numbers in the objective function	0
Biggest number in a constraint	6518
Number of bits of the biggest number in a constraint	13
Biggest sum of numbers in a constraint	18803
Number of bits of the biggest sum of numbers	15
Best result obtained on this benchmark	UNSAT
Best CPU time to get the best result obtained on this benchmark	0.371942
Number of variables	2913
Total number of constraints	3105
Number of constraints which are clauses	2259
Number of constraints which are cardinality constraints (but not clauses)	0
Number of constraints which are nor clauses,nor cardinality constraints	846
Minimum length of a constraint	1
Maximum length of a constraint	25

Trace number 4414

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc29 THE 2005-04-13 17:18:54 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=2484 boxname=wulflinc29 idbench=276 idsolver=9 numberseed=0
MD5SUM SOLVER: daf345f6fbf228671abfac48013b9cac  /oldhome/oroussel/solvers/sat4jPseudo.jar
MD5SUM BENCH:  0c52c70d5adb3b80d9053fcb18f76b68  /oldhome/oroussel/tmp/wulflinc29/normalized-blast-floppy1-7.ucl.opb
REAL COMMAND:  java -server -Xms650M -Xmx650M -jar /oldhome/oroussel/solvers/sat4jPseudo.jar /oldhome/oroussel/tmp/wulflinc29/normalized-blast-floppy1-7.ucl.opb
IDLAUNCH: 2484
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.020
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.020
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	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        874552 kB
Buffers:         35404 kB
Cached:          87392 kB
SwapCached:         12 kB
Active:          51876 kB
Inactive:        73736 kB
HighTotal:      131008 kB
HighFree:        40236 kB
LowTotal:       903652 kB
LowFree:        834316 kB
SwapTotal:     2097892 kB
SwapFree:      2097880 kB
Dirty:              40 kB
Writeback:           0 kB
Mapped:           6928 kB
Slab:            29004 kB
Committed_AS:    63492 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-04-13 17:19:04 (client local time) WITH STATUS 1 IN  SECONDS
stats: 2484 7  1
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c solving /oldhome/oroussel/tmp/wulflinc29/normalized-blast-floppy1-7.ucl.opb
c reading problem 
c [nbvar=2913]
c [nbconstr=3105]
c time 6.344
c #vars     2913
c #clauses  3105
c starts	: 0
c conflicts	: 0
c decisions	: 0
c propagations	: 0
c inspects	: 0
c learned literals	: 0
c learned binary clauses	: 0
c learned ternary clauses	: 0
c learned clauses	: 0
c root simplifications	: 0
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 2
	at org.sat4j.minisat.constraints.pb.MinWatchPb.propagate(MinWatchPb.java:323)
	at org.sat4j.minisat.core.Solver.propagate(Solver.java:523)
	at org.sat4j.minisat.core.Solver.search(Solver.java:606)
	at org.sat4j.minisat.core.Solver.isSatisfiable(Solver.java:793)
	at org.sat4j.minisat.core.Solver.isSatisfiable(Solver.java:744)
	at org.sat4j.LanceurPseudo2005.main(LanceurPseudo2005.java:83)
#### 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.80 0.95 0.94 2/54 28214
Raw data (stat): 28214 (runsolver) R 28213 27222 27221 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 477691964 1052672 99 4294967295 134512640 135381576 3221224432 3221219680 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+9.89364 s]
Raw data (loadavg): 0.99 0.99 0.95 1/53 28225
Raw data (stat): 28214 (runsolver) R 28213 27222 27221 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 477691964 1052672 99 4294967295 134512640 135381576 3221224432 3221219680 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): 9.8934
CPU time (s): 10.6894
CPU user time (s): 10.2014
CPU system time (s): 0.487925
CPU usage (%): 108.045
Max. virtual memory (Kb): 1028
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
ERROR: no interpretation found !
#### END VERIFIER DATA ####