Trace number 373219

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
minisat+ 1.14OPT33 0.027995 0.0295189

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/aksoy/
area_partials/normalized-fir07_area_partials.opb
MD5SUM7ce2ce9765bc91d2f0a2aa267ffcb923
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark33
Best CPU time to get the best result obtained on this benchmark0.013997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 33
Optimality of the best value was proved YES
Number of variables190
Total number of constraints419
Number of constraints which are clauses419
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint30
Number of terms in the objective function 92
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 92
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 92
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

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 Parsing PB file...
0.00/0.01	c Converting 389 PB-constraints to clauses...
0.00/0.01	c   -- Unit propagations: (none)
0.00/0.01	c   -- Detecting intervals from adjacent constraints: (none)
0.00/0.01	c   -- Clauses(.)/Splits(s): .....................................................................................................................................................................................................................................................................................................................................................................................................
0.00/0.01	c ==================================[MINISAT+]==================================
0.00/0.01	c | Conflicts | Original         | Learnt                           | Progress |
0.00/0.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00/0.01	c ==============================================================================
0.00/0.01	c |         0 |     389     1036 |     129       0        0     nan |  0.000 % |
0.00/0.01	c ==============================================================================
0.00/0.01	c Found solution: 34
0.00/0.01	o 34
0.00/0.01	c ---[   0]---> BDD-cost:  235
0.00/0.01	c ==================================[MINISAT+]==================================
0.00/0.01	c | Conflicts | Original         | Learnt                           | Progress |
0.00/0.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00/0.01	c ==============================================================================
0.00/0.01	c |         1 |    1030     2843 |     343       1       18    18.0 |  0.000 % |
0.00/0.02	c ==============================================================================
0.00/0.02	c Found solution: 33
0.00/0.02	o 33
0.00/0.02	c ---[   0]---> BDD-cost:    3
0.00/0.02	c ==================================[MINISAT+]==================================
0.00/0.02	c | Conflicts | Original         | Learnt                           | Progress |
0.00/0.02	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00/0.02	c ==============================================================================
0.00/0.02	c |        47 |    1038     2865 |     346      47      718    15.3 |  0.000 % |
0.00/0.02	c ==============================================================================
0.00/0.02	c Optimal solution: 33
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	v x1 x2 x3 x4 x5 x7 x8 x9 x10 x11 x12 x13 x14 x15 x16 x17 x18 x32 x33 x41 x42 x43 x44 x52 x53 x54 x55 x56 x57 x65 -x66 -x67 x68 -x69 -x71
0.00/0.02	v -x73 -x74 -x75 -x77 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x95 -x100 -x101 -x102 -x104 -x107 -x109 -x110 -x111
0.00/0.02	v -x112 -x113 -x114 -x116 x120 -x122 -x123 -x124 -x125 -x126 -x127 -x128 -x130 -x134 x136 -x139 -x143 -x145 -x147 -x149 -x152
0.00/0.02	v -x157 -x159 -x161 -x163 -x165 -x168 -x171 -x175 -x178 -x181 -x186 -x189 -x6 -x70 -x76 -x19 -x20 -x21 -x22 -x94 -x23 -x24 -x25
0.00/0.02	v -x26 -x27 x119 -x28 -x29 -x30 -x31 -x34 -x115 -x35 x36 -x138 -x144 -x37 -x38 -x39 -x151 -x40 x45 -x46 -x47 -x156 -x48 -x49 -x164
0.00/0.02	v -x50 -x51 -x170 -x58 -x174 -x177 -x180 -x185 -x59 -x60 -x61 -x62 -x188 -x63 -x64 x72 -x78 -x79 -x80 -x81 -x129 -x82 x96 -x97
0.00/0.02	v -x98 -x106 -x99 -x103 x105 -x108 x117 -x118 x121 -x131 -x132 -x133 x135 x137 x140 -x141 -x148 -x142 x146 -x150 -x153 -x154
0.00/0.02	v -x155 -x158 -x167 -x160 -x162 x166 x169 -x172 -x173 -x176 x179 x182 -x183 -x184 x187 x190
0.00/0.02	c _______________________________________________________________________________
0.00/0.02	c 
0.00/0.02	c restarts              : 3
0.00/0.02	c conflicts             : 73             (2808 /sec)
0.00/0.02	c decisions             : 222            (8540 /sec)
0.00/0.02	c propagations          : 0              (0 /sec)
0.00/0.02	c inspects              : 0              (0 /sec)
0.00/0.02	c CPU time              : 0.025996 s
0.00/0.02	c _______________________________________________________________________________

Verifier Data (download as text)

OK	33

Conversion Script Data (download as text)

/tmp/evaluation/373219-1177365055/instance-373219-1177365055.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node63/watcher-373219-1177365055 -o ROOT/results/node63/solver-373219-1177365055 -C 1800 -W 3600 -M 1800 --output-limit 1,15 /tmp/evaluation/373219-1177365055/minisat+ /tmp/evaluation/373219-1177365055/instance-373219-1177365055.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: 0.33 0.78 0.85 3/64 24902
/proc/meminfo: memFree=1676932/2055920 swapFree=4182948/4192956
[pid=24902] ppid=24900 vsize=1048 CPUtime=0
/proc/24902/stat : 24902 (minisat+) R 24900 24902 24001 0 -1 4194304 115 0 0 0 0 0 0 0 18 0 1 0 212495438 1073152 102 18446744073709551615 134512640 135395479 4294956560 18446744073709551615 134618678 0 0 4096 16386 0 0 0 17 1 0 0
/proc/24902/statm: 262 102 75 215 0 44 0

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

Child status: 30
Real time (s): 0.0295189
CPU time (s): 0.027995
CPU user time (s): 0.025996
CPU system time (s): 0.001999
CPU usage (%): 94.8376
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node63 on Mon Apr 23 21:50:55 UTC 2007

IDJOB= 373219
IDBENCH= 25028
IDSOLVER= 156
FILE ID= node63/373219-1177365055

PBS_JOBID= 4675151

Free space on /tmp= 66472 MiB

SOLVER NAME= minisat+ 1.14
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/aksoy/area_partials/normalized-fir07_area_partials.opb
COMMAND LINE= /tmp/evaluation/373219-1177365055/minisat+ /tmp/evaluation/373219-1177365055/instance-373219-1177365055.opb            
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node63/convwatcher-373219-1177365055 -o ROOT/results/node63/conversion-373219-1177365055 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/373219-1177365055/instance-373219-1177365055.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node63/watcher-373219-1177365055 -o ROOT/results/node63/solver-373219-1177365055 -C 1800 -W 3600 -M 1800 --output-limit 1,15  /tmp/evaluation/373219-1177365055/minisat+ /tmp/evaluation/373219-1177365055/instance-373219-1177365055.opb            

META MD5SUM SOLVER= e46aded85e5f265b61da9cdcce06370e
MD5SUM BENCH=  7ce2ce9765bc91d2f0a2aa267ffcb923

RANDOM SEED= 567911104

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node63.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.232
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.232
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:       1677340 kB
Buffers:         45196 kB
Cached:         254776 kB
SwapCached:       4056 kB
Active:          51960 kB
Inactive:       258160 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1677340 kB
SwapTotal:     4192956 kB
SwapFree:      4182948 kB
Dirty:            2412 kB
Writeback:           0 kB
Mapped:          16032 kB
Slab:            54420 kB
Committed_AS:  2185344 kB
PageTables:       1464 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= 66472 MiB

End job on node63 on Mon Apr 23 21:50:55 UTC 2007