add PetscAssert() and PetscAssertFalse()
make PetscInfo() variadic
SETERRQ[1-9]+ begone
Fix manpages: Argument --> Parameter (required to enable sowing checks)
Update badsource rules- Zero or more spaces are not allowed for more returning types- zero spaces not allowed for for|if|while
Remove all double blank lines from sourceCommit-type: petsc-style/2h
Linter using libClang that checks PetscValidHeaderSpecifcType, PetscValidHeaderSpecific, PetscValidHeader, PetscValid[XXX]Pointer, PetscValidType, PetscCheckSameComm, PetscValidLogicalCollectiveXXX f
Linter using libClang that checks PetscValidHeaderSpecifcType, PetscValidHeaderSpecific, PetscValidHeader, PetscValid[XXX]Pointer, PetscValidType, PetscCheckSameComm, PetscValidLogicalCollectiveXXX for validity. Automatically generates diff files for problems with a known solution.
show more ...
Documentation fixes
TSAdapt: no need to keep a working vector in the structjust use DM accessors.Not sure if we can move the glee->Y stuff up to the TSGLEE method.
Turn on checkbadSource test to generate an error when found; fix all source code that causes errorsCommit-type: portability-fix, testing-fix, style-fix, feature, maintainability/spend 1.5h
fix typos in DSP controller
Remove usage of PETSC_HAVE_FORTRAN_STDCALL, PETSC_BLASLAPACK_STDCALL, HAVE_FORTRAN_MIXED_STR_ARG flags - as Compaq f90 compiler is no longer supported
TSAdaptChoose_History: fix error message
TSADAPTDSP: Minor fixes to manual pages
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
adding support for GLEE methods to use local error controler when using GLEE adaptor; add testing with ex31.c; adding max ignore in the error calculationadding support for GLEE methods to use local
adding support for GLEE methods to use local error controler when using GLEE adaptor; add testing with ex31.c; adding max ignore in the error calculationadding support for GLEE methods to use local error controler when using GLEE adaptor; add testing with ex31.c; adding max ignore in the error calculationfixing some example output to match the new TSAdapt Viewercorrecting some hardwired values and adding a macro for repeated code
TSADAPTHISTORY: added API- set history from trajectory- inquire for initialization of time stepThe latter is needed because the initial time step may not be known to the user, and TSSolve adapts
TSADAPTHISTORY: added API- set history from trajectory- inquire for initialization of time stepThe latter is needed because the initial time step may not be known to the user, and TSSolve adapts only after the step is performed
Allow user to control the number of timesteps before an increase in timestep is allowed after failed solveThe default use to be hardwired at 4, now the default is 0 but under user controlCommit-t
Allow user to control the number of timesteps before an increase in timestep is allowed after failed solveThe default use to be hardwired at 4, now the default is 0 but under user controlCommit-type: featureReported-by: Sophie Blondel <sblondel@utk.edu>
TS: added TSADAPTHISTORY adaptor
Add if (*ierr) return checks for all Fortran stubs that utilize FREECHAR()Otherwise the ierr is overwritten by the FREECHAR() thus returning a zero error code when it should notCommit-type: bug-f
Add if (*ierr) return checks for all Fortran stubs that utilize FREECHAR()Otherwise the ierr is overwritten by the FREECHAR() thus returning a zero error code when it should notCommit-type: bug-fixReported-by: Tim Steinhoff <kandanovian@gmail.com>
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/
Fix typos and whitespaces already fixed in stefano_zampini/feature-continuousadjoint
TSADAPTDSP: New adaptive controller based on digital signal processing
TS: Add TSGetStepNumber() and TSSetStepNumber()* Remove TSGetTotalSteps()* Remove TSGetTimeStepNumber()
Merge remote-tracking branch 'origin/barry/update-petscfileretrieve'
123456