Developing PETSc Documentation

General Guidelines

  • Good documentation should be like a bonsai tree: alive, on display, frequently tended, and as small as possible (adapted from these best practices).

  • Wrong, irrelevant, or confusing documentation is worse than no documentation.

Building Main Documentation

The documentation tools listed below (except for pdflatex) are automatically downloaded and installed by ./configure.

  • Sowing: a text processing tool developed by Bill Gropp. This produces the PETSc manual pages; see the Sowing documentation and Manual Page Format.

  • C2html: A text processing package. This generates the HTML versions of all the source code.

  • A version of pdflatex, for example in Tex Live. This package might already be installed on most systems. It is required to generate the users manual (part of the PETSc documentation).

Note: Sowing and c2html have additional dependencies like gcc, g++, and flex and do not use compilers specified to PETSc configure. [Windows users please install the corresponding cygwin packages]

Once pdflatex is in your PATH, you can build the documentation with:

make alldoc LOC=${PETSC_DIR}

(Note that this does not include Sphinx Documentation).

To get a quick preview of manual pages from a single source directory (mainly to debug the manual page syntax):

cd $PETSC_DIR/src/snes/interface
make LOC=$PETSC_DIR manualpages_buildcite
browse $PETSC_DIR/docs/manualpages/SNES/SNESCreate.html  # or suitable command to open the HTML page in a browser

Sphinx Documentation

The Sphinx documentation is currently not integrated into the main docs build as described in Building Main Documentation.

ReadTheDocs generates the documentation at from the PETSc Git repository.

Building the Sphinx docs locally

  • Make sure that you have a recent version of Python 3 and the required modules, as listed in the ReadTheDocs configuration file and requirements file for ReadTheDocs (we use a precise version of Sphinx to avoid issues with our custom extension to create inline links).

  • Navigate to the location of for the Sphinx docs (currently src/docs/sphinx_docs).

  • make html

  • Open _build/html/index.html with your browser.

Sphinx Documentation Guidelines

  • Use the includeliteral directive to directly include pieces of source code, as in the following example. Note that an “absolute” path has been used, which means relative to the root for the Sphinx docs (where is found).

.. literalinclude:: /../../../src/sys/error/err.c
   :language: c
   :start-at: PetscErrorCode PetscError(
   :end-at: PetscFunctionReturn(0)
   :append: }