petsc-dev  

Messages by Thread

• • Re: [petsc-dev] tests coverage Barry Smith
• [petsc-dev] Seven days to merge MR before clang-format is instituted on the repository Barry Smith
• [petsc-dev] one last chance on clang-format https://gitlab.com/petsc/petsc/-/merge_requests/5455#note_1054605256 Barry Smith
• [petsc-dev] How to update tests output Blaise Bourdin
  • Re: [petsc-dev] How to update tests output Jed Brown
  • Re: [petsc-dev] How to update tests output Barry Smith
• [petsc-dev] Not a single person has approved the MR for allowing the use of clang-format on the repository Barry Smith
  • Re: [petsc-dev] Not a single person has approved the MR for allowing the use of clang-format on the repository Stefano Zampini
  • Re: [petsc-dev] Not a single person has approved the MR for allowing the use of clang-format on the repository Mark Adams
• [petsc-dev] petsc-3.17.4 now available Satish Balay via petsc-dev
• [petsc-dev] test failure in main Blaise Bourdin
  • Re: [petsc-dev] test failure in main Barry Smith
  • Re: [petsc-dev] test failure in main Satish Balay via petsc-dev
• [petsc-dev] GPU performance of MatSOR() Han Tran
  • Re: [petsc-dev] GPU performance of MatSOR() Jed Brown
  • Re: [petsc-dev] GPU performance of MatSOR() Barry Smith
  • Re: [petsc-dev] GPU performance of MatSOR() Paul Mullowney
  • Re: [petsc-dev] GPU performance of MatSOR() Jed Brown
  • Re: [petsc-dev] GPU performance of MatSOR() Paul Mullowney
  • Re: [petsc-dev] GPU performance of MatSOR() Barry Smith
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) LEDAC Pierre
  • Re: [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) Barry Smith
  • Re: [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) Matthew Knepley
  • Re: [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) Satish Balay via petsc-dev
  • Re: [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) LEDAC Pierre
  • Re: [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) Satish Balay via petsc-dev
  • Re: [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS) Satish Balay via petsc-dev
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Kaus, Boris
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Matthew Knepley
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Matthew Knepley
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jed Brown
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Lisandro Dalcin
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Lisandro Dalcin
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Matthew Knepley
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Lisandro Dalcin
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jed Brown
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith via petsc-dev
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jacob Faibussowitsch
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Scott Kruger
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Boyce Griffith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Boyce Griffith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jeremy L Thompson
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jed Brown
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Justin Chang
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jed Brown
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Jed Brown
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Barry Smith
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Ham, David A
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Matthew Knepley
  • Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3? Eric Chamberland
• [petsc-dev] FindPETSc.cmake Barry Smith
• [petsc-dev] Reformatting all PETSc source code with clang-format Barry Smith
• [petsc-dev] searching for petsc4py on petsc.org/main finds nothing Barry Smith
• Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Barry Smith
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Fande Kong
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Fande Kong
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Barry Smith
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
  • Re: [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame Satish Balay via petsc-dev
• [petsc-dev] MatProduct_AtB --with-scalar-type=complex Pierre Jolivet
  • Re: [petsc-dev] MatProduct_AtB --with-scalar-type=complex Barry Smith
  • Re: [petsc-dev] MatProduct_AtB --with-scalar-type=complex Zhang, Hong via petsc-dev
  • Re: [petsc-dev] MatProduct_AtB --with-scalar-type=complex Pierre Jolivet
  • Re: [petsc-dev] MatProduct_AtB --with-scalar-type=complex Zhang, Hong via petsc-dev
• [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6 Barry Smith
  • Re: [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6 Stefano Zampini
  • Re: [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6 Barry Smith
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Pierre Jolivet
  • Re: [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Barry Smith
  • Re: [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Matthew Knepley
  • Re: [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Barry Smith
  • Re: [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Matthew Knepley
  • Re: [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Barry Smith
  • Re: [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner Pierre Jolivet
• [petsc-dev] VecNest Pierre Jolivet
  • Re: [petsc-dev] VecNest Mark Adams
  • Re: [petsc-dev] VecNest Pierre Jolivet
  • Re: [petsc-dev] VecNest Pierre Jolivet
  • Re: [petsc-dev] VecNest Matthew Knepley
  • Re: [petsc-dev] VecNest Pierre Jolivet
  • Re: [petsc-dev] VecNest Matthew Knepley
  • Re: [petsc-dev] VecNest Matthew Knepley
  • Re: [petsc-dev] VecNest Pierre Jolivet
  • Re: [petsc-dev] VecNest Matthew Knepley
• [petsc-dev] Hiptmair--Xu as PCCOMPOSITE Pierre Jolivet
  • Re: [petsc-dev] Hiptmair--Xu as PCCOMPOSITE Mark Adams
• Re: [petsc-dev] proposed minor PetscPartitioner changes Eric Chamberland
  • Re: [petsc-dev] proposed minor PetscPartitioner changes Eric Chamberland
  • Re: [petsc-dev] proposed minor PetscPartitioner changes Barry Smith
  • Re: [petsc-dev] proposed minor PetscPartitioner changes Eric Chamberland
• [petsc-dev] petsc-3.17.3 now available Satish Balay via petsc-dev
• [petsc-dev] PetscObjectComposeFunction and clearing them out Barry Smith
• [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus David Andrs
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus Jed Brown
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus David Andrs
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus Matthew Knepley
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus David Andrs
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus Jed Brown
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus Matthew Knepley
  • Re: [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus David Andrs
• [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Stefano Zampini
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Barry Smith
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Stefano Zampini
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Matthew Martineau via petsc-dev
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Barry Smith
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Barry Smith
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Barry Smith
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Barry Smith
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Matthew Martineau via petsc-dev
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Barry Smith
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Matthew Martineau via petsc-dev
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
  • Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs Mark Adams
• [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Barry Smith
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Barry Smith
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Jed Brown
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Barry Smith
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Jed Brown
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Ham, David A
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Barry Smith
  • Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP? Jed Brown
• [petsc-dev] AIJ type question Mark Adams
  • Re: [petsc-dev] AIJ type question Barry Smith
• [petsc-dev] Fortran binding for VecGetValuesSection Blaise Bourdin
  • Re: [petsc-dev] Fortran binding for VecGetValuesSection Jed Brown
  • Re: [petsc-dev] Fortran binding for VecGetValuesSection Blaise Bourdin
• Re: [petsc-dev] [petsc-users] Mat created by DMStag cannot access ghost points Patrick Sanan
• [petsc-dev] new format error Mark Adams
  • Re: [petsc-dev] new format error Pierre Jolivet
• Re: [petsc-dev] Jacobi (smoothing) not staying on GPU Jose E. Roman
• [petsc-dev] petsc-3.17.2 now available Satish Balay via petsc-dev
• [petsc-dev] literal include used for manual strip PetscCall? Barry Smith
• [petsc-dev] do we really want to bother people with this? Barry Smith
  • Re: [petsc-dev] do we really want to bother people with this? Matthew Knepley
  • Re: [petsc-dev] do we really want to bother people with this? Barry Smith
  • Re: [petsc-dev] do we really want to bother people with this? Matthew Knepley
• [petsc-dev] have requests for MR review indicate time expected to complete Barry Smith
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Matthew Knepley
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Munson, Todd via petsc-dev
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Barry Smith
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Jacob Faibussowitsch
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Satish Balay via petsc-dev
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Barry Smith
  • Re: [petsc-dev] have requests for MR review indicate time expected to complete Satish Balay via petsc-dev
• [petsc-dev] kokkos hang after rebase over main, maybe, Crusher Mark Adams
  • Re: [petsc-dev] kokkos hang after rebase over main, maybe, Crusher Mark Adams
• [petsc-dev] Telescope usage Loic Gouarin
  • Re: [petsc-dev] Telescope usage Barry Smith
  • Re: [petsc-dev] Telescope usage Loic Gouarin
  • Re: [petsc-dev] Telescope usage Barry Smith
  • Re: [petsc-dev] Telescope usage Loic Gouarin
  • Re: [petsc-dev] Telescope usage Matthew Knepley
  • Re: [petsc-dev] Telescope usage Dave May
  • Re: [petsc-dev] Telescope usage Loic Gouarin
  • Re: [petsc-dev] Telescope usage Dave May
  • Re: [petsc-dev] Telescope usage Loic Gouarin
  • Re: [petsc-dev] Telescope usage Dave May
  • Re: [petsc-dev] Telescope usage Loic Gouarin
  • Re: [petsc-dev] Telescope usage Dave May
  • Re: [petsc-dev] Telescope usage Matthew Knepley
  • Re: [petsc-dev] Telescope usage Loïc Gouarin
  • Re: [petsc-dev] Telescope usage Loïc Gouarin
• [petsc-dev] Another SSP method Matthew Knepley
  • Re: [petsc-dev] Another SSP method Emil Constantinescu via petsc-dev
  • Re: [petsc-dev] Another SSP method Constantinescu, Emil M. via petsc-dev
  • Re: [petsc-dev] Another SSP method Emil Constantinescu via petsc-dev
  • Re: [petsc-dev] Another SSP method Jed Brown

• Earlier messages
• Later messages