[petsc-users] object name overwritten in VecView

2018-02-27 Thread Danyang Su
Hi All, How to set different object names when using multiple VecView? I try to use PetscObjectSetName with multiple output, but the object name is overwritten by the last one. As shown below, as well as the enclosed files as example, the vector name in sol.vtk is vec_v for both vector u

Re: [petsc-users] Malloc error with 'correct' preallocation?

2018-02-27 Thread Smith, Barry F.
> On Feb 27, 2018, at 7:05 PM, Appel, Thibaut wrote: > > Dear PETSc developers and users, > > I am forming a sparse matrix in complex, double precision arithmetic and > can’t understand why I have «PETSC ERROR: Argument out of range - New nonzero > at (X,X) caused

[petsc-users] Malloc error with 'correct' preallocation?

2018-02-27 Thread Appel, Thibaut
Dear PETSc developers and users, I am forming a sparse matrix in complex, double precision arithmetic and can’t understand why I have «PETSC ERROR: Argument out of range - New nonzero at (X,X) caused a malloc» during the assembly of the matrix. This matrix discretizes a PDE in 2D using a

Re: [petsc-users] [SLEPc] Performance of Krylov-Schur with MUMPS-based shift-and-invert

2018-02-27 Thread Thibaut Appel
Good afternoon Mr Roman, Thank you very much for your detailed and quick answer. I'll make the use of eps_view and log_view and see if I can optimize the preallocation of my matrix. Good to know that it is possible to play with the "mpd" parameter, I thought it was only for when large

Re: [petsc-users] Compiling problem after upgrading to PETSc 3.8.3

2018-02-27 Thread Smith, Barry F.
What optimization level that generates correct code depends on the compiler, its version and even sub-version. We stumble across compilers that generate bad code with optimization fairly often. If -O3 works, great but often -O2 is the best one can use. Barry > On Feb 27, 2018, at 7:01

Re: [petsc-users] Compiling problem after upgrading to PETSc 3.8.3

2018-02-27 Thread TAY wee-beng
On 23/2/2018 1:40 AM, Smith, Barry F. wrote: First run under valgrind to look for memory issues. Second I would change 1 thing at a time. So use the intel 2017 compiler with PETSc 2.8.3 so the only change is your needed changes to match 2.8.3 and does not include a compiler change.