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).
  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

Namenormalized-opb/web/uclid_pb_benchmarks/normalized-ooo.tag14.ucl.opb
MD5SUMe4be8a88d340bbbbfb27e034f74a6524
Bench Categoryno optimization function (SAT)
Has Objective FunctionNO
SatisfiableNO
(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 65
Number of bits of the biggest number in a constraint 7
Biggest sum of numbers in a constraint 254
Number of bits of the biggest sum of numbers8
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark56.8973
Number of variables40605
Total number of constraints118930
Number of constraints which are clauses117190
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1740
Minimum length of a constraint1
Maximum length of a constraint13

Trace number 2774 

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc19 THE 2005-04-13 04:56:54 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=2803 boxname=wulflinc19 idbench=312 idsolver=4 numberseed=0
MD5SUM SOLVER: 1540ae3c74fe6bb56fea7dc39e0baf99  /oldhome/oroussel/solvers/galena
MD5SUM BENCH:  e4be8a88d340bbbbfb27e034f74a6524  /oldhome/oroussel/tmp/wulflinc19/normalized-ooo.tag14.ucl.opb
REAL COMMAND:  galena /oldhome/oroussel/tmp/wulflinc19/normalized-ooo.tag14.ucl.opb
IDLAUNCH: 2803
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.037
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	: 890.88

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.037
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:        915656 kB
Buffers:           132 kB
Cached:          84320 kB
SwapCached:         72 kB
Active:          12028 kB
Inactive:        75688 kB
HighTotal:      131008 kB
HighFree:        41804 kB
LowTotal:       903652 kB
LowFree:        873852 kB
SwapTotal:     2097892 kB
SwapFree:      2097792 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           7328 kB
Slab:            25468 kB
Committed_AS:    64036 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-04-13 04:57:03 (client local time) WITH STATUS 0 IN  SECONDS
stats: 2803 7  0
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c Decisions:	0
c Implications:	13
c RUNTIME:	7.79382s
s UNKNOWN
#### 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.91 0.97 0.91 2/55 17259
Raw data (stat): 17259 (runsolver) R 17258 10867 10866 0 -1 64 5 0 0 0 0 0 0 0 19 0 1 0 473237439 1056768 100 4294967295 134512640 135381576 3221221744 3221216500 135158418 0 0 7 90112 0 0 0 17 1 0 0
Raw data (statm): 258 100 215 215 0 43 0
vsize: 1032
[startup+8.14308 s]
Raw data (loadavg): 0.92 0.97 0.91 1/54 17259
Raw data (stat): 17259 (runsolver) R 17258 10867 10866 0 -1 64 5 0 0 0 0 0 0 0 19 0 1 0 473237439 1056768 100 4294967295 134512640 135381576 3221221744 3221216500 135158418 0 0 7 90112 0 0 0 17 1 0 0
Raw data (statm): 258 100 215 215 0 43 0
vsize: 0

Child status: 0
Real time (s): 8.14285
CPU time (s): 8.12776
CPU user time (s): 7.96879
CPU system time (s): 0.158975
CPU usage (%): 99.8147
Max. virtual memory (Kb): 1032
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
ERROR: no interpretation found !
#### END VERIFIER DATA ####