So... up until now I've only ever needed one "ghosted" vector... for the solution vector. And, just as we do in petsc_nonlinear_solver.C I've just been bastardizing System::update() and current_local_solution to "ghostize" a vector.
But now that won't work because I need two such vectors simultaneously. What is the current state of the ghosted vector situation? What is the right way to take a Vec from a Petsc callback and form a ghosted PetscVector out of it that I can pass to my own (assembly like) routines? Thanks! Derek ------------------------------------------------------------------------------ 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