Trace number 46384

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, and are wall clock time (not CPU 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
SAT4JPSEUDO 2006.2UNSAT 0.953854 0.678245

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/
submitted-PB06/roussel/normalized-pigeon-cardinality-31-30.opb
MD5SUM583fb36c9cf948cc03f361dd87435bdd
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, 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.006998
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables930
Total number of constraints61
Number of constraints which are clauses31
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 constraint30
Maximum length of a constraint31
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 32
Number of bits of the biggest sum of numbers6
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.14	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.14	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.14	c no version file found!!!
0.14	c sun.arch.data.model	32
0.14	c java.version	1.5.0_06
0.14	c os.name	Linux
0.14	c os.version	2.6.9-34.ELsmp
0.15	c os.arch	i386
0.15	c Free memory 1548419056
0.15	c Max memory 1551040512
0.15	c Total memory 1551040512
0.15	c Number of processors 2
0.21	c Cutting planes based inference
0.21	c --- Begin Solver configuration ---
0.21	c org.sat4j.minisat.uip.FirstUIP@1037c71
0.21	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1df073d
0.21	c org.sat4j.minisat.learning.MiniSATLearning@1546e25
0.21	c conflictBoundIncFactor=1.5 learntBoundIncFactor=1.1 initLearntBoundConstraintFactor=10000.0 initConflictBound=100 
0.21	c VSIDS like heuristics from MiniSAT using a heap
0.21	c No reason simplification
0.21	c --- End Solver configuration ---
0.21	c solving ROOT/tmp/node84/46384-1149799279/instance-46384-1149799279.opb
0.21	c reading problem ... 
0.37	c ... done. Time 0.16 ms.
0.37	c #vars     930
0.37	c #constraints  61
0.64	c starts		: 1
0.64	c conflicts		: 30
0.64	c decisions		: 436
0.64	c propagations		: 958
0.64	c inspects		: 552
0.64	c learnt literals	: 0
0.64	c learnt binary clauses	: 0
0.64	c learnt ternary clauses	: 0
0.64	c learnt clauses	: 29
0.64	c root simplifications	: 0
0.64	c removed literals (reason simplification)	: 0
0.64	c reason swapping (by a shorter reason)	: 0
0.64	c Calls to reduceDB	: 0
0.64	c speed (decisions/second)	: 1639.0977443609022
0.64	c non guided choices	436
0.64	s UNSATISFIABLE
0.64	c Total wall clock time (ms): 0.429

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes

runsolver version 3.0.1 (c) roussel@cril.univ-artois.fr

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node84/watcher-46384-1149799279 -o ROOT/results/node84/solver-46384-1149799279 -C 1800 -M 1800 -S 64 java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node84/46384-1149799279/instance-46384-1149799279.opb 866879733 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.94 0.91 2/67 648
/proc/meminfo: memFree=1544856/2055892 swapFree=4085312/4096564
[pid=648] ppid=646 vsize=1456 CPUtime=0
/proc/648/stat : 648 (java) R 646 648 602 0 -1 0 103 0 0 0 0 0 0 0 19 0 1 0 245567152 1490944 73 18446744073709551615 134512640 134570276 4294956624 18446744073709551615 9009126 0 0 4096 0 0 0 0 17 1 0 0
/proc/648/statm: 365 83 65 14 0 9 0

Child status: 20
Real time (s): 0.678245
CPU time (s): 0.953854
CPU user time (s): 0.898863
CPU system time (s): 0.054991
CPU usage (%): 140.636
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node84 on Thu Jun  8 20:41:19 UTC 2006


FILE ID= 46384-1149799279

PBS_JOBID= 378854

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/roussel/normalized-pigeon-cardinality-31-30.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node84/46384-1149799279/instance-46384-1149799279.opb 866879733
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-46384-1149799279 -o ROOT/results/node84/solver-46384-1149799279 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node84/46384-1149799279/instance-46384-1149799279.opb 866879733

MD5SUM SOLVER= e9637a7554f3ecdf74c1815f89d00213
MD5SUM BENCH=  583fb36c9cf948cc03f361dd87435bdd

RANDOM SEED= 866879733


/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.231
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	: 6006.15
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.231
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	: 5999.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1545192 kB
Buffers:         33460 kB
Cached:         412200 kB
SwapCached:       2460 kB
Active:         116328 kB
Inactive:       338068 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1545192 kB
SwapTotal:     4096564 kB
SwapFree:      4085312 kB
Dirty:             300 kB
Writeback:           0 kB
Mapped:          16436 kB
Slab:            42992 kB
Committed_AS:   543156 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Thu Jun  8 20:41:19 UTC 2006