On Tue, Nov 20, 2012 at 3:32 PM, Jens Lohne Eftang <[email protected]> wrote: > All, > > According to this thread > > http://sourceforge.net/mailarchive/message.php?msg_id=24029850 > > in the devel list there were plans on changing the API for > cholesky_solve and lu_solve such that the interface with two arguments > did not change the arguments, and another interface with only one > argument would.
Hmm, yeah, I never got around to making the *all* changes discussed in that thread, apparently, but the rhs are no longer modified. > There seems to be only one implementation if cholesky_solve and lu_solve > in the current libmesh version, which takes two arguments. Does it > change the rhs input vector? (It seems to me that it doesn't but I just > wanted to make sure). Neither LU nor Cholesky modify the rhs vector: it's passed in as const reference to the _XXX_back_substitute() routines, and copies are made where required. > Also it seems that cholesky_solve() will change my matrix (due to the > factorization I assume). Is it correct that subsequent solves will give > the correct answer, but that if I need the matrix for matrix > multiplication I will have to keep a copy? That's correct, yes. -- John ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
