On Wed, Jun 15, 2016 at 4:29 PM Roy Stogner <[email protected]> wrote:
> > On Wed, 15 Jun 2016, Cody Permann wrote: > > > I'm running into what appears to be either a bug or a misunderstanding on > > my part. I'm trying to run a 3D adaptive simulation for the first time > on a > > phase-field problem and running into problems accessing elemental DOFs > that > > I thought that I owned but apparently whose values are not in the PETSc > > vector. > > > > My understanding has been that this assumption should hold for all > libMesh > > simulations: > > > > local dofs + ghosted dofs = semi-local dofs > > I'm afraid not, even restricting the conversation to active elements. > Only active neighbors on sides get their dofs ghosted, but point > neighbors are still kept as semilocal elements. > --- > Roy > Well this is good news. This means that this is not a libMesh bug! What is the use for semi-local then? If it's not a record of what's ghosted, what do people use it for? Based on what little information I've given you about my problem, what suggestion would you have for when about when I can expect to safely access an off-processor DOF and when I cannot based on the libMesh API? Thanks! Cody ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
