On Wed, 11 May 2011, Derek Gaston wrote: > Just a hunch: I think that Petsc is giving us a vector that hasn't > been properly closed as the solution vector. Note that I had to do > solution->close() before using the copy operator... that's because > Petsc claimed that the solution vector wasn't in the right state!
What happens when you add the solution->close() but leave the communication to VecScatter rather than VecCopy? Either way, I think we might want to assert(closed) rather than adding a usually-redundant close call here. --- Roy ------------------------------------------------------------------------------ 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
