Trace number 1858152

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 into four (or five) parts:
  1. 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 ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock time.

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. 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.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. 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 X seconds (see the parameters in the trace). 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 X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    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.
  5. 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 provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
SAT4J Pseudo CP 2.1.1UNSAT 1.02784 0.684681

General information on the benchmark

Namenormalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/
manquinho/dbsg/normalized-dbsg_10_4_1_5.opb
MD5SUM14862c55d738c6710b33c768e4cbc554
Bench CategoryDEC-SMALLINT-NLC (no optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.003998
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables20
Total number of constraints32
Number of constraints which are clauses10
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints21
Minimum length of a constraint2
Maximum length of a constraint20
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 5
Number of bits of the biggest number in a constraint 3
Biggest sum of numbers in a constraint 20
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)96
Sum of products size (including duplicates)192
Number of different products48
Sum of products size96

Solver Data 

0.08/0.14	c SAT4J: a SATisfiability library for Java (c) 2004-2008 Daniel Le Berre
0.08/0.14	c This is free software under the dual EPL/GNU LGPL licenses.
0.08/0.14	c See www.sat4j.org for details.
0.08/0.15	c version 2.1.1.v20090612
0.08/0.15	c sun.arch.data.model	32
0.08/0.15	c java.version	1.6.0_12
0.08/0.15	c os.name	Linux
0.08/0.15	c os.version	2.6.9-22.EL.rootsmp
0.08/0.15	c os.arch	i386
0.08/0.15	c Free memory 1342000320
0.08/0.15	c Max memory 1344274432
0.08/0.15	c Total memory 1344274432
0.08/0.15	c Number of processors 2
0.22/0.21	c Pseudo Boolean Optimization
0.22/0.21	c Cutting planes based inference (org.sat4j.pb.core.PBSolverCP)
0.22/0.21	c --- Begin Solver configuration ---
0.22/0.21	c Stops conflict analysis at the first Unique Implication Point
0.22/0.21	c org.sat4j.pb.constraints.PBMaxClauseCardConstrDataStructure@1d520c4
0.22/0.21	c Learn all clauses as in MiniSAT
0.22/0.21	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.22/0.21	c VSIDS like heuristics from MiniSAT using a heap phase appearing in latest learned clause taking into account the objective function
0.22/0.21	c No reason simplification
0.22/0.21	c MiniSAT restarts strategy
0.22/0.21	c Memory based learned constraints deletion strategy
0.22/0.21	c timeout=2147483s
0.22/0.21	c DB Simplification allowed=false
0.22/0.21	c --- End Solver configuration ---
0.22/0.21	c solving HOME/instance-1858152-1244971639.opb
0.22/0.21	c reading problem ... 
0.22/0.26	c ... done. Wall clock time 0.049s.
0.22/0.26	c #vars     68
0.22/0.26	c #constraints  129
0.22/0.26	c constraints type 
0.22/0.26	c org.sat4j.pb.constraints.pb.OriginalBinaryClausePB => 10
0.22/0.26	c org.sat4j.pb.constraints.pb.OriginalHTClausePB => 48
0.22/0.26	c org.sat4j.pb.constraints.pb.MinWatchCardPB => 23
0.22/0.26	c org.sat4j.pb.constraints.pb.MaxWatchPb => 48
0.90/0.64	c starts		: 1
0.90/0.64	c conflicts		: 69
0.90/0.64	c decisions		: 118
0.90/0.64	c propagations		: 817
0.90/0.64	c inspects		: 9060
0.90/0.64	c learnt literals	: 0
0.90/0.64	c learnt binary clauses	: 0
0.90/0.64	c learnt ternary clauses	: 0
0.90/0.64	c learnt clauses	: 68
0.90/0.64	c ignored clauses	: 0
0.90/0.64	c root simplifications	: 0
0.90/0.64	c removed literals (reason simplification)	: 0
0.90/0.64	c reason swapping (by a shorter reason)	: 0
0.90/0.64	c Calls to reduceDB	: 0
0.90/0.64	c speed (assignments/second)	: 2150.0
0.90/0.64	c non guided choices	52
0.90/0.64	c learnt constraints type 
0.90/0.64	c org.sat4j.pb.constraints.pb.MinWatchCardPB => 1
0.90/0.64	c org.sat4j.pb.constraints.pb.MaxWatchPb => 67
0.90/0.64	c constraints type 
0.90/0.64	c org.sat4j.pb.constraints.pb.OriginalBinaryClausePB => 10
0.90/0.64	c org.sat4j.pb.constraints.pb.OriginalHTClausePB => 48
0.90/0.64	c org.sat4j.pb.constraints.pb.MinWatchCardPB => 23
0.90/0.64	c org.sat4j.pb.constraints.pb.MaxWatchPb => 48
0.90/0.64	s UNSATISFIABLE
0.90/0.64	c Total wall clock time (in seconds): 0.431

Verifier Data 

ERROR: no interpretation found !

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1858152-1244971639/watcher-1858152-1244971639 -o /tmp/evaluation-result-1858152-1244971639/solver-1858152-1244971639 -C 1800 -W 2000 -M 1800 java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar CuttingPlanes HOME/instance-1858152-1244971639.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.23 1.06 1.02 2/64 17865
/proc/meminfo: memFree=1291896/2055920 swapFree=4182536/4192956
[pid=17865] ppid=17863 vsize=152 CPUtime=0
/proc/17865/stat : 17865 (java6) R 17863 17865 17300 0 -1 0 41 0 0 0 0 0 0 0 21 0 1 0 164760249 155648 26 1992294400 134512640 134550932 4294956160 18446744073709551615 10518827 0 0 4096 0 0 0 0 17 1 0 0
/proc/17865/statm: 38 26 19 9 0 4 0

[startup+0.104037 s]
/proc/loadavg: 1.23 1.06 1.02 2/64 17865
/proc/meminfo: memFree=1291896/2055920 swapFree=4182536/4192956
[pid=17865] ppid=17863 vsize=1472584 CPUtime=0.08
/proc/17865/stat : 17865 (java) S 17863 17865 17300 0 -1 0 3618 0 1 0 6 2 0 0 21 0 12 0 164760249 1507926016 3361 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17865/statm: 368146 3361 1068 9 0 365494 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1472584

[startup+0.202055 s]
/proc/loadavg: 1.23 1.06 1.02 2/64 17865
/proc/meminfo: memFree=1291896/2055920 swapFree=4182536/4192956
[pid=17865] ppid=17863 vsize=1474992 CPUtime=0.22
/proc/17865/stat : 17865 (java) S 17863 17865 17300 0 -1 0 4750 0 1 0 19 3 0 0 21 0 12 0 164760249 1510391808 4488 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17865/statm: 368748 4488 1341 9 0 366091 0
Current children cumulated CPU time (s) 0.22
Current children cumulated vsize (KiB) 1474992

[startup+0.30207 s]
/proc/loadavg: 1.23 1.06 1.02 2/64 17865
/proc/meminfo: memFree=1291896/2055920 swapFree=4182536/4192956
[pid=17865] ppid=17863 vsize=1475316 CPUtime=0.35
/proc/17865/stat : 17865 (java) S 17863 17865 17300 0 -1 0 5081 0 1 0 32 3 0 0 21 0 13 0 164760249 1510723584 4819 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17865/statm: 368829 4819 1357 9 0 366172 0
Current children cumulated CPU time (s) 0.35
Current children cumulated vsize (KiB) 1475316

Solver just ended. Dumping a history of the last processes samples

[startup+0.402091 s]
/proc/loadavg: 1.23 1.06 1.02 2/64 17865
/proc/meminfo: memFree=1291896/2055920 swapFree=4182536/4192956
[pid=17865] ppid=17863 vsize=1478936 CPUtime=0.51
/proc/17865/stat : 17865 (java) S 17863 17865 17300 0 -1 0 6495 0 1 0 47 4 0 0 21 0 13 0 164760249 1514430464 5872 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17865/statm: 369734 5872 1380 9 0 367077 0
Current children cumulated CPU time (s) 0.51
Current children cumulated vsize (KiB) 1478936

[startup+0.60213 s]
/proc/loadavg: 1.23 1.06 1.02 2/64 17865
/proc/meminfo: memFree=1291896/2055920 swapFree=4182536/4192956
[pid=17865] ppid=17863 vsize=1478936 CPUtime=0.9
/proc/17865/stat : 17865 (java) S 17863 17865 17300 0 -1 0 7456 0 1 0 85 5 0 0 21 0 13 0 164760249 1514430464 6513 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17865/statm: 369734 6513 1389 9 0 367077 0
Current children cumulated CPU time (s) 0.9
Current children cumulated vsize (KiB) 1478936

Child status: 20
Real time (s): 0.684681
CPU time (s): 1.02784
CPU user time (s): 0.967852
CPU system time (s): 0.05999
CPU usage (%): 150.12
Max. virtual memory (cumulated for all children) (KiB): 1478936

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.967852
system time used= 0.05999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7679
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 190
involuntary context switches= 155

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node47 at 2009-06-14 11:27:19
IDJOB=1858152
IDBENCH=48374
IDSOLVER=681
FILE ID=node47/1858152-1244971639
PBS_JOBID= 9355015
Free space on /tmp= 66092 MiB

SOLVER NAME= SAT4J Pseudo CP 2.1.1
BENCH NAME= PB07/normalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/manquinho/dbsg/normalized-dbsg_10_4_1_5.opb
COMMAND LINE= java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar CuttingPlanes BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1858152-1244971639/watcher-1858152-1244971639 -o /tmp/evaluation-result-1858152-1244971639/solver-1858152-1244971639 -C 1800 -W 2000 -M 1800  java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar CuttingPlanes HOME/instance-1858152-1244971639.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 14862c55d738c6710b33c768e4cbc554
RANDOM SEED=1998628315

node47.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.261
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.261
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1292376 kB
Buffers:         67840 kB
Cached:         628336 kB
SwapCached:       4224 kB
Active:         116384 kB
Inactive:       587716 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1292376 kB
SwapTotal:     4192956 kB
SwapFree:      4182536 kB
Dirty:             528 kB
Writeback:           0 kB
Mapped:          13676 kB
Slab:            45404 kB
Committed_AS:   140220 kB
PageTables:       1448 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66092 MiB
End job on node47 at 2009-06-14 11:27:19