Sorry about our late reply. Isn't VecGetValues similar? Note that
VecGetValuesSection currently leaks a mutable pointer and really shouldn't
exist like this without a matching VecRestoreValuesSection.
PetscCall(VecGetArray(v, ));
*values = [s->atlasOff[p]];
PetscCall(VecRestoreArray(v,
Do you think this is more correct than just using "Face Sets", which gives you
a numbered index?
There is curently some inconsistency between file formats in whether various
sets show up as stand-alone labels or values under Face Sets. And there's this
lingering issue to have a way to name
> On Jun 25, 2022, at 9:44 AM, Matthew Martineau wrote:
>
> Thanks - AmgX will accept unordered column indices.
Any performance hit?
We can provide them sorted efficiently in the future but currently can only
provide unordered column indices efficiently on the GPU.
Barry
>
> From:
Thanks - AmgX will accept unordered column indices.
From: Barry Smith
Sent: Saturday, 25 June 2022, 14:39
To: Mark Adams
Cc: Matthew Martineau ; For users of the development
version of PETSc
Subject: Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs
Does AMGX require sorted column indices? (Python indentation notation below)
If not
just use MatMPIAIJGetLocalMatMerge instead of MatMPIAIJGetLocalMat.
If yes,
on the first call
Mat tmplocal;
PetscCall(MatMPIAIJGetLocalMat(Pmat, MAT_INITIAL_MATRIX, ));
On Fri, Jun 24, 2022 at 1:54 PM Barry Smith wrote:
>
>
> On Jun 24, 2022, at 1:38 PM, Mark Adams wrote:
>
> I am rearranging the code for clarity from the repo but I have:
>
> PetscBool is_dev_ptrs;
> PetscCall(MatMPIAIJGetLocalMat(Pmat, MAT_INITIAL_MATRIX, >localA));
>
