Garth Wells <gn...@cam.ac.uk> writes: > On Wed, 2018-03-07 at 16:13 -0700, Jed Brown wrote: >> No reason, just didn't need it. I don't think any PETSc developers >> use >> VecSetValues* because VecScatter is a more natural interface with >> lower >> overhead. >> > > Any demos of its recommended use?
snes/examples/tutorials/ex28.c is my recommended demo for both MatGetLocalSubMatrix() and composite vectors. You can follow the example (using DMComposite) or call VecScatter directly.