Re: [Libmesh-users] Introduction Example 4 with Nodal BC's

On Tue, 7 Aug 2012, Onur Solmaz wrote: I finally did it, however I started to have some other problems. In a short list: 1. I am trying to call libmesh from another function than main(). This works, but I'm not sure if this is the best way to do so. I use fake arguments for LibMeshInit()   i

Re: [Libmesh-users] variable number of variables per element

Thanks Roy for your comments, I do not understand your comment below though, Even if the mesh is stored on all processors, your degree of freedom coefficients won't be. You'll need to communicate "ghost" data on processor boundaries. NumericVector::localize() is what we typically use for that

Re: [Libmesh-users] variable number of variables per element

On Mon, 6 Aug 2012, Danny Lathouwers - TNW wrote: > Q: data is regularly required from a neighbouring element that is on > another processor. Normally one would use MPI calls for this access. > Is there a more high-level command available in Libmesh to access > data on other processors or do we n

Re: [Libmesh-users] variable number of variables per element

Thank you John and Roy for your responses so far. It seems that pre-declaring all variables that we might ever use is impossible in our case (estimate: 32000 variables would be needed ...). I have a possible work-around though: we could define a single variable in Libmesh. Our own variables are