#include "petscdmda.h"
PetscErrorCode DMDACreate3d(MPI_Comm comm,DMBoundaryType bx,DMBoundaryType by,DMBoundaryType 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)
Collective on MPI_Comm
| comm | - MPI communicator | |
| bx,by,bz | - type of ghost nodes the array have. Use one of DM_BOUNDARY_NONE, DM_BOUNDARY_GHOSTED, DM_BOUNDARY_PERIODIC. | |
| stencil_type | - Type of stencil (DMDA_STENCIL_STAR or DMDA_STENCIL_BOX) | |
| M,N,P | - global dimension in each direction of the array | |
| m,n,p | - corresponding number of processors in each dimension (or PETSC_DECIDE to have calculated) | |
| dof | - number of degrees of freedom per node | |
| s | - stencil width | |
| lx, ly, lz | - arrays containing the number of nodes in each cell along the x, y, and z coordinates, or NULL. If non-null, these must be of length as m,n,p and the corresponding m,n, or p cannot be PETSC_DECIDE. Sum of the lx[] entries must be M, sum of the ly[] must N, sum of the lz[] must be P |
| -dm_view | - Calls DMView() at the conclusion of DMDACreate3d() | |
| -da_grid_x <nx> | - number of grid points in x direction | |
| -da_grid_y <ny> | - number of grid points in y direction | |
| -da_grid_z <nz> | - number of grid points in z direction | |
| -da_processors_x <MX> | - number of processors in x direction | |
| -da_processors_y <MY> | - number of processors in y direction | |
| -da_processors_z <MZ> | - number of processors in z direction | |
| -da_refine_x <rx> | - refinement ratio in x direction | |
| -da_refine_y <ry> | - refinement ratio in y direction | |
| -da_refine_z <rz> | - refinement ratio in z directio | |
| -da_refine <n> | - refine the DMDA n times before creating it |
The array data itself is NOT stored in the DMDA, it is stored in Vec objects; The appropriate vector objects can be obtained with calls to DMCreateGlobalVector() and DMCreateLocalVector() and calls to VecDuplicate() if more are needed.
You must call DMSetUp() after this call before using this DM.
If you wish to use the options database to change values in the DMDA call DMSetFromOptions() after this call but before DMSetUp().