February 2011 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] PCCreate_BFBt has no manual page
by Barry Smith 27 Feb '11

27 Feb '11

On Feb 27, 2011, at 4:24 AM, Jed Brown wrote: > BFBt should be compared to LSC. Any functionality missing in LSC should be added, then BFBt should be removed. This exact text could go into the manual page. The problem now is that this information is in only one location (your head) and no one else knows if 1) BFBt is orthogonal to to lsc 2) BFBt is the replacement to lsc 3) BFBt is to be replaced with lsc. without consulting you. That's not a good model for software maintenance. Barry > > >> On Feb 27, 2011 4:55 AM, "Barry Smith" <bsmith(a)mcs.anl.gov> wrote: >> >> >> PCCreate_BFBt has no manual page WTF? >> >> Barry >> >

1 0

Re: [petsc-dev] PCCreate_BFBt has no manual page
by Jed Brown 27 Feb '11

27 Feb '11

BFBt should be compared to LSC. Any functionality missing in LSC should be added, then BFBt should be removed. On Feb 27, 2011 4:55 AM, "Barry Smith" <bsmith(a)mcs.anl.gov> wrote: PCCreate_BFBt has no manual page WTF? Barry

1 0

PCCreate_BFBt has no manual page
by Barry Smith 26 Feb '11

26 Feb '11

PCCreate_BFBt has no manual page WTF? Barry

1 0

Re: [petsc-dev] Overzealous guards in DMGetInjection_DA
by Barry Smith 25 Feb '11

25 Feb '11

On Feb 21, 2011, at 3:37 PM, Jed Brown wrote: > ierr = DMDAGetInfo(dac,&dimc,&Mc,&Nc,&Pc,&mc,&nc,&pc,&dofc,&sc,&wrapc,&stc);CHKERRQ(ierr); > ierr = DMDAGetInfo(daf,&dimf,&Mf,&Nf,&Pf,&mf,&nf,&pf,&doff,&sf,&wrapf,&stf);CHKERRQ(ierr); > if (dimc != dimf) SETERRQ2(((PetscObject)daf)->comm,PETSC_ERR_ARG_INCOMP,"Dimensions of DMDA do not match %D %D",dimc,dimf);CHKERRQ(ierr); > if (dofc != doff) SETERRQ2(((PetscObject)daf)->comm,PETSC_ERR_ARG_INCOMP,"DOF of DMDA do not match %D %D",dofc,doff);CHKERRQ(ierr); > if (sc != sf) SETERRQ2(((PetscObject)daf)->comm,PETSC_ERR_ARG_INCOMP,"Stencil width of DMDA do not match %D %D",sc,sf);CHKERRQ(ierr); > if (wrapc != wrapf) SETERRQ(((PetscObject)daf)->comm,PETSC_ERR_ARG_INCOMP,"Periodic type different in two DMDAs");CHKERRQ(ierr); > if (stc != stf) SETERRQ(((PetscObject)daf)->comm,PETSC_ERR_ARG_INCOMP,"Stencil type different in two DMDAs");CHKERRQ(ierr); > if (Mc < 2) SETERRQ(PETSC_COMM_SELF,PETSC_ERR_ARG_OUTOFRANGE,"Coarse grid requires at least 2 points in x direction"); > if (dimc > 1 && Nc < 2) SETERRQ(PETSC_COMM_SELF,PETSC_ERR_ARG_OUTOFRANGE,"Coarse grid requires at least 2 points in y direction"); > if (dimc > 2 && Pc < 2) SETERRQ(PETSC_COMM_SELF,PETSC_ERR_ARG_OUTOFRANGE,"Coarse grid requires at least 2 points in z direction"); > > Several of these are not necessary. DMGetInjection_DA_3D: > > ierr = DMDAGetInfo(dac,0,&Mx,&My,&Mz,0,0,0,0,0,&pt,0);CHKERRQ(ierr); > ierr = DMDAGetInfo(daf,0,&mx,&my,&mz,0,0,0,&dof,0,0,0);CHKERRQ(ierr); > > Seems silly to fail when not necessary. I'm inclined to move the guards into the specific implementation so that only the necessary amount of consistency needs to be checked. How about getting rid of DMGetInjection_DA entirely and just set the appropriate ops slot? Right. Feel free to split it apart into the separate functions that go into the slot and remove the DMGetInjection_DA It is just of this style because it was coded before DM was a gleam in my eye and needs refactoring Barry

1 0

Re: [petsc-dev] Preconditioner side
by Hong Zhang 25 Feb '11

25 Feb '11

-ksp_preconditioner_side <LEFT> (choose one of) LEFT RIGHT SYMMETRIC (KSPSetPCSide) Hong On Fri, Feb 25, 2011 at 9:10 AM, Desire NUENTSA WAKAM <desire.nuentsa_wakam(a)inria.fr> wrote: > Hi all, > what's the current command-line option to set the preconditioner side in > PETSc-dev? > It seems not to be -ksp_right_pc as for PETSc-users > nor -ksp_pc_side as written in KSPSetPCSide doc. > Thanks > Désiré >

1 0

Preconditioner side
by Desire NUENTSA WAKAM 25 Feb '11

25 Feb '11

Hi all, what's the current command-line option to set the preconditioner side in PETSc-dev? It seems not to be -ksp_right_pc as for PETSc-users nor -ksp_pc_side as written in KSPSetPCSide doc. Thanks Dï¿½sirï¿½

1 0

Re: [petsc-dev] Recent changeset confuses the heck of intel compilers
by Blaise Bourdin 24 Feb '11

24 Feb '11

It's working fine now. thanks Blaise On Feb 24, 2011, at 4:53 PM, Jed Brown wrote: > On Thu, Feb 24, 2011 at 23:41, Blaise Bourdin <bourdin(a)lsu.edu> wrote: > It's still not happy... > > Damn, every other manual says that is the way to indicate that you want assignment as a truth value. Could you try again, please. -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin

1 0

Re: [petsc-dev] Recent changeset confuses the heck of intel compilers
by Jed Brown 24 Feb '11

24 Feb '11

On Thu, Feb 24, 2011 at 23:41, Blaise Bourdin <bourdin(a)lsu.edu> wrote: > It's still not happy... Damn, every other manual says that is the way to indicate that you want assignment as a truth value. Could you try again, please.

1 0

Re: [petsc-dev] Recent changeset confuses the heck of intel compilers
by Blaise Bourdin 24 Feb '11

24 Feb '11

Jed, It's still not happy... Blaise On Feb 24, 2011, at 4:36 PM, Jed Brown wrote: > On Thu, Feb 24, 2011 at 23:25, Blaise Bourdin <bourdin(a)lsu.edu> wrote: > Changeset f301815fc494cb333d15c0cefabf71a0988a0321 (rev 18363) seems to confuse the intel compilers (I tested 11.1 on linux x86_64 and mac OS X). After updating past this point, I get tons of warnings like > drawv.c(397): warning #187: use of "=" where "==" may have been intended > > The assignment is intentional, I added an extra set of parens which should satisfy even the Intel compiler. Let me know if it doesn't. -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin

1 0

Re: [petsc-dev] Recent changeset confuses the heck of intel compilers
by Jed Brown 24 Feb '11

24 Feb '11

On Thu, Feb 24, 2011 at 23:25, Blaise Bourdin <bourdin(a)lsu.edu> wrote: > Changeset f301815fc494cb333d15c0cefabf71a0988a0321 (rev 18363) seems to > confuse the intel compilers (I tested 11.1 on linux x86_64 and mac OS X). > After updating past this point, I get tons of warnings like > drawv.c(397): warning #187: use of "=" where "==" may have been intended > The assignment is intentional, I added an extra set of parens which should satisfy even the Intel compiler. Let me know if it doesn't.

1 0