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

Namesubmitted/manquinho/primes-dimacs-cnf/normalized-ssa2670-141.opb
MD5SUM423b72910a463b7aa4b9bdae86b878a8
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
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 1972
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 1972
Number of bits of the sum of numbers in the objective function 11
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 1972
Number of bits of the biggest sum of numbers11
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.19497
Number of variables1972
Total number of constraints3301
Number of constraints which are clauses3301
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint5

Trace number 9649

Launcher Data

LAUNCH ON wulflinc29 THE 2005-09-23 14:59:07 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8413 boxname=wulflinc29 idbench=209 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  423b72910a463b7aa4b9bdae86b878a8  /oldhome/oroussel/tmp/wulflinc29/normalized-ssa2670-141.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc29/normalized-ssa2670-141.opb
IDLAUNCH: 8413
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.077
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.077
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:        930624 kB
Buffers:         11028 kB
Cached:          75944 kB
SwapCached:          0 kB
Active:          44016 kB
Inactive:        45896 kB
HighTotal:      131008 kB
HighFree:        55412 kB
LowTotal:       903652 kB
LowFree:        875212 kB
SwapTotal:     2097892 kB
SwapFree:      2097892 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6976 kB
Slab:             8548 kB
Committed_AS:    63624 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-23 14:59:08 (client local time) WITH STATUS 20 IN 0.497923 SECONDS
stats: 8413 7 0.497923 20

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
s UNSATISFIABLE

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/7195/stat): 7195 (pb2sat) R 7194 7195 4005 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 21054502 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/7195/statm): 373 2 364 364 0 9 0
[pid=7195] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc29/normalized-ssa2670-141.opb
One traced child (pid=7195) exited with status: 20
All traced children have exited ! Game is over.

Child status: 20
Real time (s): 0.516181
CPU time (s): 0.497923
CPU user time (s): 0.475927
CPU system time (s): 0.021996
CPU usage (%): 96.4629
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

ERROR: no interpretation found !