May 2011 Archives by date

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...

Starting: Sun May 1 04:59:31 CDT 2011
Ending: Tue May 31 21:56:45 CDT 2011
Messages: 187

• [petsc-dev] how to use builder.py   Aron Ahmadia
• [petsc-dev] MatSetFromOptions() after DMGetMatrix()   Jed Brown
• [petsc-dev] web petsc-dev documentation broken   Aron Ahmadia
• [petsc-dev] how to use builder.py   Matthew Knepley
• [petsc-dev] how to use builder.py   Aron Ahmadia
• [petsc-dev] how to use builder.py   Matthew Knepley
• [petsc-dev] MatSetFromOptions() after DMGetMatrix()   Barry Smith
• [petsc-dev] MatSetFromOptions() after DMGetMatrix()   Jed Brown
• [petsc-dev] FieldSplit and PCLSC   domenico.borzacchiello at univ-st-etienne.fr
• [petsc-dev] FieldSplit and PCLSC   Jed Brown
• [petsc-dev] FieldSplit and PCLSC   domenico.borzacchiello at univ-st-etienne.fr
• [petsc-dev] FieldSplit and PCLSC   Jed Brown
• [petsc-dev] [petsc-users] FETI-DP   Thomas Witkowski
• [petsc-dev] FieldSplit and PCLSC   Dave May
• [petsc-dev] PETSc and multigpu   Alexander Grayver
• [petsc-dev] Solving time for nested solvers   Thomas Witkowski
• [petsc-dev] Solving time for nested solvers   Barry Smith
• [petsc-dev] FieldSplit and PCLSC   domenico.borzacchiello at univ-st-etienne.fr
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Barry Smith
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Barry Smith
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Alexander Grayver
• [petsc-dev] About PCFieldSplitGetSubKSP   Ryan Yan
• [petsc-dev] About PCFieldSplitGetSubKSP   Barry Smith
• [petsc-dev] About PCFieldSplitGetSubKSP   Ryan Yan
• [petsc-dev] About -ksp_view   Ryan Yan
• [petsc-dev] About -ksp_view   Jed Brown
• [petsc-dev] About -ksp_view   Ryan Yan
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Victor Minden
• [petsc-dev] (S)BSTRM implementations for block sizes other than 4 and 5?   Jed Brown
• [petsc-dev] (S)BSTRM implementations for block sizes other than 4 and 5?   Dahai Guo
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] preparing for a PETSc release   Blaise Bourdin
• [petsc-dev] preparing for a PETSc release   Ethan Coon
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] preparing for a PETSc release   Blaise Bourdin
• [petsc-dev] preparing for a PETSc release   Jed Brown
• [petsc-dev] preparing for a PETSc release   Blaise Bourdin
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Victor Minden
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] writing PETSc code with no memory leaks   Barry Smith
• [petsc-dev] sieve examples seem totally broken?   Barry Smith
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] preparing for a PETSc release   Blaise Bourdin
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] ! is only acceptable comment character in PETSc Fortran code   Barry Smith
• [petsc-dev] preparing for a PETSc release   Blaise Bourdin
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] preparing for a PETSc release   Blaise Bourdin
• [petsc-dev] two quick questions on Fortran style/includes   Ethan Coon
• [petsc-dev] two quick questions on Fortran style/includes   Jed Brown
• [petsc-dev] two quick questions on Fortran style/includes   Ethan Coon
• [petsc-dev] two quick questions on Fortran style/includes   Jed Brown
• [petsc-dev] two quick questions on Fortran style/includes   Ethan Coon
• [petsc-dev] PetscBag not a PetscObject?   Ethan Coon
• [petsc-dev] two quick questions on Fortran style/includes   Jed Brown
• [petsc-dev] two quick questions on Fortran style/includes   Barry Smith
• [petsc-dev] two quick questions on Fortran style/includes   Barry Smith
• [petsc-dev] two quick questions on Fortran style/includes   Satish Balay
• [petsc-dev] PetscBag not a PetscObject?   Barry Smith
• [petsc-dev] PetscBag not a PetscObject?   Satish Balay
• [petsc-dev] writing PETSc code with no memory leaks   Lisandro Dalcin
• [petsc-dev] writing PETSc code with no memory leaks   Satish Balay
• [petsc-dev] writing PETSc code with no memory leaks   Barry Smith
• [petsc-dev] Problems with Intel c++ compiler   Satish Balay
• [petsc-dev] Problems with Intel c++ compiler   Satish Balay
• [petsc-dev] preparing for a PETSc release   Matthew Knepley
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Alexander Grayver
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Victor Minden
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Alexander Grayver
• [petsc-dev] CMake broken   Jose E. Roman
• [petsc-dev] CMake broken   Barry Smith
• [petsc-dev] CMake broken   Satish Balay
• [petsc-dev] petsc shared libraries on cygwin?   Brad Aagaard
• [petsc-dev] petsc shared libraries on cygwin?   Brad Aagaard
• [petsc-dev] petsc shared libraries on cygwin?   Satish Balay
• [petsc-dev] petsc shared libraries on cygwin?   Lisandro Dalcin
• [petsc-dev] petsc shared libraries on cygwin?   Brad Aagaard
• [petsc-dev] Multiphysics section in the User's Manual   Jed Brown
• [petsc-dev] petsc shared libraries on cygwin?   Brad Aagaard
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Lisandro Dalcin
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Barry Smith
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Lisandro Dalcin
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Barry Smith
• [petsc-dev] autogeneration of petscconf.h for C, C++ and Fortran   Barry Smith
• [petsc-dev] autogeneration of petscconf.h for C, C++ and Fortran   Jed Brown
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Lisandro Dalcin
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Barry Smith
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Barry Smith
• [petsc-dev] autogeneration of petscconf.h for C, C++ and Fortran   Barry Smith
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Lisandro Dalcin
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Lisandro Dalcin
• [petsc-dev] autogeneration of petscconf.h for C, C++ and Fortran   Jed Brown
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Jed Brown
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Sean Farley
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Lisandro Dalcin
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Barry Smith
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Jed Brown
• [petsc-dev] Remove calls to XXXReset() in XXXDestroy()   Barry Smith
• [petsc-dev] Question re parallel sparse Matrix-vector / KSP solvers   David Henty
• [petsc-dev] Question re parallel sparse Matrix-vector / KSP solvers   Barry Smith
• [petsc-dev] preparing for a PETSc release   Barry Smith
• [petsc-dev] Multiphysics section in the User's Manual   Barry Smith
• [petsc-dev] SuperLU link error on BGP FEN   Aron Ahmadia
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Matthew Knepley
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] ensuring consistency with f2py, fortran/petsc4py interoperability   Aron Ahmadia
• [petsc-dev] ensuring consistency with f2py, fortran/petsc4py interoperability   Satish Balay
• [petsc-dev] ensuring consistency with f2py, fortran/petsc4py interoperability   Jed Brown
• [petsc-dev] problem with DMGetInterpolation_DA_2D_Q1() for whoever was monkeying with it   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] problem with DMGetInterpolation_DA_2D_Q1() for whoever was monkeying with it   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Matthew Knepley
• [petsc-dev] ensuring consistency with f2py, fortran/petsc4py interoperability   Matthew Knepley
• [petsc-dev] attaching field information to PetscLayout?   Jed Brown
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Dmitry Karpeev
• [petsc-dev] attaching field information to PetscLayout?   Barry Smith
• [petsc-dev] attaching field information to PetscLayout?   Matthew Knepley
• [petsc-dev] problem with DMGetInterpolation_DA_2D_Q1() for whoever was monkeying with it   Barry Smith
• [petsc-dev] Fwd: [ACTS-news] DOE ACTS Collection Newsletter, May 2011   Barry Smith
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Victor Minden
• [petsc-dev] [petsc-maint #72279] PETSc and multigpu   Alexander Grayver
• [petsc-dev] errors in PETSc dev code, please remember precisions   Barry Smith
• [petsc-dev] cmakeboot.py is a total disaster needs fixing or removal   Satish Balay
• [petsc-dev] cmakeboot.py is a total disaster needs fixing or removal   Barry Smith
• [petsc-dev] cmakeboot.py is a total disaster needs fixing or removal   Jed Brown
• [petsc-dev] incomplete fix for MatSetValuesStencil() someone recently made   Barry Smith
• [petsc-dev] cmakeboot.py is a total disaster needs fixing or removal   Barry Smith
• [petsc-dev] cmakeboot.py is a total disaster needs fixing or removal   Satish Balay
• [petsc-dev] incomplete fix for MatSetValuesStencil() someone recently made   Lisandro Dalcin
• [petsc-dev] errors in PETSc dev code, please remember precisions   Lisandro Dalcin
• [petsc-dev] errors in PETSc dev code, please remember precisions   Barry Smith
• [petsc-dev] incomplete fix for MatSetValuesStencil() someone recently made   Lisandro Dalcin
• [petsc-dev] incomplete fix for MatSetValuesStencil() someone recently made   Jed Brown
• [petsc-dev] sieve examples seem totally broken?   Matthew Knepley
• [petsc-dev] PCFieldSplit broken, what was intended?   Jed Brown
• [petsc-dev] PCFieldSplit broken, what was intended?   Barry Smith
• [petsc-dev] PCFieldSplit broken, what was intended?   Jed Brown
• [petsc-dev] PCFieldSplit broken, what was intended?   Barry Smith
• [petsc-dev] PCFieldSplit broken, what was intended?   Jed Brown
• [petsc-dev] PCFieldSplit broken, what was intended?   Barry Smith
• [petsc-dev] What was the 64-bit problem with pow()?   Jed Brown
• [petsc-dev] What was the 64-bit problem with pow()?   Jed Brown
• [petsc-dev] Petsc Make error   Jeswin Godwin
• [petsc-dev] Potential memory issue with block jacobi preconditioner   fabien delalondre
• [petsc-dev] Potential memory issue with block jacobi preconditioner   Matthew Knepley
• [petsc-dev] Potential memory issue with block jacobi preconditioner   fabien delalondre
• [petsc-dev] Potential memory issue with block jacobi preconditioner   Matthew Knepley
• [petsc-dev] What was the 64-bit problem with pow()?   Barry Smith
• [petsc-dev] What was the 64-bit problem with pow()?   Matthew Knepley

Last message date: Tue May 31 21:56:45 CDT 2011
Archived on: Wed Aug 23 15:48:56 CDT 2017

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...