Trace number 2681679

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
PB/CT 0.1 fixedOPT-13 0.975851 0.976339

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/mis/normalized-mis_50_10_5.opb
MD5SUM9d121e9bd43af8a355e8c7cd150cfe9a
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark-13
Best CPU time to get the best result obtained on this benchmark0.32095
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -13
Optimality of the best value was proved YES
Number of variables50
Total number of constraints50
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints50
Minimum length of a constraint10
Maximum length of a constraint17
Number of terms in the objective function 50
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 50
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 50
Number of bits of the biggest sum of numbers6
Number of products (including duplicates)606
Sum of products size (including duplicates)1212
Number of different products303
Sum of products size606

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 PB/CT 0.1.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 353/0 clauses 303/0 units 0
0.00/0.00	c vars 50
0.00/0.00	c objective 50 + -50
0.09/0.11	c 0.103984 11.9492 0 305
0.09/0.11	o 0
0.09/0.11	c 0.105983 12.2734 0 562
0.09/0.11	o -1
0.09/0.12	c 0.109983 12.2734 0 831
0.09/0.12	o -2
0.09/0.12	c 0.111982 12.2734 1 1036
0.09/0.12	o -3
0.19/0.27	c 0.253961 12.2734 1 2095
0.19/0.27	o -10
0.29/0.31	c 0.294955 12.2734 88 2453
0.29/0.31	o -11
0.29/0.33	c 0.314952 12.2734 198 2620
0.29/0.33	o -12
0.69/0.72	c 0.692894 12.6523 2985 5614
0.69/0.72	o -13
0.89/0.93	c 0.895863 12.6523 1465 7103
0.89/0.93	s OPTIMUM FOUND
0.89/0.93	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 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 x39 x40 x41 -x42 x43 -x44 x45 -x46 -x47 -x48 x49 x50

Verifier Data

OK	-13

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2681679-1277502150/watcher-2681679-1277502150 -o /tmp/evaluation-result-2681679-1277502150/solver-2681679-1277502150 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2681679-1277502150.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: 0.92 0.98 0.99 3/106 30633
/proc/meminfo: memFree=1857188/2059040 swapFree=4139192/4192956
[pid=30633] ppid=30631 vsize=3180 CPUtime=0
/proc/30633/stat : 30633 (pbct) R 30631 30633 30025 0 -1 4202496 487 0 0 0 0 0 0 0 20 0 1 0 91510159 3256320 407 1992294400 134512640 136421960 4293662272 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30633/statm: 795 409 190 467 0 326 0

[startup+0.0158229 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 30633
/proc/meminfo: memFree=1857188/2059040 swapFree=4139192/4192956
[pid=30633] ppid=30631 vsize=3972 CPUtime=0.01
/proc/30633/stat : 30633 (pbct) R 30631 30633 30025 0 -1 4202496 713 0 0 0 1 0 0 0 20 0 1 0 91510159 4067328 633 1992294400 134512640 136421960 4293662272 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30633/statm: 993 634 194 467 0 524 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 3972

[startup+0.100833 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 30633
/proc/meminfo: memFree=1857188/2059040 swapFree=4139192/4192956
[pid=30633] ppid=30631 vsize=11392 CPUtime=0.09
/proc/30633/stat : 30633 (pbct) R 30631 30633 30025 0 -1 4202496 2506 0 0 0 9 0 0 0 20 0 1 0 91510159 11665408 2426 1992294400 134512640 136421960 4293662272 18446744073709551615 135830543 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30633/statm: 2848 2435 204 467 0 2379 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11392

[startup+0.300856 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 30633
/proc/meminfo: memFree=1857188/2059040 swapFree=4139192/4192956
[pid=30633] ppid=30631 vsize=12564 CPUtime=0.29
/proc/30633/stat : 30633 (pbct) R 30631 30633 30025 0 -1 4202496 2815 0 0 0 28 1 0 0 20 0 1 0 91510159 12865536 2730 1992294400 134512640 136421960 4293662272 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30633/statm: 3141 2730 237 467 0 2672 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 12564

[startup+0.700903 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 30633
/proc/meminfo: memFree=1857188/2059040 swapFree=4139192/4192956
[pid=30633] ppid=30631 vsize=12952 CPUtime=0.69
/proc/30633/stat : 30633 (pbct) R 30631 30633 30025 0 -1 4202496 2896 0 0 0 67 2 0 0 21 0 1 0 91510159 13262848 2809 1992294400 134512640 136421960 4293662272 18446744073709551615 134643031 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30633/statm: 3238 2809 237 467 0 2769 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 12952

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

[startup+0.900927 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 30633
/proc/meminfo: memFree=1857188/2059040 swapFree=4139192/4192956
[pid=30633] ppid=30631 vsize=12952 CPUtime=0.89
/proc/30633/stat : 30633 (pbct) R 30631 30633 30025 0 -1 4202496 2904 0 0 0 85 4 0 0 21 0 1 0 91510159 13262848 2816 1992294400 134512640 136421960 4293662272 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30633/statm: 3238 2816 237 467 0 2769 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 12952

Child status: 0
Real time (s): 0.976339
CPU time (s): 0.975851
CPU user time (s): 0.931858
CPU system time (s): 0.043993
CPU usage (%): 99.95
Max. virtual memory (cumulated for all children) (KiB): 12952

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.931858
system time used= 0.043993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2912
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= 2

runsolver used 0.007998 second user time and 0.014997 second system time

The end

Launcher Data

Begin job on node033 at 2010-06-25 23:42:30
IDJOB=2681679
IDBENCH=48168
IDSOLVER=1192
FILE ID=node033/2681679-1277502150
PBS_JOBID= 11190582
Free space on /tmp= 62304 MiB

SOLVER NAME= PB/CT 0.1 fixed
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/manquinho/mis/normalized-mis_50_10_5.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2681679-1277502150/watcher-2681679-1277502150 -o /tmp/evaluation-result-2681679-1277502150/solver-2681679-1277502150 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2681679-1277502150.opb

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

MD5SUM BENCH= 9d121e9bd43af8a355e8c7cd150cfe9a
RANDOM SEED=1723598155

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1857708 kB
Buffers:         26640 kB
Cached:          78924 kB
SwapCached:       5984 kB
Active:          68820 kB
Inactive:        49456 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1857708 kB
SwapTotal:     4192956 kB
SwapFree:      4139192 kB
Dirty:            1884 kB
Writeback:           0 kB
AnonPages:       11408 kB
Mapped:          11908 kB
Slab:            61032 kB
PageTables:       4160 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181700 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= 62304 MiB
End job on node033 at 2010-06-25 23:42:31