Trace number 49169

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 NameAnswerObjective functionCPU timeWall clock time
absconPseudo 1OPT5 3.59045 3.14411

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/
manquiho/logic_synthesis/normalized-opus.r.opb
MD5SUM0485a54e08821af6e5a7651e5ae0ba80
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark5
Best CPU time to get the best result obtained on this benchmark0.012997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 5
Optimality of the best value was proved YES
Number of variables63
Total number of constraints45
Number of constraints which are clauses45
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 constraint42
Number of terms in the objective function 63
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 63
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 63
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

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.80	o 6
0.80	o 5
3.08	s OPTIMUM FOUND
3.08	v -x1 -x2 -x3 x4 -x5 -x6 x7 -x8 -x9 -x10 -x11 -x12 x13 -x14 -x15 -x16 -x17 -x18 -x19 -x20 -x21 -x22 -x23 -x24 -x25 -x26 -x27 -x28 -x29
3.08	v -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 x51 -x52 -x53 -x54 -x55
3.08	v -x56 -x57 -x58 x59 -x60 -x61 -x62 -x63
3.08	c nb removed universal constraints = 0
3.08	c nb removed unary constraints = 1
3.08	c cputime = 2777.0ms

Verifier Data (download as text)

OK	5

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/node79/watcher-49169-1149872904 -o ROOT/results/node79/solver-49169-1149872904 -C 1800 -M 1800 -S 64 java -server -Xms256M -Xmx1500M -cp ROOT/solvers/PB/PB06final/user2/absconPseudo1.jar abscon.Resolution ROOT/solvers/PB/PB06final/user2/configuration.xml 1 pseudo ROOT/tmp/node79/49169-1149872904/instance-49169-1149872904.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.06 0.02 0.00 2/67 29058
/proc/meminfo: memFree=1716088/2055892 swapFree=4085412/4096564
[pid=29058] ppid=29056 vsize=312 CPUtime=0
/proc/29058/stat : 29058 (java) R 29056 29058 29012 0 -1 0 58 0 0 0 0 0 0 0 19 0 1 0 252929027 319488 41 18446744073709551615 134512640 134570276 4294956512 18446744073709551615 2550919 0 0 4096 0 0 0 0 17 1 0 0
/proc/29058/statm: 78 41 32 14 0 5 0

Child status: 0
Real time (s): 3.14411
CPU time (s): 3.59045
CPU user time (s): 3.52846
CPU system time (s): 0.06199
CPU usage (%): 114.196
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node79 on Fri Jun  9 17:08:24 UTC 2006


FILE ID= 49169-1149872904

PBS_JOBID= 384401

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-opus.r.opb
COMMAND LINE= java -server -Xms256M -Xmx1500M -cp ROOT/solvers/PB/PB06final/user2/absconPseudo1.jar abscon.Resolution ROOT/solvers/PB/PB06final/user2/configuration.xml 1 pseudo  ROOT/tmp/node79/49169-1149872904/instance-49169-1149872904.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node79/watcher-49169-1149872904 -o ROOT/results/node79/solver-49169-1149872904 -C 1800 -M 1800 -S 64  java -server -Xms256M -Xmx1500M -cp ROOT/solvers/PB/PB06final/user2/absconPseudo1.jar abscon.Resolution ROOT/solvers/PB/PB06final/user2/configuration.xml 1 pseudo  ROOT/tmp/node79/49169-1149872904/instance-49169-1149872904.opb

MD5SUM SOLVER= 4ca9ffbd6a9584cc3ed948681986e0cb 7445d5e2b836dfb8cfc1479ab819c771
MD5SUM BENCH=  0485a54e08821af6e5a7651e5ae0ba80

RANDOM SEED= 590345964


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1716488 kB
Buffers:         34832 kB
Cached:         241316 kB
SwapCached:       2448 kB
Active:         106784 kB
Inactive:       178148 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1716488 kB
SwapTotal:     4096564 kB
SwapFree:      4085412 kB
Dirty:             136 kB
Writeback:           0 kB
Mapped:          16564 kB
Slab:            41096 kB
Committed_AS:   575928 kB
PageTables:       1304 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node79 on Fri Jun  9 17:08:27 UTC 2006