petsc-3.7.1 2016-05-15
Report Typos and Errors

# PCTELESCOPE

Runs a KSP solver on a sub-group of processors. MPI processes not in the sub-communicator are idle during the solve.

### Options Database

| -pc_telescope_reduction_factor <n> | - factor to use communicator size by, for example if you are using 64 MPI processes and Many bruse an n of 4, the new sub-communicator will be 4 defined with 64/4 processes Many br
| -pc_telescope_ignore_dm <false> | - flag to indicate whether an attached DM should be ignored Many br

Many br

### Notes

The preconditioner is deemed telescopic as it only calls KSPSolve() on a single Many brsub-communicator in contrast with PCREDUNDANT which calls KSPSolve() on N sub-communicators. Many brThis means there will be MPI processes within c, which will be idle during the application of this preconditioner. Many br

The default KSP is PREONLY. If a DM is attached to the PC, it is re-partitioned on the sub-communicator. Many brBoth the B mat operator and the right hand side vector are permuted into the new DOF ordering defined by the re-partitioned DM. Many brCurrently only support for re-partitioning a DMDA is provided. Many brAny nullspace attached to the original Bmat operator are extracted, re-partitioned and set on the repartitioned Bmat operator. Many brKSPSetComputeOperators() is not propagated to the sub KSP. Many brCurrently there is no support for the flag -pc_use_amat Many br

Assuming that the parent preconditioner (PC) is defined on a communicator c, this implementation Many brcreates a child sub-communicator (c') containing less MPI processes than the original parent preconditioner (PC). Many br

### Developer Notes

During PCSetup, the B operator is scattered onto c'. Many brWithin PCApply, the RHS vector (x) is scattered into a redundant vector, xred (defined on c'). Many brThen KSPSolve() is executed on the c' communicator. Many br

The communicator used within the telescoping preconditioner is defined by a PetscSubcomm using the INTERLACED Many brcreation routine. We run the sub KSP on only the ranks within the communicator which have a color equal to zero. Many br

The telescoping preconditioner is aware of nullspaces which are attached to the only B operator. Many brIn case where B has a n nullspace attached, these nullspaces vectors are extract from B and mapped into Many bra new nullspace (defined on the sub-communicator) which is attached to B' (the B operator which was scattered to c') Many br

The telescoping preconditioner is aware of an attached DM. In the event that the DM is of type DMDA (2D or 3D - Many br1D support for 1D DMDAs is not provided), a new DMDA is created on c' (e.g. it is re-partitioned), and this new DM Many bris attached the sub KSPSolve(). The design of telescope is such that it should be possible to extend support Many brfor re-partitioning other DM's (e.g. DMPLEX). The user can supply a flag to ignore attached DMs. Many br

By default, B' is defined by simply fusing rows from different MPI processes Many br

When a DMDA is attached to the parent preconditioner, B' is defined by: (i) performing a symmetric permuting of B Many brinto the ordering defined by the DMDA on c', (ii) extracting the local chunks via MatGetSubMatrices(), (iii) fusing the Many brlocally (sequential) matrices defined on the ranks common to c and c' into B' using MatCreateMPIMatConcatenateSeqMat() Many br

Limitations/improvements Many brVecPlaceArray could be used within PCApply() to improve efficiency and reduce memory usage. Many br

The symmetric permutation used when a DMDA is encountered is performed via explicitly assmbleming a permutation matrix P, Many brand performing P^T.A.P. Possibly it might be more efficient to use MatPermute(). I opted to use P^T.A.P as it appears Many brVecPermute() does not supported for the use case required here. By computing P, I can permute both the operator and RHS in a Many brconsistent manner. Many br

Mapping of vectors is performed this way Many brSuppose the parent comm size was 4, and we set a reduction factor of 2, thus would give a comm size on c' of 2. Many brUsing the interlaced creation routine, the ranks in c with color = 0, will be rank 0 and 2. Many brWe perform the scatter to the sub-comm in the following way, Many br[1] Given a vector x defined on comm c Many br

rank(c) : _________ 0 ______ ________ 1 _______ ________ 2 _____________ ___________ 3 __________ Many brx : [0, 1, 2, 3, 4, 5] [6, 7, 8, 9, 10, 11] [12, 13, 14, 15, 16, 17] [18, 19, 20, 21, 22, 23] Many br

scatter to xtmp defined also on comm c so that we have the following values Many br

rank(c) : ___________________ 0 ________________ _1_ ______________________ 2 _______________________ __3_ Many brxtmp : [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11] [ ] [12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23] [ ] Many br

The entries on rank 1 and 3 (ranks which do not have a color = 0 in c') have no values Many br

[2] Copy the value from rank 0, 2 (indices with respect to comm c) into the vector xred which is defined on communicator c'. Many brRanks 0 and 2 are the only ranks in the subcomm which have a color = 0. Many br

rank(c') : ___________________ 0 _______________ ______________________ 1 _____________________ Many brxred : [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11] [12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23] Many br

Contributed by Dave May Many br

### See Also

PCTelescopeGetKSP(), PCTelescopeGetDM(), PCTelescopeGetReductionFactor(), PCTelescopeSetReductionFactor(), PCTelescopeGetIgnoreDM(), PCTelescopeSetIgnoreDM(), PCREDUNDANT

Level:advanced
Location:src/ksp/pc/impls/telescope/telescope.c
Index of all PC routines
Table of Contents for all manual pages
Index of all manual pages