On May 11, 2011, at 11:46 PM, Roy Stogner wrote: > What happens when you add the solution->close() but leave the > communication to VecScatter rather than VecCopy?
Dunno... I'll give it a whirl. > Either way, I think we might want to assert(closed) rather than adding > a usually-redundant close call here. assert() won't work. We don't want it to die. What we need is to detect that it's not closed and close it. I don't know how to do that. This is a PetscVector that we might have made from a raw Vec (That's what happens in PetscNonlinearSolver).... we don't exactly know the state of it... Derek ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
