just pass vectors through to the PETSc interface #183

merged 1 commit into from Dec 10, 2013


None yet
2 participants

friedmud commented Dec 9, 2013

Is there a reason we haven't always done it this way?

I've done this because that for loop was showing up in my timing - and even though this may just push that for loop down into PETSc... it at least makes me feel better ;-)

How far back does the VecSetValues API go? It's not one of the ones that changed argument orderings on us at one point, is it?


friedmud replied Dec 10, 2013

friedmud added a commit that referenced this pull request Dec 10, 2013

Merge pull request #183 from friedmud/petsc_vector_optimize
just pass vectors through to the PETSc interface

@friedmud friedmud merged commit 221804c into libMesh:master Dec 10, 2013

@friedmud friedmud deleted the friedmud:petsc_vector_optimize branch Dec 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment