Trace number 1855076

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 0.461929 0.41213

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/
aloul/FPGA_SAT05/normalized-chnl15_20_pb.cnf.cr.opb
MD5SUMd9b1351aa6c01bb5c883e4233663f5e0
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
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.022995
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables600
Total number of constraints70
Number of constraints which are clauses40
Number of constraints which are cardinality constraints (but not clauses)30
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint15
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 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 21
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

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@ecd7e
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-1855076-1244866501.opb
0.22/0.21	c reading problem ... 
0.33/0.32	c ... done. Wall clock time 0.109s.
0.33/0.32	c #vars     600
0.33/0.32	c #constraints  70
0.33/0.32	c constraints type 
0.33/0.33	c org.sat4j.pb.constraints.pb.OriginalHTClausePB => 40
0.33/0.33	c org.sat4j.pb.constraints.pb.MinWatchCardPB => 30
0.33/0.36	c starts		: 1
0.33/0.36	c conflicts		: 1
0.33/0.36	c decisions		: 106
0.33/0.36	c propagations		: 296
0.33/0.36	c inspects		: 296
0.33/0.36	c learnt literals	: 0
0.33/0.36	c learnt binary clauses	: 0
0.33/0.36	c learnt ternary clauses	: 0
0.33/0.36	c learnt clauses	: 0
0.33/0.36	c ignored clauses	: 0
0.33/0.36	c root simplifications	: 0
0.33/0.36	c removed literals (reason simplification)	: 0
0.33/0.36	c reason swapping (by a shorter reason)	: 0
0.33/0.36	c Calls to reduceDB	: 0
0.33/0.36	c speed (assignments/second)	: 8457.142857142857
0.33/0.36	c non guided choices	106
0.33/0.37	c learnt constraints type 
0.33/0.37	c constraints type 
0.33/0.37	c org.sat4j.pb.constraints.pb.OriginalHTClausePB => 40
0.33/0.37	c org.sat4j.pb.constraints.pb.MinWatchCardPB => 30
0.33/0.37	s UNSATISFIABLE
0.33/0.37	c Total wall clock time (in seconds): 0.151

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-1855076-1244866501/watcher-1855076-1244866501 -o /tmp/evaluation-result-1855076-1244866501/solver-1855076-1244866501 -C 1800 -W 2000 -M 1800 java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar CuttingPlanes HOME/instance-1855076-1244866501.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.24 1.16 1.06 2/64 6580
/proc/meminfo: memFree=1258368/2055920 swapFree=4183064/4192956
[pid=6580] ppid=6578 vsize=152 CPUtime=0
/proc/6580/stat : 6580 (java6) R 6578 6580 5749 0 -1 0 41 0 0 0 0 0 0 0 20 0 1 0 154251006 155648 26 1992294400 134512640 134550932 4294956160 18446744073709551615 7893796 0 0 4096 0 0 0 0 17 1 0 0
/proc/6580/statm: 38 26 19 9 0 4 0

[startup+0.0111871 s]
/proc/loadavg: 1.24 1.16 1.06 2/64 6580
/proc/meminfo: memFree=1258368/2055920 swapFree=4183064/4192956
[pid=6580] ppid=6578 vsize=12928 CPUtime=0
/proc/6580/stat : 6580 (java) R 6578 6580 5749 0 -1 0 388 0 0 0 0 0 0 0 18 0 1 0 154251006 13238272 195 1992294400 134512640 134550932 4294956000 18446744073709551615 7865130 0 0 4096 0 0 0 0 17 1 0 0
/proc/6580/statm: 3232 202 136 9 0 1104 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12928

[startup+0.10121 s]
/proc/loadavg: 1.24 1.16 1.06 2/64 6580
/proc/meminfo: memFree=1258368/2055920 swapFree=4183064/4192956
[pid=6580] ppid=6578 vsize=1472584 CPUtime=0.08
/proc/6580/stat : 6580 (java) S 6578 6580 5749 0 -1 0 3637 0 1 0 6 2 0 0 18 0 12 0 154251006 1507926016 3380 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/6580/statm: 368146 3380 1068 9 0 365494 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1472584

[startup+0.301249 s]
/proc/loadavg: 1.24 1.16 1.06 2/64 6580
/proc/meminfo: memFree=1258368/2055920 swapFree=4183064/4192956
[pid=6580] ppid=6578 vsize=1474748 CPUtime=0.33
/proc/6580/stat : 6580 (java) S 6578 6580 5749 0 -1 0 5019 0 1 0 30 3 0 0 18 0 12 0 154251006 1510141952 4756 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/6580/statm: 368687 4756 1356 9 0 366030 0
Current children cumulated CPU time (s) 0.33
Current children cumulated vsize (KiB) 1474748

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

[startup+0.402265 s]
/proc/loadavg: 1.24 1.16 1.06 2/64 6580
/proc/meminfo: memFree=1258368/2055920 swapFree=4183064/4192956
[pid=6580] ppid=6578 vsize=1475576 CPUtime=0.44
/proc/6580/stat : 6580 (java) S 6578 6580 5749 0 -1 0 5235 0 1 0 41 3 0 0 18 0 13 0 154251006 1510989824 4972 1992294400 134512640 134550932 4294956000 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/6580/statm: 368894 4972 1374 9 0 366237 0
Current children cumulated CPU time (s) 0.44
Current children cumulated vsize (KiB) 1475576

Child status: 20
Real time (s): 0.41213
CPU time (s): 0.461929
CPU user time (s): 0.418936
CPU system time (s): 0.042993
CPU usage (%): 112.083
Max. virtual memory (cumulated for all children) (KiB): 1475576

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.418936
system time used= 0.042993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5240
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= 116
involuntary context switches= 74

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node5 at 2009-06-13 06:15:01
IDJOB=1855076
IDBENCH=1389
IDSOLVER=681
FILE ID=node5/1855076-1244866501
PBS_JOBID= 9354362
Free space on /tmp= 66352 MiB

SOLVER NAME= SAT4J Pseudo CP 2.1.1
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-chnl15_20_pb.cnf.cr.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-1855076-1244866501/watcher-1855076-1244866501 -o /tmp/evaluation-result-1855076-1244866501/solver-1855076-1244866501 -C 1800 -W 2000 -M 1800  java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar CuttingPlanes HOME/instance-1855076-1244866501.opb

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

MD5SUM BENCH= d9b1351aa6c01bb5c883e4233663f5e0
RANDOM SEED=2127158349

node5.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.259
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	: 5931.00
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.259
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:       1258848 kB
Buffers:         71272 kB
Cached:         635908 kB
SwapCached:       4304 kB
Active:          62748 kB
Inactive:       652916 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1258848 kB
SwapTotal:     4192956 kB
SwapFree:      4183064 kB
Dirty:             444 kB
Writeback:           0 kB
Mapped:          14600 kB
Slab:            67488 kB
Committed_AS:   119944 kB
PageTables:       1392 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= 66352 MiB
End job on node5 at 2009-06-13 06:15:02