HI John, Thanks for clearing that up. Is there a way to only locate elements belonging to the processor from which PointLocator is called?
Assume I'm using a SerialMesh for now. If I get an off-processor element containing a point, I send the point to the processor which owns the element. When I run PointLocator again on the processor to which this point was sent, I get a different adjoining semi-local element. This is causing problems in my application. Thanks, Harshad On Wed, Sep 28, 2016 at 11:01 AM, John Peterson <jwpeter...@gmail.com> wrote: > > > On Wed, Sep 28, 2016 at 8:03 AM, Harshad Sahasrabudhe <hsaha...@purdue.edu > > wrote: > >> Hi, >> >> I'm using Point locator to find elements containing certain points. For a >> ParallelMesh, can there be cases where the PointLocator returns different >> elements on different processors for the same point (e.g. when the point >> is >> a node). How are points located at the nodes handled, since the node >> technically belongs to all the neighboring elements. >> > > This can happen even if you are just using ReplicatedMesh, if you build > the PointLocator passing TREE_LOCAL_ELEMENTS. It's up to the application > to decide what to do with the results. In some cases it may not matter. > In MOOSE, we do an extra parallel communication, and pick the element with > the lowest ID as the element all processors agree the point is in. > > -- > John > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
