Trace number 366903

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
bsolo 3.0.16OPT11 0.032994 0.0342651

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
bounded_golomb_rulers/normalized-bogr_5.opb
MD5SUMfd5650da6eaa0e3a50dfb52821ac86aa
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark11
Best CPU time to get the best result obtained on this benchmark0.007998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 11
Optimality of the best value was proved YES
Number of variables75
Total number of constraints105
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 constraints104
Minimum length of a constraint1
Maximum length of a constraint21
Number of terms in the objective function 5
Biggest coefficient in the objective function 10
Number of bits for the biggest coefficient in the objective function 4
Sum of the numbers in the objective function 25
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 34
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 177
Number of bits of the biggest sum of numbers8
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.00/0.00	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.00	c Developed by Vasco Manquinho 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 Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/366903-1177068017/instance-366903-1177068017.opb
0.00/0.00	c File size is 11969 bytes.
0.00/0.00	c Highest Coefficient sum: 177
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.003 s
0.00/0.00	c Var: 75 Constr: 105 1/0/104 Lit: 1580 Watch. Lit: 498
0.00/0.00	c Obj. Vars: 5 (6.66667 % of total variables)
0.00/0.00	c Pre-processing Time: 0.005 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     74      104     1579   15      854    3158      0      0 0.01
0.00/0.00	c Switching off LPR mode.
0.00/0.03	c      100     74      204     2874   14     1282    3474    100   6666 0.01
0.00/0.03	o 14	0.026
0.00/0.03	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.03	c      206     74      311     4322   13     1505    3166    207   7923 0.03
0.00/0.03	o 12	0.027
0.00/0.03	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.03	c      211     72      317     4372   13     1521    3164    213   7814 0.03
0.00/0.03	o 11	0.028
0.00/0.03	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.03	c      236     67      343     4652   13     1553    3158    239   8428 0.03
0.00/0.03	v x1 -x2 -x3 -x4 x75 x15 -x16 -x17 -x18 -x19 x20 x21 -x22 -x23 -x24 -x74 -x5 -x6 -x7 -x8 -x9 -x73 -x72 -x71 x70 x69 -x10 -x11 -x12 -x13
0.00/0.03	v -x14 -x68 -x67 x66 -x65 x64 x63 x62 x61 x60 x59 x58 x57 x56 x55 -x54 -x53 x52 x51 -x50 x49 x48 x47 x46 x45 x44 x43 x42 x41 x40 x39 x38
0.00/0.03	v x37 x36 x35 x34 x33 x32 x31 x30 x29 x28 x27 x26 x25
0.00/0.03	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.03	c    4      237     50      411      344     4653    240   8172 0.03
0.00/0.03	c Objective: 11
0.00/0.03	s OPTIMUM FOUND
0.00/0.03	c Total time: 0.029 s

Verifier Data (download as text)

OK	11

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node2/watcher-366903-1177068017 -o ROOT/results/node2/solver-366903-1177068017 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/366903-1177068017/instance-366903-1177068017.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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.84 0.95 0.98 3/77 31809
/proc/meminfo: memFree=1758256/2055920 swapFree=4149072/4192956
[pid=31809] ppid=31807 vsize=19560 CPUtime=0
/proc/31809/stat : 31809 (bsolo3.0.16) R 31807 31809 31749 0 -1 4194304 366 0 0 0 0 0 0 0 18 0 1 0 182839443 20029440 334 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 10970747 0 0 4096 16384 0 0 0 17 1 0 0
/proc/31809/statm: 4890 334 282 324 0 3956 0

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

Child status: 0
Real time (s): 0.0342651
CPU time (s): 0.032994
CPU user time (s): 0.029995
CPU system time (s): 0.002999
CPU usage (%): 96.2904
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node2 on Fri Apr 20 11:20:17 UTC 2007

IDJOB= 366903
IDBENCH= 2941
IDSOLVER= 163
FILE ID= node2/366903-1177068017

PBS_JOBID= 4640265

Free space on /tmp= 66397 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/bounded_golomb_rulers/normalized-bogr_5.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/366903-1177068017/instance-366903-1177068017.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-366903-1177068017 -o ROOT/results/node2/solver-366903-1177068017 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/366903-1177068017/instance-366903-1177068017.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  fd5650da6eaa0e3a50dfb52821ac86aa

RANDOM SEED= 451189581

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

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

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1758792 kB
Buffers:         71008 kB
Cached:         147748 kB
SwapCached:      12240 kB
Active:         138080 kB
Inactive:       105764 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1758792 kB
SwapTotal:     4192956 kB
SwapFree:      4149072 kB
Dirty:            4576 kB
Writeback:           0 kB
Mapped:          29964 kB
Slab:            38776 kB
Committed_AS:  8184544 kB
PageTables:       1860 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= 66397 MiB

End job on node2 on Fri Apr 20 11:20:17 UTC 2007