On Tue, 31 Aug 2010, Derek Gaston wrote: > On Aug 31, 2010, at 1:51 PM, Roy Stogner wrote: > >> Otherwise the only thing to do is add a non-default code path, where >> instead of letting PETSc work on solution while we work to keep >> current_local_solution sync'ed up we do the opposite. > > That's an option... but what about just making a compile-time option > that makes NumericVector::build() create ghosted vectors by default?
We don't want to create ghosted instead of serial vectors - sometimes code is going to ask for a serial vector because it really needs data that's not on the local processor or its ghost cells. (and because it's too lazy to build a proper extended send list...) But it would be sufficient for your case to just create ghosted instead of parallel vectors. We can't do that in general in NumericVector::build() because that doesn't have access to DofMap's send_list. But we could do that as an option (run-time, even - make it a flag in the System class) in System::add_vector() and *System::init(). --- Roy ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
