On Fri, Jan 26, 2018 at 11:06 AM, Roy Stogner
wrote:
>
> On Thu, 25 Jan 2018, David Knezevic wrote:
>
> Thanks for that info. I'm only using ReplicatedMesh for now. Regarding
>> this:
>>
>> IIRC: on ReplicatedMesh we try to avoid communication as much
>> as possible, so you have to add user
On Thu, 25 Jan 2018, David Knezevic wrote:
Thanks for that info. I'm only using ReplicatedMesh for now. Regarding this:
IIRC: on ReplicatedMesh we try to avoid communication as much as
possible, so you have to add user constraints identically on
every processor. There might be wa
Hi Roy,
Thanks for that info. I'm only using ReplicatedMesh for now. Regarding this:
IIRC: on ReplicatedMesh we try to avoid communication as much as possible,
> so you have to add user constraints identically on every processor. There
> might be ways to get around that (add local constraints on
On Thu, 25 Jan 2018, David Knezevic wrote:
Hi all (though Roy I think you're the expert on this one ;) ),
Well, I was the least-amateur when I refactored the code, but an
*expert* would have also properly documented it, so apparently none of
those were available.
I know that in DofMap::proc
Hi all (though Roy I think you're the expert on this one ;) ),
I know that in DofMap::process_constraints libMesh handles communicating
the constraint rows to the processes that need to know about them, but I
just want to make sure that I satisfy any requirements that we have on how
user-defined c
