Dear Timo:
After reading your comment:
"SparseMatrix::vmult(dst, src) does not require ghost entries in
the vector src (but it won't hurt either)"
I started to check this in my own codes (that uses a lot of vmults) and
realized that I always use ''src'' that is locally relevant. I did that
Dear Timo:
After reading your comment:
"SparseMatrix::vmult(dst, src) does not require ghost entries in
the vector src (but it won't hurt either)"
I started to check this in my own codes (that uses a lot of vmults) and
realized that I always use ''src'' that is locally relevant. I did that
, Vect2 and Vect3 defined/declared/initialized a priori works
> fine. But it comes with the overhead of definining these vectors separately
> rather than with the the vector of shared pointers.
>
> On Fri, Mar 24, 2017 at 1:50 AM, Jean-Paul Pelteret <jppelte...@gmail.com>
> wrot
Dear everybody:
I don't have any particular problem, just trying to streamline a code. I am
have a mess with the interfaces of my code, in particular with the
functions and classes I have created, primarily because I have to handle a
''packet'' of vectors, say
PETScWrappers::MPI::Vector
