On 08/21/2012 12:02 PM, Roy Stogner wrote: > > On Tue, 21 Aug 2012, Derek Gaston wrote: > >> For now I'll vote for #2. One thing that you could add to #2 is a >> method >> that we could call to clear/delete the sparsity pattern in the case >> where we >> _know_ we won't need it again and we really do need the memory... > > Nice idea - if we go with #2 then I'll be sure to do so.
As a reduced basis person, I'd certainly vote for #2. Another question: does this issue explain why the reduced basis examples never worked with trilinos? David ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
