Update the use of Collective on in the manual pages to reflect the new styleCommit-type: style-fix, documentationThanks-to: Patrick Sanan <patrick.sanan@gmail.com>
Man pages: remove Concepts: fieldsThese fields were previously stripped from the man pages by logic removed in 21a59cba2737d49dc2f0bd12c08db0d2a3f3f209Remove these fields from all man pages (but
Man pages: remove Concepts: fieldsThese fields were previously stripped from the man pages by logic removed in 21a59cba2737d49dc2f0bd12c08db0d2a3f3f209Remove these fields from all man pages (but not from examples).This is accomplished with GNU sed (gsed on OS X), with the following commands.*Warning* that this type of command can corrupt a .git directory,so be cautious in reusing or modifying these commands. They first lookfor and delete matching lines with a following line consisting of only whitespace,and then delete any remaining matching lines. find src -type f -not -path "*/examples/*" -not -name "*.html" -not -name "*.bib" -exec gsed -i '/Concepts:/ {N; /\n\s*$/d}' {} + find src -type f -not -path "*/examples/*" -not -name "*.html" -not -name "*.bib" -exec gsed -i '/Concepts:/d' {} + find include -type f -not -path "*/examples/*" -not -name "*.html" -not -name "*.bib" -exec gsed -i '/Concepts:/ {N; /\n\s*$/d}' {} + find include -type f -not -path "*/examples/*" -not -name "*.html" -not -name "*.bib" -exec gsed -i '/Concepts:/d' {} +Hints on the sed command obtained from: https://unix.stackexchange.com/questions/100754/how-to-delete-a-specific-line-and-the-following-blank-line-using-gnu-sed
show more ...
Man pages: remove .keywords: fieldsThis field is recognized by doctext from Sowing (http://wgropp.cs.illinois.edu/projects/software/sowing/doctext/node20.htm#Node20),but it doesn't seem to be unif
Man pages: remove .keywords: fieldsThis field is recognized by doctext from Sowing (http://wgropp.cs.illinois.edu/projects/software/sowing/doctext/node20.htm#Node20),but it doesn't seem to be uniformly used or maintained.Thus, remove all .keywords: fields, and a following blank line, if present.This is accomplished with GNU sed (gsed on OS X), with the following commands.*Warning* that this type of command can corrupt a .git directory,so be cautious in reusing or modifying these commands. They first lookfor and delete matching lines with a following line consisting of only whitespace,and then delete any remaining matching lines. find src/ -type f -exec gsed -i '/keywords:/ {N; /\n\s*$/d}' {} + find src/ -type f -exec gsed -i '/keywords:/d' {} + find include/ -type f -exec gsed -i '/keywords:/ {N; /\n\s*$/d}' {} + find include/ -type f -exec gsed -i '/keywords:/d' {} +Hints on the sed command obtained from: https://unix.stackexchange.com/questions/100754/how-to-delete-a-specific-line-and-the-following-blank-line-using-gnu-sed
Work on PetscViewerString. Fix use of PetscInt -> size_t, add new functionality, add usage by basic solver objects, add test caseCommit-type: style-fix, feature, documentation, example
Revert the function name where it is referenced
Improve the error propagation between and within KSPs and PCs- Added KSPCheckSolve() to be called consistently by PCs to set failures if the inner solvers fail.- Added use of KSPCheckNorm() and KS
Improve the error propagation between and within KSPs and PCs- Added KSPCheckSolve() to be called consistently by PCs to set failures if the inner solvers fail.- Added use of KSPCheckNorm() and KSPCheckDot() to all the Krylov methods to propagate errors from PCs to the KSPs.Commit-type: feature
Changed VecScatterCreate() to take a communicator and return scatter as other first class PETSc objects do.Changed old VecScatterCreate() to VecScatterCreateWithData()Completed basic refactorizati
Changed VecScatterCreate() to take a communicator and return scatter as other first class PETSc objects do.Changed old VecScatterCreate() to VecScatterCreateWithData()Completed basic refactorization of VecScatter code, ready for new implementations to be added.(There is still some code duplication between the VecScatter MPI1 and MPI3 code but it can be fixed at anytime without requiring changes to the VecScatter API.Part 5 of a refactorization of VecScatter to be treated as a first class PETSc objectCommit-type: style-fix
Merge branch 'maint'
Fix PCApplyTranspose_ASM() that accidently changed KSPSolveTranspose() to KSPSolve()Commit-type: bug-fixReported-by: Marshall Galbraith
Log: various fixes and cleanups- Reorganize declarations in petsclog.h- Better -log_exclude, now applies to all registered stages- Minor fixes to implementation of -info_exclude- PCASM: Log appl
Log: various fixes and cleanups- Reorganize declarations in petsclog.h- Better -log_exclude, now applies to all registered stages- Minor fixes to implementation of -info_exclude- PCASM: Log apply-on-blocks KSP solves- Rename PetscLogDestroy() -> PetscLogFinalize() and hide it from the API
Man pages: add newlines after "Notes:"This allows for proper formatting from sowing.On OS X (using gsed, not the default BSD sed), from the PETSc root directory: find src include -type f \(
Man pages: add newlines after "Notes:"This allows for proper formatting from sowing.On OS X (using gsed, not the default BSD sed), from the PETSc root directory: find src include -type f \( -name "*.c" -or -name "*.h" -or -name "*.cxx" \) | xargs gsed -i 's/Notes\s*:\s*\(\w.*\)/Notes:\n \1/'This adds a newline and 4 spaces whenever "Notes:" is followed by any "word" character, in any .c, .h, or .cxx file in src/ or include/
Merge remote-tracking branch 'origin/knepley/fix-fe-vector-spaces'* origin/knepley/fix-fe-vector-spaces: (21 commits) SNES ex12: Updated test output Plex ex8: Updated test output Plex ex7: Up
Merge remote-tracking branch 'origin/knepley/fix-fe-vector-spaces'* origin/knepley/fix-fe-vector-spaces: (21 commits) SNES ex12: Updated test output Plex ex8: Updated test output Plex ex7: Updated test output Plex ex5: Updated test output Plex ex4: Updated test output Plex ex3: Updated test output Plex ex20: Updated test output Plex ex19: Updated test output Plex ex18: Updated test output Plex ex17: Updated test output Plex ex16: Updated test output Plex ex13: Updated test output Plex ex12: Updated test output Plex ex1: Updated test output DualSpace: Interaction of branches FAS: Added viewing during coarse correction Plex+FEM: Fixes for reorg of vector spaces which I missed - Fixed DMPlexComputeInterpolatorNested() field offsets - Fixed DMPlexComputeInjector() PetscFE: Fixed viewers - Added PetscDualSpace viewer - Can view FE without quadrature PC: Added some options and documentation for BJacobi, ASM, Richardson Plex: Fixes for ASCII viewer ...
Add MatGetOperation() and fixes to MATSHELL
PC: Added some options and documentation for BJacobi, ASM, Richardson
More variables not declared at start of scopeCommit-type: portability-fixReported-by: nightly tests
Declaration of variable not at beginning of code blockCommit-type: portability-fix
Remove C++ comments, format comments and codeCommit-type: bug-fixReported-by: Stefano ZampiniThanks-to: Eugenio Aulisa
Removed unused data members from struct PC_ASM
PC_ASM with improved global to local communication
moving to PC_ASM with one pre and post syncronization
Merge branch 'maint' into eugenio
PC_ASM added lprolongation and changed multiplicative
Revert last commit since it breaks examplesCommit-type: bug-fixReported-by: nightly tests
Fix problem with multiplicative local additive SchwarzText and fix provided by Eugenio AulisaReason. The problem arises if in the overlapping index sets ghost nodes are presents.If this is the ca
Fix problem with multiplicative local additive SchwarzText and fix provided by Eugenio AulisaReason. The problem arises if in the overlapping index sets ghost nodes are presents.If this is the case the vectors osm->lx and osm->ly (built immediately after)not only will include the dofs owned by the process, but also the ghost dofs.This creates vectors whose sizes differ from vec usedto generate the prolongation scatter object at line 379.Thus the error at line 519 when trying to use the interpolation object with osm->ly vector.The fix basically concatenates all the own index sets, which do not include ghost nodes.Then the local sizes of vec, osm->lx and osm->ly are all the same.Is this the best/only fix? Not sure.While it works for the Poisson example I generated for you, it still has "convergence" issues withmore sophisticated FSI problems I am working to, where the additive case works well.Moreover also in the Poisson example I built for you, the additive case works better.Considerations:1) instead of adapting osm->lx and osm->ly to the size of vec, it may be the case of doing the opposite.2) I am somehow concerned that the presence of ghost nodes may somehow alter the scatter, but to justify thisI need to study the alghorithm much more in detail.Add some missing error checkingCommit-type: bug-fixReported-by: Eugenio Aulisa <Eugenio.Aulisa@ttu.edu>
Typo in manual pageCommit-type: documentationReported-by: Peter Meisrimel <peter.meisrimel@na.lu.se>
12345678910>>...14