Re: [petsc-users] Calling LAPACK routines from PETSc

2019-05-20 Thread Dave Lee via petsc-users
Thanks Barry, I found some helpful examples on the intel lapack site - moral of the story: using C ordering for input matrix, but transposed output matrices leads to a consistent solution. Cheers, Dave. On Mon, May 20, 2019 at 6:07 PM Smith, Barry F. wrote: > > > > On May 20, 2019, at 2:28 AM,

Re: [petsc-users] Calling LAPACK routines from PETSc

2019-05-20 Thread Smith, Barry F. via petsc-users
> On May 20, 2019, at 2:28 AM, Dave Lee wrote: > > Thanks Jed and Barry, > > So, just to confirm, > > -- From the KSP_GMRES structure, if I call *HH(a,b), that will return the row > a, column b entry of the Hessenberg matrix (while the back end array > *hh_origin array is ordering using t

Re: [petsc-users] Calling LAPACK routines from PETSc

2019-05-19 Thread Smith, Barry F. via petsc-users
The little work arrays in GMRES tend to be stored in Fortran ordering; there is no C style p[][] indexing into such arrays. Thus the arrays can safely be sent to LAPACK. The only trick is knowing the two dimensions and as Jed say the "leading dimension parameter. He gave you a place to loo

Re: [petsc-users] Calling LAPACK routines from PETSc

2019-05-19 Thread Jed Brown via petsc-users
Dave Lee via petsc-users writes: > Hi Petsc, > > I'm attempting to implement a "hookstep" for the SNES trust region solver. > Essentially what I'm trying to do is replace the solution of the least > squares problem at the end of each GMRES solve with a modified solution > with a norm that is cons