Creates a new PetscViewer (same type as the old) that lives on a subcommunicator of the original viewer’s communicator


#include "petscviewer.h" 
PetscErrorCode PetscViewerGetSubViewer(PetscViewer viewer, MPI_Comm comm, PetscViewer *outviewer)


Input Parameters#

  • viewer - the PetscViewer to be reproduced

  • comm - the sub communicator to use

Output Parameter#


The output of the subviewers is synchronized against the original viewer. For example, if a viewer on two MPI processes is decomposed into two subviewers, the output from the first viewer is all printed before the output from the second viewer.

Call PetscViewerRestoreSubViewer() to destroy this PetscViewer, NOT PetscViewerDestroy()

This is most commonly used to view a sequential object that is part of a parallel object. For example PCView() on a PCBJACOBI could use this to obtain a PetscViewer that is used with the sequential KSP on one block of the preconditioner.

PetscViewerFlush() is run automatically at the beginning of PetscViewerGetSubViewer() and with PetscViewerRestoreSubViewer() for PETSCVIEWERASCII

PETSCVIEWERDRAW and PETSCVIEWERBINARY only support returning a singleton viewer on MPI rank 0, all other ranks will return a NULL viewer

Must be called by all MPI processes that share viewer, for processes that are not of interest you can pass PETSC_COMM_SELF.

For PETSCVIEWERASCII the viewers behavior is as follows:

  Recursive calls are allowed
  A call to `PetscViewerASCIIPrintf()` on a subviewer results in output for the first MPI process in the `outviewer` only
  Calls to  `PetscViewerASCIIPrintf()` and `PetscViewerASCIISynchronizedPrintf()` are immediately passed up through all
  the parent viewers to the higher most parent with `PetscViewerASCIISynchronizedPrintf()` where they are immediately
  printed on the first MPI process or stashed on the other processes.
  At the higher most `PetscViewerRestoreSubViewer()` the viewer is automatically flushed with `PetscViewerFlush()`

Developer Notes#

There is currently incomplete error checking to ensure the user does not use the original viewer between the the calls to PetscViewerGetSubViewer() and PetscViewerRestoreSubViewer(). If the user does there could be errors in the viewing that go undetected or crash the code.

Complex use of this functionality with PETSCVIEWERASCII can result in output in unexpected order. This seems unavoidable.

See Also#

Viewers: Looking at PETSc Objects, PetscViewer, PetscViewerSocketOpen(), PetscViewerASCIIOpen(), PetscViewerDrawOpen(), PetscViewerFlush(), PetscViewerRestoreSubViewer()








PetscViewerGetSubViewer_ASCII() in src/sys/classes/viewer/impls/ascii/filev.c
PetscViewerGetSubViewer_Binary() in src/sys/classes/viewer/impls/binary/binv.c
PetscViewerGetSubViewer_Draw() in src/sys/classes/viewer/impls/draw/drawv.c
PetscViewerGetSubViewer_String() in src/sys/classes/viewer/impls/string/stringv.c

Index of all Viewer routines
Table of Contents for all manual pages
Index of all manual pages