Garth Wells writes:
> On Thu, 2018-03-08 at 11:25 -0700, Jed Brown wrote:
>> Garth Wells 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
>> > >
On Thu, 2018-03-08 at 11:25 -0700, Jed Brown wrote:
> Garth Wells 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
Garth Wells 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
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?
Garth
> Garth Wells
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.
Garth Wells writes:
> Is there a reason why there is no 'VecGetLocalSubVector' to match
> MatGetLocalSubMatrix?
>
> I've
Is there a reason why there is no 'VecGetLocalSubVector' to match
MatGetLocalSubMatrix?
I've used VecGetSubVector, but can't use local indices with it, e.g.
can't use VecSetValuesLocal.
Garth