Have we abstracted VecCUDAGetArray[Read] ? VecDeviceGetArray? Mark
https://petsc.org/main/docs/manualpages/Vec/VecGetArrayAndMemType.html Mark Adams <[email protected]> writes:
Have we abstracted VecCUDAGetArray[Read] ?
VecDeviceGetArray?
Mark
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 <[email protected]> wrote:
https://petsc.org/main/docs/manualpages/Vec/VecGetArrayAndMemType.html
Mark Adams <[email protected]> writes:
Have we abstracted VecCUDAGetArray[Read] ?
VecDeviceGetArray?
Mark
nvm, the Read version is there. On Wed, Apr 28, 2021 at 7:45 AM Mark Adams <[email protected]> wrote:
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 <[email protected]> wrote:
https://petsc.org/main/docs/manualpages/Vec/VecGetArrayAndMemType.html
Mark Adams <[email protected]> writes:
Have we abstracted VecCUDAGetArray[Read] ?
VecDeviceGetArray?
Mark
participants (2)
-
Jed Brown -
Mark Adams