Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > I've run meshes with several million elements on my desktop with several > non-linear variables per DOF without memory issues. The mesh data structure > is relatively small compared to your equation systems (unless you are > running really simple "single" physics problems). If it fits in memory

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Cody Permann
I've run meshes with several million elements on my desktop with several non-linear variables per DOF without memory issues. The mesh data structure is relatively small compared to your equation systems (unless you are running really simple "single" physics problems). If it fits in memory, you'll a

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > At that point there's little reason to bother using a ParallelMesh at > all; after an allgather it's become a less-efficient-than-SerialMesh > serial mesh. > You can use a point locator on the distributed mesh without > serializing first; you just have to account for the fact that it will >

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > For now I just keep all the elements on all processes (basically > SerialMesh). > > Why not just use SerialMesh? > I was initially trying to have only the required elements on each process, since the mesh could get big (100,000+ elements). I would like to be able to do that, so I haven't cha

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Cody Permann
Why not just use SerialMesh? On Tue, Sep 22, 2015 at 3:33 PM Harshad Sahasrabudhe wrote: > > > > I initially use the Poisson mesh point locator on quadrature points > > of the second mesh to find the elements of Poisson mesh > > > > Hmm.. assuming the point locator is up to date, that should giv

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Roy Stogner
On Tue, 22 Sep 2015, Harshad Sahasrabudhe wrote: > I forgot to mention that I call allgather() on the Poisson mesh and > reinitialize the point locator before calling it. At that point there's little reason to bother using a ParallelMesh at all; after an allgather it's become a less-efficient-th

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > I initially use the Poisson mesh point locator on quadrature points > of the second mesh to find the elements of Poisson mesh > Hmm.. assuming the point locator is up to date, that should give you > semilocal elements or NULL, but shouldn't give you anything with an > invalid_id. I'm stumped.

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Roy Stogner
On Tue, 22 Sep 2015, Harshad Sahasrabudhe wrote: > I initially use the Poisson mesh point locator on quadrature points > of the second mesh to find the elements of Poisson mesh Hmm.. assuming the point locator is up to date, that should give you semilocal elements or NULL, but shouldn't give you

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
I don't understand this. An element (and therefore all quadrature points on that element) is either entirely owned by a processor or is entirely not. Do you have a coarser grid that you're integrating on? > Each element is entirely on one process, but the quantity that I'm

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > I don't understand this. An element (and therefore all quadrature > points on that element) is either entirely owned by a processor or is > entirely not. Do you have a coarser grid that you're integrating on? > > Each element is entirely on one process, but the quantity that

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Roy Stogner
On Tue, 22 Sep 2015, Harshad Sahasrabudhe wrote: I don't understand this.  An element (and therefore all quadrature points on that element) is either entirely owned by a processor or is entirely not.  Do you have a coarser grid that you're integrating on? Each element is enti

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > Not sure what this means: "quantity is not available for all quadrature > points of some elements on one process" You shouldn't be computing anything on ghosted elements... they will be the > responsibility of the processor that owns them. So the reason why that quantity isn't available on t

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Harshad Sahasrabudhe
> > I don't understand this. An element (and therefore all quadrature > points on that element) is either entirely owned by a processor or is > entirely not. Do you have a coarser grid that you're integrating on? Each element is entirely on one process, but the quantity that I'm integrating isn

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread John Peterson
On Tue, Sep 22, 2015 at 2:42 PM, Harshad Sahasrabudhe wrote: > Hi, > > I'm using ParallelMesh to discretize the Poisson equation. I want to > integrate a certain quantity over each element. That quantity is not > available for all quadrature points of some elements on one process (such > elements

Re: [Libmesh-users] ParallelMesh: Identify elements across processes

2015-09-22 Thread Roy Stogner
On Tue, 22 Sep 2015, Harshad Sahasrabudhe wrote: > I'm using ParallelMesh to discretize the Poisson equation. I want to > integrate a certain quantity over each element. That quantity is not > available for all quadrature points of some elements on one process (such > elements are ghosted), so I