DMCOMPOSITE: fix improper computation of l2g map indicesWhen a l2g map has a negative index, we just flag it as negative in the composite map and move onThere's no consensus on what a negative ind
DMCOMPOSITE: fix improper computation of l2g map indicesWhen a l2g map has a negative index, we just flag it as negative in the composite map and move onThere's no consensus on what a negative index means, except for skipping when setting the values in vectors and matrices
show more ...
Merge branch 'gropp/doc-fixes-1' [PR #1838]
DMSetType: Clear dm->ops and set type name before calling constructor
Merge from doc-fixes branch
Fixes for doctext update
Add PetscArraycmp(), PetscArraycpy(), PetscArrayzero(), PetscArraymove(), update code to use new formsReplace a couple multi-mallocs with a single mallocReplace backwards loops in MatSetValues_*()
Add PetscArraycmp(), PetscArraycpy(), PetscArrayzero(), PetscArraymove(), update code to use new formsReplace a couple multi-mallocs with a single mallocReplace backwards loops in MatSetValues_*() with PetscArraymove()Commit-type: style-fix, feature
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>
Use new vector read-lock function namesThe new one are VecLockReadPush, VecLockReadPop, VecSetErrorIfLocked
DM+DS: Reorganized DS handling completely do that multiple regions can be supported- A region is labeled portion of the mesh which has the same approximation space for the solution. Note that this i
DM+DS: Reorganized DS handling completely do that multiple regions can be supported- A region is labeled portion of the mesh which has the same approximation space for the solution. Note that this is NOT the same as the label indicating the support of a field. Regions are the refinement of the field supports into unique approximation space pieces. Right now, we only support a single strategy, namely one space on the regular mesh and one on the hybrid cells, but we only have to change DMCreateDS() to extend the capability.- Now instead of using PetscDSSetDiscretization() and DMSetDS(), you use DMSetField() and DMCreateDS(). Also, you now must use DMCopyDisc(), instead of DMSetDS(), which copies both the field and DS structure to another DM. These changes have been made in all examples.- DMGetCellDS() returns the approximation space for that cell- DMGetDS() return the default space since most people will not use regions. There is still a lot of work left t generalize all methods to multiple DSes, but all old code still functions.- DMGetRegion/RegionNumDS() gets spaces by label and region number- DMCreateDS() is the setup method which makes the regions and corresponding DSes. With some work, this could be converted to a lazy initialization.- Cleaned up access to DS since now we can have more than one- Projection was improved to extract the DS for the particular cells it is iterating over- The DS are set from options during Section creation. The idea is that people using DS would also use automatic Section creation, or they would manage things themselves and call SetFromOptions manually.- I updated the subDM and superDM constructors, but they only work for a single region
Merge branch 'maint'
DMComposite: add missing guards
DMDAVecGetArrayF90(): bug fix wrt passing wrong argument to F90Array3dDestroy() introduced in fcfd50eb5fbAlso use 'typedef void* F90Array1d' to get compiler type-checkReported-by: Randall Mackie
DMDAVecGetArrayF90(): bug fix wrt passing wrong argument to F90Array3dDestroy() introduced in fcfd50eb5fbAlso use 'typedef void* F90Array1d' to get compiler type-checkReported-by: Randall Mackie <rlmackie862@gmail.com>Thanks-to: Jed Brown <jed@jedbrown.org>Thanks-to: Intel Support Subject: Intel Developer Products Support - Update to Service Request#:03369230
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/
a few more Fortran interfacesCommit-type: feature
Minor fixes for conflicts with auto generated Fortran stubs and missing define in FortranCommit-type: bug-fix
add a collection of Fortran interfaces and additional docsFor some reason this cause failures in many examples, need to debugCommit-type: testing-fix,style-fix,documentation, example
Merge remote-tracking branch 'origin/stefano_zampini/feature-glvis-supportdmcomposite'
DMComposite: Add support for GLVis viewer
Docs: DMCompositeAddDM man page: fix input parameters
Merge remote-tracking branch 'origin/maint'
Fix VecView_DMComposite() to use Vec{Get|Restore}ArrayRead()
F90Array routines now take a MPI_Datatype argument instead of PetscDataTypeThis is part of the refactorization to limit and maybe eventually eliminate PetscDataType sinceit duplicates MPI_Datatype
F90Array routines now take a MPI_Datatype argument instead of PetscDataTypeThis is part of the refactorization to limit and maybe eventually eliminate PetscDataType sinceit duplicates MPI_Datatype functionality (poorly).Commit-type: style-fixThanks-to: Jed Brown <jed@jedbrown.org>
configure: add option --with-fortran-bindingsNow one can use --with-fc=gfortran --with-fortran-bindings=0 to detect fortran compiler properly[for externalpacakge use - for eg: scalapack] but avoid
configure: add option --with-fortran-bindingsNow one can use --with-fc=gfortran --with-fortran-bindings=0 to detect fortran compiler properly[for externalpacakge use - for eg: scalapack] but avoid building PETSc fortran bindings in library and modules.Also disable sowing when with-fortran-bindings is disabledFix makefiles (corresponding to fortran bindings) to consistantly use PETSC_HAVE_FORTRANAlso remove unused PETSC_USE_FORTRAN_DATATYPES flagReported-by: Patrick Farrell <patrick.farrell@maths.ox.ac.uk>
1234567891011