Trace number 2669168

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.1Wrong Opt.62567 0.266958 0.266722

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/mps-v2-20-10/
MIPLIB/miplib/normalized-mps-v2-20-10-p0040.opb
MD5SUMab21eb5817d07a398a94670d7815d5fb
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark62027
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 62027
Optimality of the best value was proved YES
Number of variables40
Total number of constraints23
Number of constraints which are clauses10
Number of constraints which are cardinality constraints (but not clauses)10
Number of constraints which are nor clauses,nor cardinality constraints3
Minimum length of a constraint4
Maximum length of a constraint10
Number of terms in the objective function 40
Biggest coefficient in the objective function 8161
Number of bits for the biggest coefficient in the objective function 13
Sum of the numbers in the objective function 265332
Number of bits of the sum of numbers in the objective function 19
Biggest number in a constraint 8161
Number of bits of the biggest number in a constraint 13
Biggest sum of numbers in a constraint 265332
Number of bits of the biggest sum of numbers19
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 PB/CT 0.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 12/0 clauses 11/0 units 0
0.00/0.00	c vars 40
0.00/0.00	c objective 40 + 0
0.00/0.01	c 0.007998 3.69141 1 47
0.00/0.01	o 63994
0.00/0.01	c 0.007998 3.69141 2 61
0.00/0.01	o 63687
0.00/0.01	c 0.008998 3.69141 2 72
0.00/0.01	o 63670
0.00/0.01	c 0.008998 3.69141 8 90
0.00/0.01	o 63275
0.00/0.01	c 0.008998 3.69141 12 107
0.00/0.01	o 63184
0.00/0.02	c 0.016997 3.69141 87 271
0.00/0.02	o 62861
0.00/0.04	c 0.035994 3.69141 136 831
0.00/0.04	o 62844
0.00/0.05	c 0.040993 3.69141 107 986
0.00/0.05	o 62770
0.05/0.07	c 0.057991 3.69141 175 1408
0.05/0.07	o 62768
0.05/0.09	c 0.073988 3.69141 164 1899
0.05/0.09	o 62602
0.09/0.11	c 0.092985 3.69141 169 2375
0.09/0.11	o 62592
0.09/0.18	c 0.142978 3.69141 111 3737
0.09/0.18	o 62567
0.19/0.26	c 0.211967 3.69141 1 5529
0.19/0.26	s OPTIMUM FOUND
0.19/0.26	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

Verifier Data

OK	62567

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2669168-1276437410/watcher-2669168-1276437410 -o /tmp/evaluation-result-2669168-1276437410/solver-2669168-1276437410 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669168-1276437410.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.99 0.97 0.99 3/106 23176
/proc/meminfo: memFree=1870472/2059040 swapFree=4140228/4192956
[pid=23176] ppid=23174 vsize=3644 CPUtime=0
/proc/23176/stat : 23176 (pbct) R 23174 23176 21207 0 -1 4202496 618 0 0 0 0 0 0 0 20 0 1 0 19342757 3731456 540 1992294400 134512640 136485738 4294931376 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23176/statm: 911 540 210 482 0 427 0

[startup+0.0577359 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23176
/proc/meminfo: memFree=1870472/2059040 swapFree=4140228/4192956
[pid=23176] ppid=23174 vsize=3776 CPUtime=0.05
/proc/23176/stat : 23176 (pbct) R 23174 23176 21207 0 -1 4202496 688 0 0 0 4 1 0 0 20 0 1 0 19342757 3866624 602 1992294400 134512640 136485738 4294931376 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23176/statm: 944 602 243 482 0 460 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 3776

[startup+0.100739 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23176
/proc/meminfo: memFree=1870472/2059040 swapFree=4140228/4192956
[pid=23176] ppid=23174 vsize=3776 CPUtime=0.09
/proc/23176/stat : 23176 (pbct) R 23174 23176 21207 0 -1 4202496 692 0 0 0 7 2 0 0 20 0 1 0 19342757 3866624 604 1992294400 134512640 136485738 4294931376 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23176/statm: 944 604 243 482 0 460 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3776

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

[startup+0.200751 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23176
/proc/meminfo: memFree=1870472/2059040 swapFree=4140228/4192956
[pid=23176] ppid=23174 vsize=3776 CPUtime=0.19
/proc/23176/stat : 23176 (pbct) R 23174 23176 21207 0 -1 4202496 696 0 0 0 15 4 0 0 20 0 1 0 19342757 3866624 606 1992294400 134512640 136485738 4294931376 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23176/statm: 944 606 243 482 0 460 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 3776

Child status: 0
Real time (s): 0.266722
CPU time (s): 0.266958
CPU user time (s): 0.212967
CPU system time (s): 0.053991
CPU usage (%): 100.088
Max. virtual memory (cumulated for all children) (KiB): 3776

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

runsolver used 0.004999 second user time and 0.007998 second system time

The end

Launcher Data

Begin job on node009 at 2010-06-13 15:56:50
IDJOB=2669168
IDBENCH=1867
IDSOLVER=1170
FILE ID=node009/2669168-1276437410
PBS_JOBID= 11173311
Free space on /tmp= 62444 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-p0040.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669168-1276437410/watcher-2669168-1276437410 -o /tmp/evaluation-result-2669168-1276437410/solver-2669168-1276437410 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669168-1276437410.opb

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

MD5SUM BENCH= ab21eb5817d07a398a94670d7815d5fb
RANDOM SEED=1924482487

node009.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.199
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.39
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.199
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:       1871000 kB
Buffers:          6588 kB
Cached:         104088 kB
SwapCached:       5328 kB
Active:          23308 kB
Inactive:        99412 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1871000 kB
SwapTotal:     4192956 kB
SwapFree:      4140228 kB
Dirty:            1988 kB
Writeback:           0 kB
AnonPages:       10932 kB
Mapped:          12828 kB
Slab:            43468 kB
PageTables:       4020 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   179756 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= 62440 MiB
End job on node009 at 2010-06-13 15:56:50