There does not seem to be a Read variant of VecGetArrayAndMemType.

I am getting an error:

[0]PETSC ERROR: Object is in wrong state
[0]PETSC ERROR: Vec is already locked for read-only or read/write access, argument # 1

This is in a TS callback. Does TS lock the state vector from writing?

Should I add a Read version of VecGetArrayAndMemType?

On Wed, Apr 28, 2021 at 12:29 AM Jed Brown <jed@jedbrown.org> wrote:

https://petsc.org/main/docs/manualpages/Vec/VecGetArrayAndMemType.html

Mark Adams <mfadams@lbl.gov> writes:

> Have we abstracted VecCUDAGetArray[Read] ?
>
> VecDeviceGetArray?
>
> Mark