On Tue, 7 Apr 2009, Derek Gaston wrote:
On Apr 7, 2009, at 9:22 AM, Roy Stogner wrote:
On Mon, 6 Apr 2009, Tim Kroeger wrote:
I would vote for making ghosted vectors the default now.
I'm tempted to agree. (Which probably means everyone else is way
ahead of me; they just talked me into making --enable-second a default
option, years after I wrote it.)
Personally... I don't see much point in making it the default...
Better memory usage by default, better scalability by default, plus
better test coverage. We only caught that nasty parallel AMR bug
because, while it would have manifested as slightly corrupted
solutions with serial local vectors, it tripped a libmesh_assert()
with ghosted vectors.
unless we're going to do away with current_local_solution.
We are - the question is just "when".
How big of a deal would it be to remove that at this point?
It wouldn't be too hard, if we were just talking about PETSc. But
unless we want to break our other interfaces, we'll need the
equivalent of ghosted vectors from LASPACK and Trilinos (and
DistributedVector? anyone using that for explicit problems?) too.
---
Roy
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
