Trace number 363655

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
Pueblo 1.4OPT20 0.164974 0.167567

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/ttp/normalized-circ4_3.opb
MD5SUM6b7a318661ea9d7a03f30f3e64874f46
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark20
Best CPU time to get the best result obtained on this benchmark0.164974
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 20
Optimality of the best value was proved YES
Number of variables144
Total number of constraints704
Number of constraints which are clauses464
Number of constraints which are cardinality constraints (but not clauses)96
Number of constraints which are nor clauses,nor cardinality constraints144
Minimum length of a constraint2
Maximum length of a constraint12
Number of terms in the objective function 48
Biggest coefficient in the objective function 2
Number of bits for the biggest coefficient in the objective function 2
Sum of the numbers in the objective function 64
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 8
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 64
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

Solver Data (download as text)

0.00/0.00	c Pueblo version 1.4 (September 2005)
0.00/0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00/0.00	c  by Hossein Sheini
0.00/0.01	c starting to Solve
0.00/0.01	c #variables read: 144 - #constraints read: 765
0.00/0.01	o 20
0.09/0.16	c optimum objective found = 20
0.09/0.16	c total time              : 0.16 s
0.09/0.16	s OPTIMUM FOUND
0.09/0.16	v -x97 -x98 x99 -x100 x101 -x102 x103 -x104 -x105 -x106 x107 -x108 -x109 -x110 x111 x112 -x113 -x114 -x115 x116 -x117 -x118 -x119
0.09/0.16	v x120 -x121 x122 -x123 -x124 x125 -x126 -x127 x128 x129 x130 -x131 -x132 -x133 -x134 x135 x136 -x137 -x138 -x139 x140 -x141
0.09/0.16	v -x142 -x143 x144 -x2 -x18 -x34 x50 -x66 -x82 -x3 -x19 -x35 -x51 x67 -x83 -x4 -x20 x36 -x52 -x68 -x84 x5 -x21 -x37 -x53 -x69 -x85
0.09/0.16	v -x7 -x23 x39 -x55 -x71 -x87 -x8 x24 -x40 -x56 -x72 -x88 -x9 x25 -x41 -x57 -x73 -x89 -x10 -x26 -x42 -x58 -x74 x90 x12 -x28 -x44 -x60
0.09/0.16	v -x76 -x92 -x13 -x29 -x45 -x61 -x77 x93 -x14 -x30 -x46 -x62 x78 -x94 -x15 -x31 -x47 x63 -x79 -x95 -x6 -x22 -x38 x54 x70 x86 -x11
0.09/0.16	v -x27 x43 x59 x75 -x91 x16 x32 x48 -x64 -x80 -x96 x1 x17 -x33 -x49 -x65 x81

Verifier Data (download as text)

OK	20

Conversion Script Data (download as text)

/tmp/evaluation/363655-1177030264/instance-363655-1177030264.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/node29/watcher-363655-1177030264 -o ROOT/results/node29/solver-363655-1177030264 -C 1800 -W 3600 -M 1800 --output-limit 1,15 Pueblo /tmp/evaluation/363655-1177030264/instance-363655-1177030264.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: 1.02 1.00 1.00 3/77 6642
/proc/meminfo: memFree=1786488/2055920 swapFree=4146452/4192956
[pid=6642] ppid=6640 vsize=2552 CPUtime=0
/proc/6642/stat : 6642 (Pueblo) R 6640 6642 5380 0 -1 4194304 266 0 0 0 0 0 0 0 18 0 1 0 150942171 2613248 236 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4595415 0 0 4096 0 0 0 0 17 1 0 0
/proc/6642/statm: 638 236 199 16 0 77 0

[startup+0.0309491 s]
/proc/loadavg: 1.02 1.00 1.00 3/77 6642
/proc/meminfo: memFree=1786488/2055920 swapFree=4146452/4192956
[pid=6642] ppid=6640 vsize=2688 CPUtime=0.02
/proc/6642/stat : 6642 (Pueblo) R 6640 6642 5380 0 -1 4194304 318 0 0 0 2 0 0 0 18 0 1 0 150942171 2752512 288 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/6642/statm: 672 288 205 16 0 111 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 2688

[startup+0.101955 s]
/proc/loadavg: 1.02 1.00 1.00 3/77 6642
/proc/meminfo: memFree=1786488/2055920 swapFree=4146452/4192956
[pid=6642] ppid=6640 vsize=2816 CPUtime=0.09
/proc/6642/stat : 6642 (Pueblo) R 6640 6642 5380 0 -1 4194304 329 0 0 0 9 0 0 0 18 0 1 0 150942171 2883584 299 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/6642/statm: 704 299 205 16 0 143 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2816

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

Child status: 30
Real time (s): 0.167567
CPU time (s): 0.164974
CPU user time (s): 0.160975
CPU system time (s): 0.003999
CPU usage (%): 98.4526
Max. virtual memory (cumulated for all children) (KiB): 2816

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node29 on Fri Apr 20 00:51:04 UTC 2007

IDJOB= 363655
IDBENCH= 2012
IDSOLVER= 165
FILE ID= node29/363655-1177030264

PBS_JOBID= 4640094

Free space on /tmp= 66466 MiB

SOLVER NAME= Pueblo 1.4
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/ttp/normalized-circ4_3.opb
COMMAND LINE= Pueblo /tmp/evaluation/363655-1177030264/instance-363655-1177030264.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node29/convwatcher-363655-1177030264 -o ROOT/results/node29/conversion-363655-1177030264 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/363655-1177030264/instance-363655-1177030264.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node29/watcher-363655-1177030264 -o ROOT/results/node29/solver-363655-1177030264 -C 1800 -W 3600 -M 1800 --output-limit 1,15  Pueblo /tmp/evaluation/363655-1177030264/instance-363655-1177030264.opb

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  6b7a318661ea9d7a03f30f3e64874f46

RANDOM SEED= 808373007

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node29.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.224
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.224
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:       1787024 kB
Buffers:         50624 kB
Cached:         134468 kB
SwapCached:      11360 kB
Active:         107772 kB
Inactive:       108044 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1787024 kB
SwapTotal:     4192956 kB
SwapFree:      4146452 kB
Dirty:            2524 kB
Writeback:           0 kB
Mapped:          30004 kB
Slab:            38524 kB
Committed_AS:  2535492 kB
PageTables:       1872 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= 66466 MiB

End job on node29 on Fri Apr 20 00:51:05 UTC 2007