If you really think about, all of the decomposition classes should be handled by factories. The decompositions all seem to occur in the constructor. Everything else is derived from those results, so one could argue that the actual decomposition code could be written very procedurally and put into the factory as a static private method. The returned class from the factory would be nothing more than a container of the results and methods to get the data and derivatives of the data.
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Greg Sterijevski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Ted Dunning
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Sébastien Brisard
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Luc Maisonobe
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Gilles Sadowski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Ted Dunning
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Ted Dunning
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Greg Sterijevski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Gilles Sadowski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Ted Dunning
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Greg Sterijevski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Ted Dunning
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Phil Steitz
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Greg Sterijevski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Gilles Sadowski
- Re: [MATH] Re: Pivoting QR Decomposition: Take Two! Gilles Sadowski