[MOAB-dev] boundary nodes on parallel mesh

[Timothy Tautges]

Draw an example out on paper with a ghost layer and mark shared, skin, etc
and it will be clear.
On Nov 1, 2015 7:45 PM, "Nico Schlömer" <nico.schloemer at gmail.com> wrote:

> Yes, that would be much appreciated! (I don't understand from the thread
> [1] what exactly the solution is. People talk about a fork of sorts, shared
> and owned filtering etc. A piece of code in the FAQs would help.)
>
> By the way, where do I find the FAQs? :)
>
> --Nico
>
> [1] http://lists.mcs.anl.gov/pipermail/moab-dev/2013/005509.html
>
> On Mon, Nov 2, 2015 at 2:40 AM Timothy Tautges <
> timothy.tautges at cd-adapco.com> wrote:
>
>> Moab folks, this should be put in the faq if it isn't there already.
>> On Nov 1, 2015 7:38 PM, "Timothy Tautges" <timothy.tautges at cd-adapco.com>
>> wrote:
>>
>>> I think that's still the way.
>>>
>>> - tim
>>> On Nov 1, 2015 7:27 PM, "Nico Schlömer" <nico.schloemer at gmail.com>
>>> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> As I'm diving deeper into MOAB, more questions pop up. Right now: I
>>>> need to loop over the actual physical boundary of a parallel mesh and get
>>>> the node IDs and their coordinates.
>>>>
>>>> I found an old mailing list thread on the topic [1], but I'm not sure
>>>> it was conclusive. What's the current best practice here?
>>>>
>>>> Cheers,
>>>> Nico
>>>>
>>>> [1] http://lists.mcs.anl.gov/pipermail/moab-dev/2013/005509.html
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20151101/4766095f/attachment.html>