File: factorize_demo.tex

package info (click to toggle)
suitesparse 1%3A5.12.0%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 176,720 kB
  • sloc: ansic: 1,193,914; cpp: 31,704; makefile: 6,638; fortran: 1,927; java: 1,826; csh: 765; ruby: 725; sh: 529; python: 333; perl: 225; sed: 164; awk: 35
file content (590 lines) | stat: -rw-r--r-- 18,264 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590

% This LaTeX was auto-generated from an M-file by MATLAB.
% To make changes, update the M-file and republish this document.

\documentclass{article}
\usepackage{graphicx}
\usepackage{color}

\sloppy
\definecolor{lightgray}{gray}{0.5}
\setlength{\parindent}{0pt}

\begin{document}

    
    
\section*{THE FACTORIZE OBJECT for solving linear systems}

\begin{par}
Copyright 2011-2012, Timothy A. Davis,
\begin{verbatim}http://www.suitesparse.com\end{verbatim}
\begin{verbatim}DrTimothyAldenDavis@gmail.com\end{verbatim} \end{par}
\vspace{1em}
\begin{par}
This is a demonstration of the FACTORIZE object for solving linear systems and
least-squares problems, and for computations with the matrix inverse and
pseudo-inverse.
\end{par} \vspace{1em}

\subsection*{Contents}

\begin{itemize}
\setlength{\itemsep}{-1ex}
   \item Rule Number One: never multiply by the inverse, inv(A)
   \item Rule Number Two:  never break Rule Number One
   \item How to use BACKSLASH solve A*x=b
   \item BACKSLASH versus INV ... let the battle begin
   \item LU and LINSOLVE are fast and accurate but complicated to use
   \item INV is easy to use, but slow and inaccurate
   \item So the winner is ... nobody
   \item The FACTORIZE object to the rescue
   \item Least-squares problems
   \item Underdetermined systems
   \item Computing selected entries in the inverse or pseudo-inverse
   \item Computing the entire inverse or pseudo-inverse
   \item Update/downdate of a dense Cholesky factorization
   \item Caveat Executor
   \item Summary
\end{itemize}


\subsection*{Rule Number One: never multiply by the inverse, inv(A)}

\begin{par}
Use backslash or a matrix factorization instead (LU, CHOL, or QR).
\end{par} \vspace{1em}


\subsection*{Rule Number Two:  never break Rule Number One}

\begin{par}
However, the problem with Rule Number One is that it can be hard to figure out
which matrix factorization to use and how to use it.  Using LU, CHOL, or QR is
complicated, particularly if you want the best performance.  BACKSLASH
(MLDIVIDE) is great, but it can't be reused when solving multiple systems
(x=A\ensuremath{\backslash}b and y=A\ensuremath{\backslash}c).  Its syntax
doesn't match the use of the inverse in mathematical expressions, either.
\end{par} \vspace{1em}
\begin{par}
The goal of the FACTORIZE object is to solve this problem ...
\end{par} \vspace{1em}
\begin{par}
"Don't let that INV go past your eyes; to solve that system, FACTORIZE!"
\end{par} \vspace{1em}


\subsection*{How to use BACKSLASH solve A*x=b}

\begin{par}
First, let's create a square matrix A and a right-hand-side b for a linear
system A*x=b.  There are many ways to solve this system.  The best way is to
use x=A\ensuremath{\backslash}b.  The residual r is a vector of what's left
over in each equation, and its norm tells you how accurately the system was
solved.
\end{par} \vspace{1em}
\begin{verbatim}
format compact ;
A = rand (3)
b = rand (3,1)
x = A\b
r = b-A*x ;
norm (r)
\end{verbatim}

        \color{lightgray} \begin{verbatim}A =
    0.2748    0.2719    0.3696
    0.2217    0.8329    0.5006
    0.9315    0.5791    0.0753
b =
    0.1293
    0.9138
    0.4589
x =
   -0.3827
    1.4657
   -0.4437
ans =
   1.2413e-16
\end{verbatim} \color{black}
    

\subsection*{BACKSLASH versus INV ... let the battle begin}

\begin{par}
The backslash operation x=A\ensuremath{\backslash}b is mathematically the same
as x=inv(A)*b. However, backslash is faster and more accurate since it uses a
matrix factorization instead of multiplying by the inverse.  Even though your
linear algebra textbook might write x=A\^{}(-1)*b as the solution to the system
A*x=b, your textbook author never means for you to compute the inverse.
\end{par} \vspace{1em}
\begin{par}
These next statements give the same answer, so what's the big deal?
\end{par} \vspace{1em}
\begin{verbatim}
S = inv(A) ;
x = S*b
x = A\b
\end{verbatim}

        \color{lightgray} \begin{verbatim}x =
   -0.3827
    1.4657
   -0.4437
x =
   -0.3827
    1.4657
   -0.4437
\end{verbatim} \color{black}
    \begin{par}
The big deal is that you should care about speed and you should care even more
about accuracy.  BACKSLASH relies on matrix factorization (LU, CHOL, QR, or
other specialized methods).  It's faster and more reliable than multiplying by
the inverse, particularly for large matrices and sparse matrices.  Here's an
illustration of how pathetic inv(A)*b can be.
\end{par} \vspace{1em}
\begin{verbatim}
A = gallery ('frank',16) ; xtrue = ones (16,1) ; b = A*xtrue ;

x = inv(A)*b ; norm (b-A*x)
x = A\b      ; norm (b-A*x)
\end{verbatim}

        \color{lightgray} \begin{verbatim}ans =
    0.0606
ans =
   1.7764e-15
\end{verbatim} \color{black}
    \begin{par}
The performance difference between BACKSLASH and INV for even small sparse
matrices is striking.
\end{par} \vspace{1em}
\begin{verbatim}
load west0479 ;
A = west0479 ;
n = size (A,1)
b = rand (n,1) ;
tic ; x = A\b ; toc
norm (b-A*x)
tic ; x = inv(A)*b ; toc
norm (b-A*x)
\end{verbatim}

        \color{lightgray} \begin{verbatim}n =
   479
Elapsed time is 0.002425 seconds.
ans =
   1.9174e-10
Elapsed time is 0.041780 seconds.
ans =
   3.4438e-09
\end{verbatim} \color{black}
    \begin{par}
What if you want to solve multiple systems?  Use a matrix factorization. But
which one?  And how do you use it?  Here are some alternatives using LU for the
sparse west0479 matrix, but some are faster than others.
\end{par} \vspace{1em}
\begin{verbatim}
tic ; [L,U]     = lu(A) ; x1 = U \ (L \ b)         ; t1=toc ; nz1=nnz(L+U);
tic ; [L,U,P]   = lu(A) ; x2 = U \ (L \ P*b)       ; t2=toc ; nz2=nnz(L+U);
tic ; [L,U,P,Q] = lu(A) ; x3 = Q * (U \ (L \ P*b)) ; t3=toc ; nz3=nnz(L+U);

fprintf ('1: nnz(L+U): %5d time: %8.4f resid: %e\n', nz1,t1, norm(b-A*x1));
fprintf ('2: nnz(L+U): %5d time: %8.4f resid: %e\n', nz2,t2, norm(b-A*x2));
fprintf ('3: nnz(L+U): %5d time: %8.4f resid: %e\n', nz3,t3, norm(b-A*x3));
\end{verbatim}

        \color{lightgray} \begin{verbatim}1: nnz(L+U): 16151 time:   0.0031 resid: 1.346712e-10
2: nnz(L+U): 15826 time:   0.0081 resid: 1.757002e-10
3: nnz(L+U):  3704 time:   0.0017 resid: 1.691750e-10
\end{verbatim} \color{black}
    

\subsection*{LU and LINSOLVE are fast and accurate but complicated to use}

\begin{par}
A quick look at ``help lu'' will scroll off your screen.  For full matrices,
[L,U,p] = lu (A,'vector') is fastest.  Then for the forward/backsolves, use
LINSOLVE instead of BACKSLASH for even faster performance.  But for sparse
matrices, use the optional 'Q' output of LU so you get a good fill-reducing
ordering.  But you can't use 'Q' if the matrix is full.  But LINSOLVE doesn't
work on sparse matrices.
\end{par} \vspace{1em}
\begin{par}
But ... Ack!  That's getting complicated ...
\end{par} \vspace{1em}
\begin{par}
Here's the best way to solve A*x=b and A*y=c when A is full and unsymmetric:
\end{par} \vspace{1em}
\begin{verbatim}
n = 1000 ;
A = rand (n) ;
b = rand (n,1) ;
c = rand (n,1) ;
tic ; [L,U,p] = lu (A, 'vector') ; LUtime = toc

tic ; x = U \ (L \ b (p,:)) ;
      y = U \ (L \ c (p,:)) ; toc

tic ; opL = struct ('LT', true) ;
      opU = struct ('UT', true) ;
      x = linsolve (U, linsolve (L, b(p,:), opL), opU) ;
      y = linsolve (U, linsolve (L, c(p,:), opL), opU) ; toc
\end{verbatim}

        \color{lightgray} \begin{verbatim}LUtime =
    0.0155
Elapsed time is 0.004917 seconds.
Elapsed time is 0.002092 seconds.
\end{verbatim} \color{black}
    

\subsection*{INV is easy to use, but slow and inaccurate}

\begin{par}
Oh bother!  Using LU and LINSOLVE is too complicated.  You just want to solve
your system.  Let's just compute inv(A) and use it twice.  Easy to write, but
slower and less accurate ...
\end{par} \vspace{1em}
\begin{verbatim}
S = inv (A) ;
x = S*b ; norm (b-A*x)
y = S*c ; norm (c-A*y)
\end{verbatim}

        \color{lightgray} \begin{verbatim}ans =
   2.3292e-11
ans =
   1.7292e-11
\end{verbatim} \color{black}
    \begin{par}
Sometimes using the inverse seems inevitable.  For example, your textbook might
show the Schur complement formula as S = A-B*inv(D)*C.  This can be done
without inv(D) in one of two ways: SLASH or BACKSLASH (MRDIVIDE or MLDIVIDE to
be precise).
\end{par} \vspace{1em}
\begin{par}
inv(A)*B and A\ensuremath{\backslash}B are mathematically equivalent, as are
B*inv(A) and B/A, so these three methods give the same results (ignoring
computational errors, which are worse for inv(D)).  Only the first equation
looks like the equation in your textbook, however.
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (200) ; B = rand (200) ; C = rand (200) ; D = rand (200) ;

tic ; S1 = A - B*inv(D)*C ; toc ;
tic ; S2 = A - B*(D\C) ;    toc ;
tic ; S3 = A - (B/D)*C ;    toc ;
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.002398 seconds.
Elapsed time is 0.001632 seconds.
Elapsed time is 0.001474 seconds.
\end{verbatim} \color{black}
    

\subsection*{So the winner is ... nobody}

\begin{par}
BACKSLASH: mostly simple to use (except remember that Schur complement
formula?).  Fast and accurate ... but slow if you want to solve       two
linear systems with the same matrix A.
\end{par} \vspace{1em}
\begin{par}
LU, QR, CHOL: fast and accurate.  Awful syntax to use.  Drag out your
linear algebra textbook if you want to use these in MATLAB.       Whenever I
use them I have to derive them from scratch, even       though I \textbf{wrote}
most of the sparse factorizations used in MATLAB!
\end{par} \vspace{1em}
\begin{par}
INV: slow and inaccurate.  Wins big on ease-of-use, though, since it's a
direct plug-in for all your nice mathematical formulas.
\end{par} \vspace{1em}
\begin{par}
No method is best on all three criterion: speed, accuracy, and ease of use.
\end{par} \vspace{1em}
\begin{par}
Is there a solution?  Yes ... keeping reading ...
\end{par} \vspace{1em}


\subsection*{The FACTORIZE object to the rescue}

\begin{par}
The FACTORIZE method is just as easy to use as INV, but just as fast and
accurate as BACKSLASH, LU, QR, CHOL, and LINSOLVE.
\end{par} \vspace{1em}
\begin{par}
F = factorize(A) computes the factorization of A and returns it as an object
that you can reuse to solve a linear system with x=F\ensuremath{\backslash}b.
It picks LU, QR, or Cholesky for you, just like BACKSLASH.
\end{par} \vspace{1em}
\begin{par}
S = inverse(A) is simpler yet.  It does NOT compute inv(A), but factorizes A.
When multiplying S*b, it doesn't mulitply by the inverse, but uses the correct
forward/backsolve equations to solve the linear system.
\end{par} \vspace{1em}
\begin{verbatim}
n = 1000 ;
A = rand (n) ;
b = rand (n,1) ;
c = rand (n,1) ;

tic ;                       x = A\b ; y = A\c ; toc
tic ; S = inv(A) ;          x = S*b ; y = S*c ; toc
tic ; F = factorize(A) ;    x = F\b ; y = F\c ; toc
tic ; S = inverse(A) ;      x = S*b ; y = S*c ; toc
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.051483 seconds.
Elapsed time is 0.053813 seconds.
Elapsed time is 0.025811 seconds.
Elapsed time is 0.029840 seconds.
\end{verbatim} \color{black}
    

\subsection*{Least-squares problems}

\begin{par}
Here are some different methods for solving a least-squares problem when your
system is over-determined.  The last two methods are the same.
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (1000,200) ;
b = rand (1000,1) ;

tic ; x = A\b            ; toc, norm (A'*A*x-A'*b)
tic ; x = pinv(A)*b      ; toc, norm (A'*A*x-A'*b)
tic ; x = inverse(A)*b   ; toc, norm (A'*A*x-A'*b)
tic ; x = factorize(A)\b ; toc, norm (A'*A*x-A'*b)
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.010705 seconds.
ans =
   2.7575e-12
Elapsed time is 0.025339 seconds.
ans =
   2.3477e-12
Elapsed time is 0.008903 seconds.
ans =
   2.5140e-12
Elapsed time is 0.008408 seconds.
ans =
   2.5140e-12
\end{verbatim} \color{black}
    \begin{par}
FACTORIZE is better than BACKSLASH because you can reuse the factorization for
different right-hand-sides.  For full-rank matrices, it's better than PINV
because it's faster (and PINV fails for sparse matrices).
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (1000,200) ;
b = rand (1000,1) ;
c = rand (1000,1) ;

tic ;                  ; x = A\b ; y = A\c ; toc
tic ; S = pinv(A)      ; x = S*b ; y = S*c ; toc
tic ; S = inverse(A)   ; x = S*b ; y = S*c ; toc
tic ; F = factorize(A) ; x = F\b ; y = F\c ; toc
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.021934 seconds.
Elapsed time is 0.027198 seconds.
Elapsed time is 0.009692 seconds.
Elapsed time is 0.010197 seconds.
\end{verbatim} \color{black}
    

\subsection*{Underdetermined systems}

\begin{par}
The under-determined system A*x=b where A has more columns than rows has many
solutions.  x=A\ensuremath{\backslash}b finds a basic solution (some of the
entries in x are zero).  pinv(A)*b finds a minimum 2-norm solution, but it's
slow.  QR factorization will do the same if A has full rank.  That's what the
factorize(A) and inverse(A) methods do.
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (200,1000) ;
b = rand (200,1) ;

tic ; x = A\b            ; toc, norm (x)
tic ; x = pinv(A)*b      ; toc, norm (x)
tic ; x = inverse(A)*b   ; toc, norm (x)
tic ; x = factorize(A)\b ; toc, norm (x)
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.016247 seconds.
ans =
    2.5580
Elapsed time is 0.034924 seconds.
ans =
    0.5154
Elapsed time is 0.012460 seconds.
ans =
    0.5154
Elapsed time is 0.009924 seconds.
ans =
    0.5154
\end{verbatim} \color{black}
    

\subsection*{Computing selected entries in the inverse or pseudo-inverse}

\begin{par}
If you want just a few entries from the inverse, it's still better to formulate
the problem as a system of linear equations and use a matrix factorization
instead of computing inv(A).  The FACTORIZE object does this for you, by
overloading the subsref operator.
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (1000) ;

tic ; S = inv (A)     ; S (2:3,4), toc
tic ; S = inverse (A) ; S (2:3,4), toc
\end{verbatim}

        \color{lightgray} \begin{verbatim}ans =
   -0.2554
    0.0993
Elapsed time is 0.047095 seconds.
ans =
   -0.2554
    0.0993
Elapsed time is 0.030233 seconds.
\end{verbatim} \color{black}
    

\subsection*{Computing the entire inverse or pseudo-inverse}

\begin{par}
Rarely, and I mean RARELY, you really do need the inverse.  More frequently
what you want is the pseudo-inverse.  You can force a factorization to become a
plain matrix by converting it to double.  Note that inverse(A) only handles
full-rank matrices (either dense or sparse), whereas pinv(A) works for all
dense matrices (not sparse).
\end{par} \vspace{1em}
\begin{par}
The explicit need for inv(A) (or S=A\ensuremath{\backslash}eye(n), which is the
same thing) is RARE.  If you ever find yourself multiplying by the inverse,
then you know one thing for sure.  You know with certainty that you don't know
what you're doing.
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (500) ;
tic ; S1 = inv (A) ;            ; toc
tic ; S2 = double (inverse (A)) ; toc
norm (S1-S2)

A = rand (500,400) ;
tic ; S1 = pinv (A)             ; toc
tic ; S2 = double (inverse (A)) ; toc
norm (S1-S2)
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.009174 seconds.
Elapsed time is 0.013046 seconds.
ans =
   1.6446e-12
Elapsed time is 0.073158 seconds.
Elapsed time is 0.016360 seconds.
ans =
   1.7565e-14
\end{verbatim} \color{black}
    

\subsection*{Update/downdate of a dense Cholesky factorization}

\begin{par}
Wilkinson considered the update/downdate of a matrix factorization to be a key
problem in computational linear algebra.  The idea is that you first factorize
a matrix.  Next, make a low-rank change to A, and patch up (or down...) the
factorization so that it becomes the factorization of the new matrix.  In
MATLAB, this only works for dense symmetric positive definite matrices, via
cholupdate.  This is much faster than computing the new factorization from
scratch.
\end{par} \vspace{1em}
\begin{verbatim}
n = 1000 ;
A = rand (n) ;
A = A*A' + n*eye (n) ;
w = rand (n,1) ; t = rand (n,1) ; b = rand (n,1) ;
F = factorize (A) ;

tic ; F = cholupdate (F,w,'+') ; x = F\b ; toc
tic ; y = (A+w*w')\b ;      toc
norm (x-y)

tic ; F = cholupdate (F,t,'-') ; x = F\b ; toc
tic ; y = (A+w*w'-t*t')\b ; toc
norm (x-y)
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 0.010284 seconds.
Elapsed time is 0.015608 seconds.
ans =
   3.6395e-17
Elapsed time is 0.011662 seconds.
Elapsed time is 0.019173 seconds.
ans =
   3.5119e-17
\end{verbatim} \color{black}
    

\subsection*{Caveat Executor}

\begin{par}
One caveat:  If you have a large number of very small systems to solve, the
object-oriented overhead of creating and using an object can dominate the run
time, at least in MATLAB R2011a.  For this case, if you want the best
performance, stick with BACKSLASH, or LU and LINSOLVE (just extract the
appropriate formulas from the M-files in the FACTORIZE package).
\end{par} \vspace{1em}
\begin{par}
Hopefully the object-oriented overhead will drop in future versions of MATLAB,
and you can ignore this caveat.
\end{par} \vspace{1em}
\begin{verbatim}
A = rand (10) ; b = rand (10,1) ; F = factorize (A) ;

tic ; for k = 1:10000, x = F\b ; end ; toc

tic ; for k = 1:10000, x = A\b ; end ; toc

[L,U,p] = lu (A, 'vector') ;
opL = struct ('LT', true) ;
opU = struct ('UT', true) ;
tic ;
for k = 1:10000
    x = linsolve (U, linsolve (L, b(p,:), opL), opU) ;
end
toc
\end{verbatim}

        \color{lightgray} \begin{verbatim}Elapsed time is 1.156836 seconds.
Elapsed time is 0.123091 seconds.
Elapsed time is 0.057961 seconds.
\end{verbatim} \color{black}
    

\subsection*{Summary}

\begin{par}
So ... don't use INV, and don't worry about how to use LU, CHOL, or QR
factorization.  Just install the FACTORIZE package, and you're on your way.
Assuming you are now in the Factorize/ directory, cut-and-paste these commands
into your command window:
\end{par} \vspace{1em}
\begin{verbatim}addpath (pwd)
savepath\end{verbatim}
\begin{par}
And remember ...
\end{par} \vspace{1em}
\begin{par}
{\em Don't let that INV go past your eyes; to solve that system, FACTORIZE!}
\end{par} \vspace{1em}



\end{document}