On Tue, Jan 12, 2016 at 6:07 PM, David Knezevic <david.kneze...@akselos.com> wrote:
> I'm assembling a non-local term (specifically some LHS values on either > side of a contact interface). Let's consider a simple case: node A on proc > 0 is on one side of the interface, and node B on proc 1 is on the other > side. Suppose that node A has a dof_constraint_row associated with it > (stored on proc 0), and that we're assembling the term on proc 1. > > The issue I'm running into is that the constraints on node A do not get > enforced because proc 1 doesn't know anything about that constraint row on > proc 0. > > I added the node A and node B dofs to the send lists, but as far as I know > that doesn't affect the communication of the constraints. > > Is there a standard way to deal with this situation? I gather that I need > a way to communicate the _dof_constraints. I could do this manually, but I > thought there might already be a way to handle this? > > Thanks, > David > It looks like DofMap::scatter_constraints is the method I had in mind. That doesn't scatter the non-local constraints in my case, though. I think I'll just send the constraint rows via my own Communicator::send calls, since I don't see an easy alternative (though if anyone has any alternative suggestions, I'd be interested to hear them!). David ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
