Trace number 2657206

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 NameAnswerobjective functionCPU timeWall clock time
bsolo 3.2 CardOPT6 0.004998 0.0098211

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
bounded_golomb_rulers/normalized-bogr_4.opb
MD5SUMe07d1b5f59078d7e9ac49c5c9d354a5d
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark6
Best CPU time to get the best result obtained on this benchmark0.002998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 6
Optimality of the best value was proved YES
Number of variables38
Total number of constraints44
Number of constraints which are clauses1
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints43
Minimum length of a constraint1
Maximum length of a constraint18
Number of terms in the objective function 5
Biggest coefficient in the objective function 8
Number of bits for the biggest coefficient in the objective function 4
Sum of the numbers in the objective function 21
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 32
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 114
Number of bits of the biggest sum of numbers7
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 

0.00/0.00	c bsolo beta version 3.2 - 23/05/2010 : 1630 GMT
0.00/0.00	c Developed by Vasco Manquinho and José Santos IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Learning Strategy: Cardinality Constraint Learning
0.00/0.00	c Instance file HOME/instance-2657206-1276618634.opb
0.00/0.00	c File size is 4199 bytes.
0.00/0.00	c Highest Coefficient sum: 114
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 38 Constr: 44 1/0/43 Lit: 542 Watch. Lit: 205
0.00/0.00	c Obj. Vars: 5 (13.1579 % of total variables)
0.00/0.00	c Pre-processing Time: 0.001 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     36       43      541   12      333    1082      0      0 0.00
0.00/0.00	c Switching off lower bounding mode.
0.00/0.00	o 18
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       11     36       63      685   10      441    1093     20   5500 0.00
0.00/0.00	o 10
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       16     36       72      745   10      426    1093     29   8000 0.00
0.00/0.00	o 8
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       17     33       75      750   10      437    1089     32   8500 0.00
0.00/0.00	o 6
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       19     29       79      757    9      441    1086     36   6333 0.00
0.00/0.00	v -x1 -x2 -x3 -x4 x38 -x5 -x6 -x7 -x8 x14 -x15 -x16 -x17 -x37 -x9 -x10 -x11 -x12 -x13 -x36 x35 x34 x33 x32 -x31 x30 x29 x28 x27 x26 x25 x24 x23 x22 x21 x20 x19 x18 
0.00/0.00	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.00	c    4       19     14       81       79      757     36   6333 0.00
0.00/0.00	c Objective: 6
0.00/0.00	s OPTIMUM FOUND
0.00/0.00	c Total time: 0.003 s

Verifier Data 

OK	6

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2657206-1276618634/watcher-2657206-1276618634 -o /tmp/evaluation-result-2657206-1276618634/solver-2657206-1276618634 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l2 HOME/instance-2657206-1276618634.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.00 1.00 1.00 3/106 10608
/proc/meminfo: memFree=1763996/2059040 swapFree=4192956/4192956
[pid=10608] ppid=10606 vsize=0 CPUtime=0
/proc/10608/stat : 10608 (bsolo_pb10) Z 10606 10608 10498 0 -1 4202524 322 0 0 0 0 0 0 0 23 0 1 0 3155399 0 0 1992294400 0 0 0 0 0 0 0 4096 16384 18446744073709551615 0 0 17 1 0 0 0
/proc/10608/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.0098211
CPU time (s): 0.004998
CPU user time (s): 0.003999
CPU system time (s): 0.000999
CPU usage (%): 50.8905
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node047 at 2010-06-15 18:17:14
IDJOB=2657206
IDBENCH=2933
IDSOLVER=1162
FILE ID=node047/2657206-1276618634
PBS_JOBID= 11172321
Free space on /tmp= 62540 MiB

SOLVER NAME= bsolo 3.2 Card
BENCH NAME= PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/bounded_golomb_rulers/normalized-bogr_4.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l2 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2657206-1276618634/watcher-2657206-1276618634 -o /tmp/evaluation-result-2657206-1276618634/solver-2657206-1276618634 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l2 HOME/instance-2657206-1276618634.opb

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

MD5SUM BENCH= e07d1b5f59078d7e9ac49c5c9d354a5d
RANDOM SEED=1209095609

node047.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.244
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.48
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.244
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.44
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1764648 kB
Buffers:         37392 kB
Cached:         133696 kB
SwapCached:          0 kB
Active:         113224 kB
Inactive:       117124 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1764648 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            4000 kB
Writeback:           0 kB
AnonPages:       59272 kB
Mapped:          15424 kB
Slab:            42248 kB
PageTables:       4068 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181572 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62540 MiB
End job on node047 at 2010-06-15 18:17:14