Trace number 366907

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
PB-clasp 2007-04-10OPT11 0.147976 0.164814

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.06	o 18
0.00/0.08	o 14
0.06/0.11	o 12
0.06/0.13	o 11
0.06/0.16	s OPTIMUM FOUND
0.06/0.16	v x1 x15 x20 x21 x25 x26 x27 x28 x29 x30 x31 x32 x33 x34 x35 x36 x37 x38 x39 x40 x41 x42 x43 x44 x45 x46 x47 x48 x49 x51 x52 x55 x56 x57
0.06/0.16	v x58 x59 x60 x61 x62 x63 x64 x66 x69 x70 x75

Verifier Data (download as text)

OK	11

Conversion Script Data (download as text)

/tmp/evaluation/366907-1177068021/instance-366907-1177068021.opb is already a linear file

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-366907-1177068021 -o ROOT/results/node2/solver-366907-1177068021 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-366907-1177068021.opb /tmp/evaluation/366907-1177068021/temp 

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.77 0.94 0.98 3/77 31937
/proc/meminfo: memFree=1762000/2055920 swapFree=4149072/4192956
[pid=31937] ppid=31935 vsize=12268 CPUtime=0
/proc/31937/stat : 31937 (pbclasp) R 31935 31937 31749 0 -1 4194304 411 0 0 0 0 0 0 0 18 0 1 0 182839888 12562432 377 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206381159137 0 0 4224 0 0 0 0 17 1 0 0
/proc/31937/statm: 3067 377 286 3 0 167 0

[startup+0.0969929 s]
/proc/loadavg: 0.77 0.94 0.98 3/77 31937
/proc/meminfo: memFree=1762000/2055920 swapFree=4149072/4192956
[pid=31937] ppid=31935 vsize=12400 CPUtime=0.06
/proc/31937/stat : 31937 (pbclasp) R 31935 31937 31749 0 -1 4194304 799 5015 0 0 0 0 4 2 16 0 1 0 182839888 12697600 462 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206381312671 0 0 4224 16384 0 0 0 17 1 0 0
/proc/31937/statm: 3100 462 343 3 0 200 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 12400

[startup+0.101988 s]
/proc/loadavg: 0.77 0.94 0.98 3/77 31937
/proc/meminfo: memFree=1762000/2055920 swapFree=4149072/4192956
[pid=31937] ppid=31935 vsize=12400 CPUtime=0.06
/proc/31937/stat : 31937 (pbclasp) S 31935 31937 31749 0 -1 4194304 806 5015 0 0 0 0 4 2 16 0 1 0 182839888 12697600 462 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206390214548 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/31937/statm: 3100 462 343 3 0 200 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 12400

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

Child status: 0
Real time (s): 0.164814
CPU time (s): 0.147976
CPU user time (s): 0.078987
CPU system time (s): 0.068989
CPU usage (%): 89.7836
Max. virtual memory (cumulated for all children) (KiB): 12400

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

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

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

IDJOB= 366907
IDBENCH= 2941
IDSOLVER= 167
FILE ID= node2/366907-1177068021

PBS_JOBID= 4640265

Free space on /tmp= 66401 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/bounded_golomb_rulers/normalized-bogr_5.opb
COMMAND LINE= pbclasp instance-366907-1177068021.opb /tmp/evaluation/366907-1177068021/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node2/convwatcher-366907-1177068021 -o ROOT/results/node2/conversion-366907-1177068021 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/366907-1177068021/instance-366907-1177068021.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-366907-1177068021 -o ROOT/results/node2/solver-366907-1177068021 -C 1800 -W 3600 -M 1800 --output-limit 1,15  pbclasp instance-366907-1177068021.opb /tmp/evaluation/366907-1177068021/temp

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  fd5650da6eaa0e3a50dfb52821ac86aa

RANDOM SEED= 557742609

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:       1762472 kB
Buffers:         71028 kB
Cached:         143852 kB
SwapCached:      12240 kB
Active:         134264 kB
Inactive:       105796 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1762472 kB
SwapTotal:     4192956 kB
SwapFree:      4149072 kB
Dirty:             728 kB
Writeback:           0 kB
Mapped:          30024 kB
Slab:            38860 kB
Committed_AS:  8184704 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= 66401 MiB

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