I'm using a PointLocator to copy a solution onto a boundary mesh, and I was initially using the following steps:
1. extract the boundary mesh using mesh->boundary_info->sync(surface_ids, boundary_mesh); 2. get a PointLocator for the full mesh, using AutoPtr<PointLocatorBase> point_locator = full_mesh.sub_point_locator(); 3. loop over the nodes and elements of boundary_mesh and use point_locator from 2 to find out which element each node and element belongs to, and then copy the solution over to a system defined on the boundary mesh This worked well. But then I ran into some problems when I did the above several times in a row with different surface_ids. In this case the PointLocator seemed to grind to a halt. I then added "system.get_mesh().clear_point_locator()" in step 2 before the call to sub_point_locator, and that fixed the issue. So I was just wondering what might've been going wrong here, and why (and when) it's necessary to clear the point_locator? Thanks, David ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
