Re: [petsc-users] ghost points, DMs, and vector operations

gideon.simp...@gmail.com writes: > Yes, when I was talking about vector operations, i.e., VecAXPY, I was doing > them on the global vectors. So what I'm understanding from you is that the > ghost points only appear after I go to the local data structure, is that > correct? The concept

Re: [petsc-users] ghost points, DMs, and vector operations

Yes, when I was talking about vector operations, i.e., VecAXPY, I was doing them on the global vectors. So what I'm understanding from you is that the ghost points only appear after I go to the local data structure, is that correct? -gideon > On Feb 25, 2017, at 12:30 AM, Jed Brown

Re: [petsc-users] ghost points, DMs, and vector operations

Gideon Simpson writes: > I’ve got a simple problem where I use a DM to handle a representation of a > vector complex numbers, storing the real and imaginary components at each > lattice point. I also have ghost points at either end, i.e.: > > DMDACreate1d

[petsc-users] ghost points, DMs, and vector operations

I’ve got a simple problem where I use a DM to handle a representation of a vector complex numbers, storing the real and imaginary components at each lattice point. I also have ghost points at either end, i.e.: DMDACreate1d (PETSC_COMM_WORLD, DM_BOUNDARY_GHOSTED, N, 2 , 1 , NULL, ) ; I have a

Re: [petsc-users] consider an error message as a petscinfo??

Thanks a lot for your explanation, Barry, This makes sense! Fande, On Fri, Feb 24, 2017 at 1:56 PM, Barry Smith wrote: > > Fande, > > Yes. Say one is doing a timestepping and using a direct solver. With > time stepping we do not want to necessarily stop (in fact we

Re: [petsc-users] consider an error message as a petscinfo??

Fande, Yes. Say one is doing a timestepping and using a direct solver. With time stepping we do not want to necessarily stop (in fact we almost never) on a failed solve (due to for example a failed factorization). We want the code to continue up the stack until it gets to the time

[petsc-users] consider an error message as a petscinfo??

Hi All, In MatSolve(), there is a piece of code: * if (mat->errortype) {ierr = PetscInfo1(mat,"MatFactorError %D\n",mat->errortype);CHKERRQ(ierr);ierr = VecSetInf(x);CHKERRQ(ierr); } else {ierr = (*mat->ops->solve)(mat,b,x);CHKERRQ(ierr); }* If a direct solver such as LU or

Re: [petsc-users] python3 update

yes, though I don’t know if this breaks backwards compatibility with python2. -gideon > On Feb 24, 2017, at 1:26 PM, Barry Smith wrote: > > > Thanks, we'll get this into maint and master ASAP. > > >> On Feb 24, 2017, at 11:46 AM, Gideon Simpson

Re: [petsc-users] python3 update

Thanks, we'll get this into maint and master ASAP. > On Feb 24, 2017, at 11:46 AM, Gideon Simpson wrote: > > It appears the following modification to petsc_conf.py is sufficient to get > PetscBinaryIO.py working: > > change: > if os.environ.has_key('PETSC_DIR’):

[petsc-users] python3 update

It appears the following modification to petsc_conf.py is sufficient to get PetscBinaryIO.py working: change: if os.environ.has_key('PETSC_DIR’): to if 'PETSC_DIR' in os.environ: and if os.environ.has_key('PETSC_ARCH’): to if 'PETSC_ARCH' in os.environ: -gideon

Re: [petsc-users] understanding the LSC preconditioner

David Nolte writes: > At the moment it's not possible for me to rebuild python with the proper > configuration for valgrind (--without-pymalloc --with-valgrind). I'm not > sure how useful the output is now. I can't say I get it... you can find > it in the attachment, if you

Re: [petsc-users] understanding the LSC preconditioner

At the moment it's not possible for me to rebuild python with the proper configuration for valgrind (--without-pymalloc --with-valgrind). I'm not sure how useful the output is now. I can't say I get it... you can find it in the attachment, if you want to take a look. Valgrind crashes with the