Re: [petsc-users] PETSC_VIEWER_DRAW_(Comm) Fortran interface missing?

Thanks Satish! > On Mar 8, 2018, at 9:50 AM, Satish Balay wrote: > > Great! I've merged balay/ftn-VIEWER_DRAW/maint to 'maint' > > Satish > > On Thu, 8 Mar 2018, Tim Steinhoff wrote: > >> Yeah, thanks Satish. >> PETSC_VIEWER_DRAW_() works perfectly and I could not

[petsc-users] make: *** No rule to make target `chk_makej', needed by `all'. Stop.

Hi, I've just been trying to compile SLEPC on a cluster, and am getting the following error message after I type "make": > ./configure Checking environment... done Checking PETSc installation... done Checking LAPACK library... done Writing various configuration files... done Generating

Re: [petsc-users] No VecGetLocalSubVector?

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

Re: [petsc-users] No VecGetLocalSubVector?

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

Re: [petsc-users] No VecGetLocalSubVector?

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 >> > >

Re: [petsc-users] No VecGetLocalSubVector?

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

[petsc-users] Tweaking my code for CUDA

Hello all, I am working on porting a linear solver into GPUs for timing purposes, so far i've been able to compile and run the CUSP libraries and compile PETSc to be used with CUSP and ViennaCL, after the initial runs i noticed some errors, they are different for different flags and i would

Re: [petsc-users] No VecGetLocalSubVector?

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

Re: [petsc-users] make: *** No rule to make target `chk_makej', needed by `all'. Stop.

Thanks, Jose. "Jose E. Roman" writes: > Update the SLEPc repository and try again. > When a change in petsc-master affects SLEPc, you have to allow one or two > days for us to re-synchronize. > Jose > >> El 9 mar 2018, a las 3:59, Samuel Lanthaler

Re: [petsc-users] make: *** No rule to make target `chk_makej', needed by `all'. Stop.

Ah, now I undestood what you meant... sorry. Thank you, Jose! On 08.03.2018 22:26, Jed Brown wrote: Thanks, Jose. "Jose E. Roman" writes: Update the SLEPc repository and try again. When a change in petsc-master affects SLEPc, you have to allow one or two days for us to

Re: [petsc-users] make: *** No rule to make target `chk_makej', needed by `all'. Stop.

Update the SLEPc repository and try again. When a change in petsc-master affects SLEPc, you have to allow one or two days for us to re-synchronize. Jose > El 9 mar 2018, a las 3:59, Samuel Lanthaler escribió: > > Hi, > > I've just been trying to compile SLEPC on a

Re: [petsc-users] make: *** No rule to make target `chk_makej', needed by `all'. Stop.

Thanks, Jose. I actually tried that before, but it turns out there probably was some kind of an issue already with the compilation of petsc; even though it looked like it had worked. Trying again, now. Thanks, Samuel On 08.03.2018 22:14, Jose E. Roman wrote: Update the SLEPc repository and

Re: [petsc-users] [petsc-maint] how to check if cell is local owned in DMPlex

On 18-03-07 03:54 PM, Jed Brown wrote: Danyang Su writes: Based on my test, this function works fine using current PETSc-dev version, but I cannot get it compiled correctly using other versions for Fortran code, as mentioned in the previous emails. I asked this question

Re: [petsc-users] Inertia of Hermitian Matrix

You can verify there is a generalization of the inertia theorem thanks to Ikramov. Furthermore, recall the inertia theorem is about eigenvalues; for a Hermitian matrix, you can diagonalize it in a form that has real entries, and that preserves the eigenvalues. Of course, being able to apply the

Re: [petsc-users] PETSC_VIEWER_DRAW_(Comm) Fortran interface missing?

Great! I've merged balay/ftn-VIEWER_DRAW/maint to 'maint' Satish On Thu, 8 Mar 2018, Tim Steinhoff wrote: > Yeah, thanks Satish. > PETSC_VIEWER_DRAW_() works perfectly and I could not reproduce my > above mentioned issue with PETSC_VIEWER_STDOUT_(), so probably I > messed something up. > Thanks