[Libmesh-users] Stiffness matrix in Adaptive Mesh Refinement

2014-09-03 Thread Miguel Angel Salazar de Troya
Hello all In this paper http://arxiv.org/pdf/1009.4975.pdf In page 9, at the bottom, they mention this: As indicated by the circled nodes in Figure 3(a), level-one mesh incompatibility results in hanging nodes. The libMesh package handles those hanging nodes by using the projection method to en

[Libmesh-users] Fwd: Postdoctoral position at ANL/MCS (CHiMaD)

2014-09-03 Thread Dmitry Karpeyev
Dear All, Sorry to spam this list, but I thought the following job opportunity may be of interest to many libMesh users. Regards, Dmitry. *Postdoctoral position at the Center for Hierarchical Materials Design* We have an opening for a postdoctoral position in the Center for Hierarchical Mater

Re: [Libmesh-users] libMesh on Mac OS X

2014-09-03 Thread Roy Stogner
On Wed, 3 Sep 2014, Andrew Davis wrote: > auto mesh = make_shared(); > > to > > auto mesh = make_shared(libMesh::Parallel::Communicator()); > Ly, libMesh::QUAD9); Not quite. That default Communicator constructor uses MPI_COMM_NULL, which is almost certainly not what you want. If you just want

Re: [Libmesh-users] libMesh on Mac OS X

2014-09-03 Thread Andrew Davis
Thanks! That helps a lot. I have reinstalled with GCC and everything seems to be compiling. However, the issue may not have been the compiler. I realized I haven't updated libmesh in a while. I did a "git pull" on my Ubuntu machine (where everything was previously working fine) and ran into som

Re: [Libmesh-users] Neighbors that are not in the current processor

2014-09-03 Thread Miguel Angel Salazar de Troya
I ended up building the parallel matrix from the beginning, so no need to copy it from a serial matrix. My apologies for the inconvenience. On Tue, Sep 2, 2014 at 3:49 PM, Miguel Angel Salazar de Troya < salazardetr...@gmail.com> wrote: > Could anyone help me with this one please? How could I co

Re: [Libmesh-users] Modifying the solution vector

2014-09-03 Thread Miguel Angel Salazar de Troya
I ended up writing the conditional to let work just one processor work for only the routines where I'm writing global vectors. A barrier right after this conditional synchronizes the processors. I leave the assembly and solve routines out so I can call them with all the processors. Including them i