[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: improved QR & Cholesky updating
From: |
John W. Eaton |
Subject: |
Re: improved QR & Cholesky updating |
Date: |
Wed, 21 Jan 2009 14:41:56 -0500 |
On 21-Jan-2009, Jaroslav Hajek wrote:
| True, but it doesn't catch a warning, does it?
Are there cases where missing functions only generate warnings?
| OK, so where should the replacements go?
| Putting them in the QR & Cholesky classes means writing replacement
| code for 4 * 8 + 4 * 5 = 52 methods (OK, In fact only quarter and then
| copy-paste-search-replace-adjust). I suppose writing generic
| replacements directly in the DLD funcs would be simpler. Also, I'm
| thinking of issuing a warning the first time any of the updating
| function is run, only once.
|
| What do you think?
I think the best place is in the QR::update method (for example),
because that way, any code that might use that class won't have to
work around missing functionality either. Can templates or macros
help here?
jwe
- improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/17
- Re: improved QR & Cholesky updating, David Bateman, 2009/01/17
- Re: improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/20
- Re: improved QR & Cholesky updating, John W. Eaton, 2009/01/20
- Re: improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/21
- Re: improved QR & Cholesky updating, John W. Eaton, 2009/01/21
- Re: improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/21
- Re: improved QR & Cholesky updating, John W. Eaton, 2009/01/21
- Re: improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/21
- Re: improved QR & Cholesky updating,
John W. Eaton <=
- Re: improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/21
- Re: improved QR & Cholesky updating, John W. Eaton, 2009/01/21
- Re: improved QR & Cholesky updating, Jaroslav Hajek, 2009/01/22
- Re: improved QR & Cholesky updating, John W. Eaton, 2009/01/22