From: Yves M. <yma...@ci...> - 2011-04-07 15:42:16
|
Dear List, I'm using VXL through ITK and am looking at speeding up matrix inversion (for big matrices ~5000*5000). I'm using VXL 1.9.0 (from ITK 3.20). I hope my question is not too outdated since the current version is 1.13. >From what I understand, the SVD implemented in VNL uses LINPACK. Isn't LAPACK faster? Since LAPACK is already included in VXL, are you planning on using it for SVD? Is there (or will there be) a way to switch from one implementation using LINPACK to another using LAPACK if people still want to use LINPACK? Best regards, Yves |
From: David R. <dav...@qu...> - 2011-04-07 17:25:00
|
I would also be interested in this if it makes SVD faster for large matrices (1000+). I've added vxl-maintainers to the recipients list for this email. David. On 8 April 2011 01:29, Yves Martelli <yma...@ci...> wrote: > Dear List, > > I’m using VXL through ITK and am looking at speeding up matrix inversion > (for big matrices ~5000*5000). I’m using VXL 1.9.0 (from ITK 3.20). I hope > my question is not too outdated since the current version is 1.13. > > From what I understand, the SVD implemented in VNL uses LINPACK. Isn’t > LAPACK faster? Since LAPACK is already included in VXL, are you planning on > using it for SVD? Is there (or will there be) a way to switch from one > implementation using LINPACK to another using LAPACK if people still want to > use LINPACK? > > Best regards, > > Yves > > > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > Vxl-users mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-users > > |
From: Peter V. <pet...@ya...> - 2011-04-08 10:04:40
|
One possible way to have both a LINPACK and a LAPACK implementation for SVD next to each other in vnl_algo would be to add a static member to the vnl_svd class which stores (on a per-thread base) the user choice (lapack or linpack) for future vnl_svd uses. Which leaves open the actual vnl implementation (based on lapack) to be written out. Feel free to contribute! I'll happily add it to the vnl_svd class implementation. -- Peter. |