Mention linear regressor in KSP docs and KSP usage from linear regressor
Add initial version PetscRegressor, part of the planned machine learning (ML) toolkitCo-authored-by: Mr. Hong Zhang <hongzhang@anl.gov>Co-authored-by: Hansol Suh <hsuh@anl.gov>Co-authored-by: Bar
Add initial version PetscRegressor, part of the planned machine learning (ML) toolkitCo-authored-by: Mr. Hong Zhang <hongzhang@anl.gov>Co-authored-by: Hansol Suh <hsuh@anl.gov>Co-authored-by: Barry Smith <bsmith@petsc.dev>Co-authored-by: Toby Isaac <toby.isaac@gmail.com>Co-authored-by: Satish Balay <balay@mcs.anl.gov>Mr. Hong Zhang developed the petsc4py interface and examples.Hansol Suh provided extensive help with updating the code to the latest PETSc coding guidelines and APIs, some documentation development, getting documentation to build correctly, getting new tests into the test harness, and numerous big fixes plus minor changes.Barry Smith provided extensive feedback and code to get the Fortran interfaces and documentation build working.Toby Isaac provided a fix to prevent breakage with complex-arithmetic builds.Satish Balay provided important help with fixing builds.Thanks-to: Pierre Jolivet <pierre@joliv.et>Thanks-to: Jed Brown <jed@jedbrown.org>Thanks-to: Jose Roman <jroman@dsic.upv.es>Thanks-to: Stefano Zampini <stefano.zampini@gmail.com>Pierre, Jed, Jose, and Stefano provided extremely helpful feedback and suggestions during the merge review process.
show more ...
Convert manualpages/*.rst to manualpages/*.md files
Merge remote-tracking branch 'origin/release'
docs: Add user manual documentation of PetscSection
Fortran 90: fully embrace After 34 years!- deprecate use of 'F90' in Fortran function names- use Fortran pointers when appropriate- the new Fortran API is not backward compatible with previous ve
Fortran 90: fully embrace After 34 years!- deprecate use of 'F90' in Fortran function names- use Fortran pointers when appropriate- the new Fortran API is not backward compatible with previous versions!- also clean up inconsistent PETSc code detected by new Fortran generation tools- drop use of bfort- automatically generate all the Fortran PETSc objects, enums etc from the include files- generate most of the Fortran interface definitions and functions from the source code- simplify the number and organization of Fortran modulesCo-authored-by: Jose E. Roman <jroman@dsic.upv.es>
Improve discussions of Fortran in API docs, in particular adding very useful...
Organize the Mat coloring, partitioning, coarsening, and ordering in a common directoryunder the SUBMANSEC of MatGraphOperations instead of MatOrderingsCommit-type: housekeeping
Move doc/classic materials to doc/manualpagesUpdate scripts and makefiles to process them in the new locations
Merge branch 'main-patch-bf88' into 'main'Update file Optimization.rstSee merge request petsc/petsc!6179
Update file System.rst
Update file Optimization.rst
Have PETSc's website include petsc4py API docPut slightly more mention of petsc4py in websiteTODO: improve website presentation and introduction to petsc4pyCommit-type: documentationThanks-to:
Have PETSc's website include petsc4py API docPut slightly more mention of petsc4py in websiteTODO: improve website presentation and introduction to petsc4pyCommit-type: documentationThanks-to: Satish BalayDevelopment Tools: Vim, Emacs, Eclipse
Web: Fix API TOC
Remove confusing and un-need docs directory that contains manualCommit-type: housekeeping