petsc-dev
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: [petsc-dev] Regression bug in Merge branch 'knepley/feature-hybrid-mass' into 'main'
Matthew Knepley
[petsc-dev] Is the petsc4py build broken?
Matthew Knepley
Re: [petsc-dev] Is the petsc4py build broken?
Satish Balay via petsc-dev
Re: [petsc-dev] Is the petsc4py build broken?
Pierre Jolivet
Re: [petsc-dev] Is the petsc4py build broken?
Matthew Knepley
Re: [petsc-dev] Is the petsc4py build broken?
Satish Balay via petsc-dev
[petsc-dev] Fwd: Thank you for filling out Project Application to Join NumFOCUS
Barry Smith
[petsc-dev] The PETSc code of conduct does not appear on the PETSc website
Barry Smith
[petsc-dev] Matrix Manipulation Question
Matthew Knepley
Re: [petsc-dev] Matrix Manipulation Question
Barry Smith
[petsc-dev] manual page organization wrt all those things
Barry Smith
Re: [petsc-dev] manual page organization wrt all those things
Matthew Knepley
[petsc-dev] numFocus membership and needed new webpages
Barry Smith
[petsc-dev] PETSc release announcement and reminder to register for the PETSc annual meeting
Barry Smith
[petsc-dev] DMPlex redistribution
Adrian Croucher
Re: [petsc-dev] DMPlex redistribution
Matthew Knepley
Re: [petsc-dev] DMPlex redistribution
Adrian Croucher
Re: [petsc-dev] DMPlex redistribution
Matthew Knepley
Re: [petsc-dev] DMPlex redistribution
Adrian Croucher
Re: [petsc-dev] DMPlex redistribution
Matthew Knepley
Re: [petsc-dev] DMPlex redistribution
Adrian Croucher
Re: [petsc-dev] DMPlex redistribution
Matthew Knepley
Re: [petsc-dev] DMPlex redistribution
Adrian Croucher
[petsc-dev] I will be converting .rst files to .md; let me know if you have any outstanding MR with changes
Barry Smith
Re: [petsc-dev] I will be converting .rst files to .md; let me know if you have any outstanding MR with changes
Junchao Zhang
[petsc-dev] Request to add a PETSc-MUMPS API for null pivot rows
Ashish Patel
Re: [petsc-dev] Request to add a PETSc-MUMPS API for null pivot rows
Barry Smith
Re: [petsc-dev] [petsc-users] HDF5 timestepping in PETSc 3.16
Adrian Croucher
[petsc-dev] GMSH reader and vertex sets
Blaise Bourdin
Re: [petsc-dev] GMSH reader and vertex sets
Matthew Knepley
[petsc-dev] VecCreateGhost on GPUs
Goddard, Christopher
Re: [petsc-dev] VecCreateGhost on GPUs
Matthew Knepley
[petsc-dev] VecCreateGhost on GPUs
Goddard, Christopher
[petsc-dev] SNESNEWTONLS
Angus, Justin Ray via petsc-dev
Re: [petsc-dev] SNESNEWTONLS
Barry Smith
Re: [petsc-dev] SNESNEWTONLS
Angus, Justin Ray via petsc-dev
Re: [petsc-dev] SNESNEWTONLS
Matthew Knepley
Re: [petsc-dev] SNESNEWTONLS
Angus, Justin Ray via petsc-dev
Re: [petsc-dev] SNESNEWTONLS
Barry Smith
Re: [petsc-dev] SNESNEWTONLS
Angus, Justin Ray via petsc-dev
Re: [petsc-dev] SNESNEWTONLS
Barry Smith
[petsc-dev] How come petsc4py objects do not handle attributes in the "standard" way?
Barry Smith
Re: [petsc-dev] How come petsc4py objects do not handle attributes in the "standard" way?
Aron Ahmadia
[petsc-dev] petsc release plan for Mar/2023
Satish Balay via petsc-dev
Re: [petsc-dev] petsc release plan for Mar/2023
Satish Balay via petsc-dev
[petsc-dev] gcov tests on my machine before CI
Barry Smith
Re: [petsc-dev] gcov tests on my machine before CI
Jacob Faibussowitsch
[petsc-dev] Putting more menu items at the top of petsc.org pages (how to?)
Barry Smith
Re: [petsc-dev] Putting more menu items at the top of petsc.org pages (how to?)
Zhang, Hong via petsc-dev
Re: [petsc-dev] Putting more menu items at the top of petsc.org pages (how to?)
Jed Brown
Re: [petsc-dev] Putting more menu items at the top of petsc.org pages (how to?)
Barry Smith
[petsc-dev] Rig the search icon in petsc.org to also search the PETSc users archives (and other stuff?)
Barry Smith
[petsc-dev] Now put PETSc docs updates into main branch
Barry Smith
[petsc-dev] PETSC_VIEWER_FAILED
Pierre Jolivet
Re: [petsc-dev] PETSC_VIEWER_FAILED
Barry Smith
[petsc-dev] Apply for Google Summer of Code 2023?
Karl Rupp
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Matthew Knepley
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Junchao Zhang
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Satish Balay via petsc-dev
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Jed Brown
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Junchao Zhang
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Jed Brown
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Matthew Knepley
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Karl Rupp
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Karl Rupp
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Karl Rupp
Re: [petsc-dev] Apply for Google Summer of Code 2023?
Junchao Zhang
[petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Barry Smith
Re: [petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Matthew Knepley
Re: [petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Barry Smith
Re: [petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Matthew Knepley
Re: [petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Barry Smith
Re: [petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Jed Brown
Re: [petsc-dev] xlocal = da.getLocalVec() .. da.restoreLocalVec(xlocal) skip the restore
Barry Smith
[petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Barry Smith
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Matthew Knepley
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Barry Smith
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Matthew Knepley
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Jed Brown
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Barry Smith
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Jed Brown
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Barry Smith
Re: [petsc-dev] PetscOptionsGetViewer() problems with multiple usage on the same object but different options databases
Jacob Faibussowitsch
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
Earlier messages
Later messages