petsc-dev  

Messages by Thread

• • Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases Barry Smith
• [petsc-dev] New Object and Function Development Brandon Denton
  • Re: [petsc-dev] New Object and Function Development Jed Brown
• [petsc-dev] Fortran-auto-interfaces Blaise Bourdin
  • Re: [petsc-dev] Fortran-auto-interfaces Jose E. Roman
  • Re: [petsc-dev] Fortran-auto-interfaces Blaise Bourdin
  • Re: [petsc-dev] Fortran-auto-interfaces Jose E. Roman
  • Re: [petsc-dev] Fortran-auto-interfaces Blaise Bourdin
• [petsc-dev] bad cpu/MPI performance problem Mark Adams
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Matthew Knepley
  • Re: [petsc-dev] bad cpu/MPI performance problem Mark Adams
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Jed Brown
  • Re: [petsc-dev] bad cpu/MPI performance problem Mark Adams
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Mark Adams
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Barry Smith
  • Re: [petsc-dev] bad cpu/MPI performance problem Mark Adams
• [petsc-dev] GPU timers broken in main Zhang, Hong via petsc-dev
• [petsc-dev] is there a bug in private_DMDALocatePointsIS_3D_Regular? Matteo Semplice
  • Re: [petsc-dev] is there a bug in private_DMDALocatePointsIS_3D_Regular? Matthew Knepley
• [petsc-dev] FFT of multi-component system Matthew Knepley
• [petsc-dev] https://petsc.org/release/docs/manualpages/PC/PCFIELDSPLIT/ is a mess! Barry Smith
  • Re: [petsc-dev] https://petsc.org/release/docs/manualpages/PC/PCFIELDSPLIT/ is a mess! Matthew Knepley
• [petsc-dev] DMPlexComputeGeometryFEM Yann Jobic
  • Re: [petsc-dev] DMPlexComputeGeometryFEM Matthew Knepley
  • Re: [petsc-dev] DMPlexComputeGeometryFEM Yann Jobic
• [petsc-dev] Swarm tag error Matthew Knepley
  • Re: [petsc-dev] Swarm tag error Junchao Zhang
  • Re: [petsc-dev] Swarm tag error Matthew Knepley
  • Re: [petsc-dev] Swarm tag error Junchao Zhang
  • Re: [petsc-dev] Swarm tag error Matthew Knepley
  • Re: [petsc-dev] Swarm tag error Dave May
  • Re: [petsc-dev] Swarm tag error Stefano Zampini
  • Re: [petsc-dev] Swarm tag error Dave May
  • Re: [petsc-dev] Swarm tag error Dave May
• Re: [petsc-dev] the google is seemingly preferring the main branch Matthew Knepley
• [petsc-dev] Matshell with PETSs solvers using GPU Han Tran
  • Re: [petsc-dev] Matshell with PETSs solvers using GPU Jed Brown
  • Re: [petsc-dev] Matshell with PETSs solvers using GPU Jed Brown
  • Re: [petsc-dev] Matshell with PETSs solvers using GPU Barry Smith
  • Re: [petsc-dev] Matshell with PETSs solvers using GPU Han Tran
• [petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen Stefano Zampini
  • Re: [petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen Jacob Faibussowitsch
  • Re: [petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen Stefano Zampini
  • Re: [petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen Jacob Faibussowitsch
  • Re: [petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen Matthew Knepley
• [petsc-dev] PETSc 3.18.1 undefined reference Antonio T. sagitter
  • Re: [petsc-dev] PETSc 3.18.1 undefined reference Satish Balay via petsc-dev
  • Re: [petsc-dev] PETSc 3.18.1 undefined reference Antonio T. sagitter
  • Re: [petsc-dev] PETSc 3.18.1 undefined reference Jed Brown
  • Re: [petsc-dev] PETSc 3.18.1 undefined reference Satish Balay via petsc-dev
• [petsc-dev] petsc-3.18.1 now available Satish Balay via petsc-dev
• [petsc-dev] Docs do not build for me Matthew Knepley
• [petsc-dev] petsc4py, numpy's BLAS and PETSc's BLAS Barry Smith
  • Re: [petsc-dev] petsc4py, numpy's BLAS and PETSc's BLAS Zhang, Hong via petsc-dev
  • Re: [petsc-dev] petsc4py, numpy's BLAS and PETSc's BLAS Satish Balay via petsc-dev
  • Re: [petsc-dev] petsc4py, numpy's BLAS and PETSc's BLAS Satish Balay via petsc-dev
  • Re: [petsc-dev] petsc4py, numpy's BLAS and PETSc's BLAS Barry Smith
• [petsc-dev] Make checkbadSource error Blaise Bourdin
  • Re: [petsc-dev] Make checkbadSource error Matthew Knepley
• [petsc-dev] Time-Steppers: how to stop and resume iterations at intermediate times? Alexis Marboeuf
  • Re: [petsc-dev] Time-Steppers: how to stop and resume iterations at intermediate times? Matthew Knepley
  • Re: [petsc-dev] Time-Steppers: how to stop and resume iterations at intermediate times? Alexis Marboeuf
• Re: [petsc-dev] [petsc-users] Regarding the status of MatSolve on GPUs Junchao Zhang
  • Re: [petsc-dev] [petsc-users] Regarding the status of MatSolve on GPUs Junchao Zhang
• [petsc-dev] Manualpage TOC Matthew Knepley
  • Re: [petsc-dev] Manualpage TOC Barry Smith
  • Re: [petsc-dev] Manualpage TOC Satish Balay via petsc-dev
  • Re: [petsc-dev] Manualpage TOC Barry Smith
  • Re: [petsc-dev] Manualpage TOC Blaise Bourdin
  • Re: [petsc-dev] Manualpage TOC Barry Smith
  • Re: [petsc-dev] Manualpage TOC Blaise Bourdin
  • [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Emil Constantinescu via petsc-dev
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Barry Smith
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Jed Brown
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Zhang, Hong via petsc-dev
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Pierre Jolivet
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Jed Brown
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Pierre Jolivet
  • Re: [petsc-dev] Potential memory leak in PETSc - hypre interface when using Euclid Pierre Jolivet
• [petsc-dev] PETSc 2023 User Meeting and New Release 3.18 Barry Smith
• [petsc-dev] Python garbage collector broken? Stefano Zampini
  • Re: [petsc-dev] Python garbage collector broken? Barry Smith
• [petsc-dev] Enhancing the PETSc Developer Experience Zhang, Hong via petsc-dev
  • Re: [petsc-dev] Enhancing the PETSc Developer Experience Zhang, Hong via petsc-dev
• [petsc-dev] Symbol names using clang in addition to gcc Aagaard, Brad T via petsc-dev
  • Re: [petsc-dev] Symbol names using clang in addition to gcc Satish Balay via petsc-dev
  • Re: [petsc-dev] Symbol names using clang in addition to gcc Satish Balay via petsc-dev
  • Re: [petsc-dev] Symbol names using clang in addition to gcc Satish Balay via petsc-dev
  • Re: [petsc-dev] Symbol names using clang in addition to gcc Satish Balay via petsc-dev
• [petsc-dev] final decision on 2023 User group meeting and location Barry Smith
• [petsc-dev] do all MIS algorithms require a symmetric structure? Barry Smith
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Mark Adams
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Barry Smith
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Mark Adams
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Barry Smith
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Mark Adams
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Barry Smith
  • Re: [petsc-dev] do all MIS algorithms require a symmetric structure? Mark Adams
• [petsc-dev] PetscLogEventRegister() is problematic since it must be call in exactly the same order on all ranks Barry Smith
  • Re: [petsc-dev] PetscLogEventRegister() is problematic since it must be call in exactly the same order on all ranks Matthew Knepley
  • Re: [petsc-dev] PetscLogEventRegister() is problematic since it must be call in exactly the same order on all ranks Barry Smith
  • Re: [petsc-dev] PetscLogEventRegister() is problematic since it must be call in exactly the same order on all ranks Jed Brown
• [petsc-dev] large cost of symmetrizing for GAMG? Barry Smith
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Mark Adams
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Barry Smith
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Mark Adams
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Barry Smith
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Mark Adams
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Barry Smith
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Mark Adams
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Barry Smith
  • Re: [petsc-dev] large cost of symmetrizing for GAMG? Mark Adams
• [petsc-dev] Bug in DMPlexVecGetClosure/DMPlexVecRestoreClosure in Fortran Blaise Bourdin
  • Re: [petsc-dev] Bug in DMPlexVecGetClosure/DMPlexVecRestoreClosure in Fortran Blaise Bourdin
• [petsc-dev] Reminder: PETSc release in less than one month Barry Smith
• [petsc-dev] Fwd: Pending configuration of custom domain docs.petsc.org Matthew Knepley
  • Re: [petsc-dev] Fwd: Pending configuration of custom domain docs.petsc.org Satish Balay via petsc-dev
  • Re: [petsc-dev] Fwd: Pending configuration of custom domain docs.petsc.org Jed Brown
• [petsc-dev] PETSc janitorial work Blaise Bourdin
  • Re: [petsc-dev] PETSc janitorial work Matthew Knepley
  • Re: [petsc-dev] PETSc janitorial work Nathan Collier
  • Re: [petsc-dev] PETSc janitorial work Blaise Bourdin
  • Re: [petsc-dev] PETSc janitorial work Barry Smith
  • Re: [petsc-dev] PETSc janitorial work Barry Smith
• [petsc-dev] clang-format is not idempotent Barry Smith
  • Re: [petsc-dev] clang-format is not idempotent Jacob Faibussowitsch
• [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Barry Smith
  • Re: [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Lawrence Mitchell
  • Re: [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Barry Smith
  • Re: [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Lawrence Mitchell
  • Re: [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Barry Smith
  • Re: [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Lawrence Mitchell
  • Re: [petsc-dev] Still unable to provide link from manual page into users manual after Sphinx Barry Smith
• [petsc-dev] Type mismatch warnings Blaise Bourdin
  • Re: [petsc-dev] Type mismatch warnings Satish Balay via petsc-dev
  • Re: [petsc-dev] Type mismatch warnings Blaise Bourdin
  • Re: [petsc-dev] Type mismatch warnings Satish Balay via petsc-dev
  • Re: [petsc-dev] Type mismatch warnings Barry Smith
  • Re: [petsc-dev] Type mismatch warnings Barry Smith
• [petsc-dev] Postdoc Openings at Argonne Munson, Todd via petsc-dev
• [petsc-dev] DMPlex: fix bug for natural Point SF Alexis Marboeuf
• [petsc-dev] Reminder: You may want to get some of , your MR merged before the global clang-format reformatting later this week Barry Smith
• [petsc-dev] tests coverage Blaise Bourdin
  • Re: [petsc-dev] tests coverage Satish Balay via petsc-dev
  • Re: [petsc-dev] tests coverage Jed Brown
  • Re: [petsc-dev] tests coverage Blaise Bourdin
  • Re: [petsc-dev] tests coverage Satish Balay via petsc-dev
  • 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

• Earlier messages
• Later messages