Add log event for PetscOptionsGetViewerNormally this time should be small, but this way we will see if thereare many calls that are hurting.
Add test of PetscViewerPushGetViewerOff
Allow runtime control of viewer creation in PetscOptionsGetViewer27b0f28 (Added configure option --with-viewfromoptions=0) allowsbuilding PETSc such that PetscOptionsGetViewer never returns a view
Allow runtime control of viewer creation in PetscOptionsGetViewer27b0f28 (Added configure option --with-viewfromoptions=0) allowsbuilding PETSc such that PetscOptionsGetViewer never returns a viewer.Sometimes it is useful to control this at runtime. For example, wewould like to still use -log_view and the like, but want to turn off theexpensive XXXViewFromOptions and similar calls inside small subsolves.Allow this by exposing control at runtime. Typical use case: PetscOptionsPushGetViewerOff(PETSC_TRUE); for (i = 0; i < npatch; i++) KSPSolve(patch[i], ...); PetscOptionsPopGetViewerOff();
show more ...
Updated and simplified Fortran interfaceReduced from 4 distinct approaches to using PETSc from Fortran to 1No more .h90 files (Fortran 90 functionality is now always available)Parameters and func
Updated and simplified Fortran interfaceReduced from 4 distinct approaches to using PETSc from Fortran to 1No more .h90 files (Fortran 90 functionality is now always available)Parameters and function prototypes are now provide through Fortran modules, not includes;only #define are provided in the petscXXXdef.h filesPETSc objects can be declared as either type(tXXX) or XXX. For example type(tVec) or VecMoved now private Fortran include files out of public include directory since uses don't use them;they are only used to generate the Fortran modulesEasier to support and test; we can now easily add more function prototypesAlso had to rework generation of manual pages to consistently use MANSEC and SUBMANSECsince these variables also handle how the Fortran modules are generated.Time: 57 hours
Merge remote-tracking branch 'origin/balay/fix-matlab-test'
matlab: fix runex12 in src/dm/examples/testsThanks-to: Barry Smith <bsmith@mcs.anl.gov>
improve the manual pages seealso and add additional manual pages for PETSc web utilitiesTime: 1 hour
add information to PetscDrawXXCreate() routines that options and data provided are ignored on all processes except the first in the communicatorTime: .1 hours
Add cross links to many of the PetscDraw routinesTime: .75 hours
add many .seealso: for PetscDraw routinesStill need to add them PetscDrawAxis, PetscDrawSP, PetscDrawHG, PetscDrawBarTime: .35 hours
build: --with-fortran-datatypes fixes
made --with-fortran-interfaces by default; cleaned up sys fortran interfacessys fortran interfaces had not previously been tested thus had to clean up several that were brokenTime: 2 hoursRepor
made --with-fortran-interfaces by default; cleaned up sys fortran interfacessys fortran interfaces had not previously been tested thus had to clean up several that were brokenTime: 2 hoursReported-by: nightly tests
Merge branch 'barry/use-fortran-kind-consistently' into barry/fix-dmdacreateNeed to resolve conflicts with .F90 code reformating
Fortran updatesUpdated all F90 examples to use free form with full error checkingUpdate all Fortran examples to check error code for PetscInitialize() callTime: 2 hours
Cannot use return in Fortran main program so use stop insteadReported-by: nightly tests
added return checking for more system calls missed beforesince Windows compilers don't support ssize_t remove its usage from exampleTime: .2 hoursReported-by: nightly tests
Introduce PETSC_REAL_KIND and update all .F90 examples to free form with error checking and to use itThe reason for PETSC_REAL_KIND is there is no way to assign constants (say .1) in Fortran so tha
Introduce PETSC_REAL_KIND and update all .F90 examples to free form with error checking and to use itThe reason for PETSC_REAL_KIND is there is no way to assign constants (say .1) in Fortran so that they have the full precision of the left hand side variable. And if you mark them with D0 then compile in single precision you get a warning about truncating precisionTime: 6 hourReported-by: Todd Munson <tmunson@mcs.anl.gov>Thanks-to: Blaise A Bourdin <bourdin@lsu.edu>, Lisandro Dalcin <dalcinl@gmail.com>
Added (void) casts for system calls that return arguments that PETSc ignoresCertain compilers (Microsoft) generate warnings without the casts. Since we conciously choicenot to process the return a
Added (void) casts for system calls that return arguments that PETSc ignoresCertain compilers (Microsoft) generate warnings without the casts. Since we conciously choicenot to process the return arguments we label the calls with (void) as suchTime: .3 hoursReported-by: nightly tests
Merge branch 'maint'
fix location to example in manual pages for PetscViewerSocketOpen() and PETSC_VIEWER_SOCKET_()Also improve manual pages slightlyTime: .1 hourReported-by: apostol <apostol.faliagas@gmail.com>
Removed crumbs from previous support of Netcdf. Support was removed in 2010Time: .2 hours
added manual pages for missing PETSCVIEWERXXX such as PETSCVIEWERBINARYThanks-to: apostol <apostol.faliagas@gmail.com>
Refactored ./configures handling of package requirements for precision. Now each package indicateswhat it supports withself.precisions = ['single','double','__float128']Updated the package files t
Refactored ./configures handling of package requirements for precision. Now each package indicateswhat it supports withself.precisions = ['single','double','__float128']Updated the package files to indicate what they supportRemoved unneeded #requires arguments from makefiles for external packages.Time: 2 hoursReported-by: Patrick Sanan <patrick.sanan@gmail.com>
Merge branch 'pr520/psanan/psanan/vtk-viewer-leak-fix/master' into maint
Merge branch 'pr520/psanan/psanan/vtk-viewer-leak-fix/master'
1...<<31323334353637383940>>...64