added..

satish

On Tue, 15 Mar 2011, Ethan Coon wrote:

> The fortran includes got screwed up somehow (likely by me...)
> 
> Fix below.
> 
> Ethan
> 
> diff -r 58c112bf6c29 include/finclude/petscdmda.h
> --- a/include/finclude/petscdmda.h    Mon Mar 14 16:30:42 2011 -0500
> +++ b/include/finclude/petscdmda.h    Tue Mar 15 10:47:34 2011 -0600
> @@ -20,9 +20,9 @@
>        PetscEnum DMDA_BOUNDARY_PERIODIC
>  
>        parameter (DMDA_BOUNDARY_NONE = 0)
> -      parameter (DMDA_BOUNDARY_GHOSTED = 0)
> -      parameter (DMDA_BOUNDARY_MIRROR = 0)
> -      parameter (DMDA_BOUNDARY_PERIODIC = 0)
> +      parameter (DMDA_BOUNDARY_GHOSTED = 1)
> +      parameter (DMDA_BOUNDARY_MIRROR = 2)
> +      parameter (DMDA_BOUNDARY_PERIODIC = 3)
>  
>  !
>  ! DMDAInterpolationType
> 
> 
> 
> 
> On Fri, 2011-03-11 at 09:29 -0700, Ethan Coon wrote:
> > On Thu, 2011-03-10 at 23:53 -0300, Lisandro Dalcin wrote:
> > > While updating petsc4py for the latest DMDA chages, and alto taking
> > > into account some new in NumPy C API related to neighborhood
> > > iterators,  I've got new idea. What about the API below?:
> > > 
> > > enum DMDABoundaryType:
> > >     DMDA_BOUNDARY_NONE = 0
> > >     DMDA_BOUNDARY_GHOSTED = 1
> > >     DMDA_BOUNDARY_MIRROR = 2
> > >     DMDA_BOUNDARY_PERIODIC = 4
> > > 
> > > PetscErrorCode DMDASetBoundaryType(DM dm, DMDABoundaryType bx,
> > > DMDABoundaryType by, DMDABoundaryType bz)
> > > 
> > > Changes for GHOSTED and PERIODIC should be easy
> > > (http://lkml.org/lkml/2000/8/25/132) ;-).
> > > 
> > > The new MIRROR boundary type could be implemented later.
> > > 
> > 
> > How does this fit into DMDACreate*D()?  Are you changing the create API
> > as well?
> > 
> > PetscErrorCode DMDACreate3d(MPI_Comm comm,DMDABoundaryType bx,
> > DMDABoundaryType by, DMDABoundaryType bz, DMDAStencilType
> > stencil_type,PetscInt M,PetscInt N,PetscInt P,PetscInt m,PetscInt
> > n,PetscInt p,PetscInt dof,PetscInt s,const PetscInt lx[],const PetscInt
> > ly[],const PetscInt lz[],DM *da)
> > 
> > 
> > Ethan
> > 
> > > 
> > > 
> > 
> 
> 


Reply via email to