doc: update doi for PETSc users manual

!7005 stopped make docs from erroring on some errors in the manual pages. This now returns the erroring out

Reported-by: Satish Balay

Update file petsc.bib

DMDASNES: support using user context if operation context is not provided

Add MPI_Allreduce inside the main objective driver

Clarify when 64 bit BLAS/LAPACK integers are used.

Reported-by: Gerard Henry <gerard.henry@fresnel.fr>

Merge remote-tracking branch 'origin/release'

Whitelist MKL [C]PARDISO/SuperLU_DIST to be listed in manpages

SNESNEWTONTR: code improvements

support QN models

accepts Cauchy point if it is on the boundary

Enlarge trust region only if direction is on the boundary

Use previously estimated largest eigenval

SNESNEWTONTR: code improvements

support QN models

accepts Cauchy point if it is on the boundary

Enlarge trust region only if direction is on the boundary

Use previously estimated largest eigenvalue of hessian in minimum decrease

Customize trust region norm

Fix dogleg path computation

Update output files and add tests

show more ...

MATLMVM: must call reset if history size changes

PCLMVM: support automatic updates and operators of type MATLMVM

Merge branch 'hdf5-1.14.0' into 'main'

HDF5 1.14.3

See merge request petsc/petsc!6116

drop support for MED files

Fix PetscOptionsGetViewer() so it works in a thread-safe way

When PetscOptionsGetViewer() returns, for example, PETSC_VIEWER_STDOUT_SELF the same object is shared
by all threads that call PetscOptio

Fix PetscOptionsGetViewer() so it works in a thread-safe way

When PetscOptionsGetViewer() returns, for example, PETSC_VIEWER_STDOUT_SELF the same object is shared
by all threads that call PetscOptionsGetViewer(). In the previous code PetscObjectReference() and
dereference (via PetscViewerDestroy() where called on the viewer by multiple threads after the viewer
was accessed thus corrupting the object.

This branch introduces a PetscOptionsRestoreViewer() that allows not doing the referencing and dereferencing
on persistant viewers, thus removing the specific race condition above.

Other possible solutions include

Use a lock on each PetscObjectReference/Dereference() just in case they are shared. Could be time consuming so one
could mark each object as either threadshared or independent and only do the locks on threadshared objects. This lowers
the cost but would require more extensive changes to PETSc infrastructure. And I do not know if this shared/not shared model
is what we need in the long run, though it might be.

show more ...

Merge remote-tracking branch 'origin/release'

Merge branch 'jolivet/housekeeping' into 'release'

Minor housekeeping

See merge request petsc/petsc!7075

Merge branch 'barry/2023-11-28/doc-petsccall-vs-petscassert/release' into 'release'

Clarify in the manual pages the use of PetscCheck() vs PetscAssert()

See merge request petsc/petsc!7066

Clarify in the manual pages the use of PetscCheck() vs PetscAssert()

Minor housekeeping

Merge branch 'release'

Increase patchlevel to 3.20.2

Merge remote-tracking branch 'origin/release'

Merge branch 'barry/2023-11-22/fix-some-manualpages/release' into 'release'

Improve SNES manual pages

See merge request petsc/petsc!7049

Fix some manual pages focusing on SNES

Merge remote-tracking branch 'origin/release'

Change ./configure arguments to speed up compile of PETSc for petsc4py docs