Re: [Libmesh-devel] [libmesh] Consider Eigen/Suitesparse as a Laspack alternative for "serial" configs (#44)

2013-02-17 Thread roystgnr
Fantastic - thanks, Ben! --- Reply to this email directly or view it on GitHub: https://github.com/libMesh/libmesh/issues/44#issuecomment-13698058 -- The Go Parallel Website, sponsored by Intel - in partnership with Geekn

Re: [Libmesh-devel] [libmesh] Consider Eigen/Suitesparse as a Laspack alternative for "serial" configs (#44)

2013-02-21 Thread roystgnr
On Thu, 21 Feb 2013, Benjamin S. Kirk wrote: > Argh!!! MatType is a template parameter for Eigen, and a #define by PETSc... A #define in which PETSc header? It seems like we should be trying to keep that out of non-petsc-related source files regardless. --- Reply to this email directly or view

Re: [Libmesh-devel] [libmesh] Allow for alternate communicators in parallel objects (#71)

2013-04-04 Thread roystgnr
I'll put together a "FakeCommunicator" class implementation sometime today or tonight, then, and we can try it out. The stack trace should work just fine. We do want Mesh(CommWorld) to fail in the --disable-default-comm case, and we also want Mesh() to fail... but we want *some* way to create a

Re: [Libmesh-devel] [libmesh] Allow for alternate communicators in parallel objects (#71)

2013-04-04 Thread roystgnr
What's the proper git procedure for this? Create a roystgnr/libmesh/fake_comm branch, regularly "pull --rebase" from benkirk/libmesh/communicators, then set up a pull request back to benkirk/libmesh/communicators when I'm done? --- Reply to this email directly or view