On Wed, Dec 5, 2018 at 8:51 AM Stogner, Roy H
wrote:
>
> On Tue, 4 Dec 2018, David Knezevic wrote:
>
> > Yep, geometry is irrelevant for me. Also, I'm using ReplicatedMesh
> > currently, so I gather that geometric ghosting is not an issue
> > anyway.
>
> That's correct.
>
> > Hmm, ok... well this
On Tue, 4 Dec 2018, David Knezevic wrote:
> Yep, geometry is irrelevant for me. Also, I'm using ReplicatedMesh
> currently, so I gather that geometric ghosting is not an issue
> anyway.
That's correct.
> Hmm, ok... well this is interesting. I've used the approach I
> described a lot on 3D mesh
Hi Roy,
Thanks for your comments, I've replied below:
On Tue, Dec 4, 2018 at 5:01 PM Stogner, Roy H
wrote:
>
> On Tue, 4 Dec 2018, David Knezevic wrote:
>
> > I use NodeElems with GhostingFunctor to couple unconnected nodes (i.e. I
> > attach NodeElems to the nodes that I want to couple), and t
On Tue, 4 Dec 2018, David Knezevic wrote:
> I use NodeElems with GhostingFunctor to couple unconnected nodes (i.e. I
> attach NodeElems to the nodes that I want to couple), and this works well.
> However, I realized that this approach requires me to set the processor_id
> in the NodeElem to matc
I use NodeElems with GhostingFunctor to couple unconnected nodes (i.e. I
attach NodeElems to the nodes that I want to couple), and this works well.
However, I realized that this approach requires me to set the processor_id
in the NodeElem to match the processor_id of the Node that it points to, as
