Matthew Knepley <[email protected]> writes:

It was suggested to me that we add VecGhostUpdate() to VecAssembly(). This sounds reasonable to me. What do you think?

Uh, why? What is the most common use of VecAssembly? Seems like building b or x_0 to solve A x = b, in which case you don't need updated ghost values. Also, who uses VecGhost _and_ VecAssembly for the same Vec? That's quite wasteful; if you have local indexing, why not just use VecGhostUpdate(...,SCATTER_REVERSE)?