Trace number 429150

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.4OPT2 0.036993 0.037623

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=5-P0=31-P1=23-P2=2-P3=17-P4=17-B.opb
MD5SUMab5c167d631c36380726b7ea7a7cf75a
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2
Best CPU time to get the best result obtained on this benchmark0.034994
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of variables60
Total number of constraints9
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 constraints9
Minimum length of a constraint5
Maximum length of a constraint35
Number of terms in the objective function 5
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 31
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 512
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 1984
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)100
Sum of products size (including duplicates)200
Number of different products100
Sum of products size200

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 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.00	c starting to Solve
0.00/0.00	c #variables read: 160 - #constraints read: 214
0.00/0.01	o 17
0.00/0.01	o 3
0.00/0.03	o 2
0.00/0.03	c optimum objective found = 2
0.00/0.03	c total time              : 0.03 s
0.00/0.03	s OPTIMUM FOUND
0.00/0.03	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 -x61 x62 -x63 -x64 -x65
0.00/0.03	v -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x26 x27 -x28 -x29 x30 -x41
0.00/0.03	v -x42 -x43 -x44 -x45 -x86 x87 -x88 -x89 x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 x102 -x103 -x104 x105 -x106
0.00/0.03	v -x107 -x108 -x109 -x110 -x31 x32 -x33 -x34 -x35 x46 -x47 x48 -x49 -x50 -x111 x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119
0.00/0.03	v -x120 -x121 -x122 -x123 -x124 -x125 -x126 -x127 -x128 -x129 -x130 -x131 x132 -x133 -x134 -x135 -x36 x37 -x38 -x39 -x40 x51
0.00/0.03	v -x52 -x53 -x54 -x55 -x136 x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148 -x149 -x150 -x151 x152 -x153
0.00/0.03	v -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x56 -x57 -x58 -x59 -x60

Verifier Data (download as text)

OK	2

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/429150-1177981238/instance-429150-1177981238.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node23/watcher-429150-1177981238 -o ROOT/results/node23/solver-429150-1177981238 -C 1800 -W 3600 -M 1800 --output-limit 1,15 Pueblo /tmp/evaluation/429150-1177981238/instance-429150-1177981238.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.15 1.03 0.87 3/77 6175
/proc/meminfo: memFree=1904320/2055920 swapFree=4169104/4192956
[pid=6175] ppid=6173 vsize=2552 CPUtime=0
/proc/6175/stat : 6175 (Pueblo) R 6173 6175 14988 0 -1 4194304 265 0 0 0 0 0 0 0 18 0 1 0 246040945 2613248 236 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 134542840 0 0 4096 0 0 0 0 17 1 0 0
/proc/6175/statm: 638 236 199 16 0 77 0

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

Child status: 30
Real time (s): 0.037623
CPU time (s): 0.036993
CPU user time (s): 0.032994
CPU system time (s): 0.003999
CPU usage (%): 98.3255
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.032994
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= 305
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= 2

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node23 on Tue May  1 01:00:38 UTC 2007

IDJOB= 429150
IDBENCH= 47888
IDSOLVER= 165
FILE ID= node23/429150-1177981238

PBS_JOBID= 4728174

Free space on /tmp= 66562 MiB

SOLVER NAME= Pueblo 1.4
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=5-P0=31-P1=23-P2=2-P3=17-P4=17-B.opb
COMMAND LINE= Pueblo /tmp/evaluation/429150-1177981238/instance-429150-1177981238.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node23/convwatcher-429150-1177981238 -o ROOT/results/node23/conversion-429150-1177981238 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/429150-1177981238/instance-429150-1177981238.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  ab5c167d631c36380726b7ea7a7cf75a

RANDOM SEED= 986811604

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node23.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.276
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.276
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:       1904664 kB
Buffers:         16452 kB
Cached:          46176 kB
SwapCached:       2176 kB
Active:          59492 kB
Inactive:        25648 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1904664 kB
SwapTotal:     4192956 kB
SwapFree:      4169104 kB
Dirty:            2520 kB
Writeback:           0 kB
Mapped:          30168 kB
Slab:            51564 kB
Committed_AS:  3035492 kB
PageTables:       1796 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= 66562 MiB

End job on node23 on Tue May  1 01:00:38 UTC 2007