Generate an error if code attempts to load a dense formatted matrix from disk into a sparse matrixThe error check was missing for some matrix typesReported-by: Analabha Roy <hariseldon99@gmail.co
Generate an error if code attempts to load a dense formatted matrix from disk into a sparse matrixThe error check was missing for some matrix typesReported-by: Analabha Roy <hariseldon99@gmail.com>
show more ...
removed bstream code since it was not in nightly tests and broken
MatNorm: fix negative logging and missing error handling
MatNorm: fix missing PetscLogFlopsReported-by: Anishi Gupta <anishi.anishi@gmail.com>
cleanup MatGetSubMatrices_MPISBAIJ()
rm checking of (isrow != iscol) in response to Jose's request for SLEPc; Zero some ops' to avoid invalid use of MatGetSubMatrices_SeqSBAIJ()
PetscDraw: Proper implementation of PETSC_DRAW_NULL* Remove special casing of PETSC_DRAW_NULL in the draw interface* Rework handling of PETSC_DRAW_NULL in Draw{Axis|LG|SP|BAR|HG}* Some 'extern' -
PetscDraw: Proper implementation of PETSC_DRAW_NULL* Remove special casing of PETSC_DRAW_NULL in the draw interface* Rework handling of PETSC_DRAW_NULL in Draw{Axis|LG|SP|BAR|HG}* Some 'extern' -> 'PETSC_INTERN' fixes* Add missing error checking
Merge branch 'barry/fix-private-functions'
PetscDraw: Fix MatView() for MAT{SEQ|MPI}{[S|SB]AIJ|DENSE}
More decreasing visibility of symbols from outside librariesAlso fix a few bugs related to having multiple PETSc libraries
Print a better error when someone sets a MatOption that that matrix is not ready for yet.Reported-by: Mark McClure <mark.w.mccl@gmail.com>
Merge branch 'master' into barry/petscoptions-object
Merge remote-tracking branch 'origin/hzhang/matmatmult_dense'
Complete update to new PetscOptions interface
add MAT_INPLACE_MATRIX; replace MAT_REUSE_MATRIX with it for MatConvert()
Merge branch 'barry/add-mpiu_allreduce'
Merge branch 'barry/fix-ts-matshift-error'
Introduce MPIU_Allreduce() to detect cases where all processes that share an MPI comm do not call the same sequence of MPI_Allreduce()This is a bug that can be difficult to track down.Suggested-by
Introduce MPIU_Allreduce() to detect cases where all processes that share an MPI comm do not call the same sequence of MPI_Allreduce()This is a bug that can be difficult to track down.Suggested-by: Eric Chamberland <Eric.Chamberland@giref.ulaval.ca>Suggested-by: Patrick Lacasse <placasse@giref.ulaval.ca>
Merge branch 'maint'
If only some processes had no local entries in the matrix the MatSeqXAIJPreallocation() changed the value of aij->nonew on only thoseprocesses thus resulting in gridlock in MatAssemblyEnd_MPIXAIJ()
If only some processes had no local entries in the matrix the MatSeqXAIJPreallocation() changed the value of aij->nonew on only thoseprocesses thus resulting in gridlock in MatAssemblyEnd_MPIXAIJ() since some processes wanted to update the matrix nonzero state while others did notReported-by: Eric Chamberland <Eric.Chamberland@giref.ulaval.ca>
Added missing MatMissingDiagonal() implementations
MatHeaderReplace() corrupted the -objects_dump arrayReported-by: Torquil Macdonald Sørensen <torquil@gmail.com>MatHeaderReplace() and MatHeaderMerge() destroy the second matrix argument therefor
MatHeaderReplace() corrupted the -objects_dump arrayReported-by: Torquil Macdonald Sørensen <torquil@gmail.com>MatHeaderReplace() and MatHeaderMerge() destroy the second matrix argument therefor pass it asa pointer to it can be zeroed and not mistakenly reused.
Merge branch 'jed/mat-assembly-perf' of bitbucket:petsc/petscVecAssembly and MatAssembly now use a scalable exchange pattern based onPetscCommBuildTwoSided. This feature can be controlled with th
Merge branch 'jed/mat-assembly-perf' of bitbucket:petsc/petscVecAssembly and MatAssembly now use a scalable exchange pattern based onPetscCommBuildTwoSided. This feature can be controlled with the options -vec_assembly_bts 0 or 1 (default 0) -matstash_bts 0 or 1 (default 0)The rationale is that the new implementation with scalable datastructures can be slightly slower than the old version at small processcounts. The default here could be changed to depend on the processcount (leading to possibly-confusing scaling performance diagnostics) orthe implementation could learn to take a fast path.* 'jed/mat-assembly-perf' of bitbucket:petsc/petsc: (49 commits) MatStash: fix -Wsign-compare by using size_t for loop index when max is also size_t Sys BuildTwoSided test: fix for non-POD std::complex MatStash: cast to satisfy non-structural MPI type tag check mpiuni: fix compile error /sandbox/petsc/petsc.clone-2/arch-linux-uni/lib/libpetsc.so: undefined reference to `MPI_Type_create_resized' Vec: Silence compiler warning Vec: fix typo in comment Sys: fix C89 compiler warning VecStash BTS: fix block stash InsertMode accounting VecStash BTS: fix indexing bug counting sends to rank 0 MatStash BTS: fix memory leak on MAT_SUBSET_OFF_PROC_ENTRIES VecAssemblyEnd_MPI_BTS: fix donotstash code path VecAssemblyEnd_MPI_BTS: fix C++ conversion to InsertMode Sys: fix datatypes test using MPI_Type_create_resized MatStash BTS: work around lack of offsetof() for non-POD (std::complex) MatAssembly: move check for InsertMode consistency into MatStashScatter impls MatStash BTS: fix memory leak on reassembly with MAT_SUBSET_OFF_PROC_ENTRIES MatStash BTS: small simplification to row ownership calculation MatStash BTS: add MAT_SUBSET_OFF_PROC_ENTRIES, impl with neighbor-only comm MatStash: initial BTS (BuildTwoSided) implementation MatStash: add extension point for new BTS implementation ...
Merge branch 'master' into barry/fix-petscviewer-attempt-2
Merge branch 'barry/fix-nonew-notcollective/maint' into jed/mat-assembly-perfJed this fucking 6+ month running thing in next that is not in master is a royal fucking pain in the ass andan abuse of
Merge branch 'barry/fix-nonew-notcollective/maint' into jed/mat-assembly-perfJed this fucking 6+ month running thing in next that is not in master is a royal fucking pain in the ass andan abuse of git. I think it is not justified to ever have anything in next for more than a few weeks at most.Either take it out of next if it is broken or put it in master if it is not broken. Hanging around in next butnot master for ever is not a good policy.
1...<<11121314151617181920>>...37