I have started to work on this now, and have the following question:
Each element in the boundary mesh keeps a pointer to its parent in the
original mesh. So, if I use MeshSerializer to serialize the boudnary mesh,
I am assuming that it will also retain the parent element's pointer in the
serializ
On Mon, 9 Sep 2013, Manav Bhatia wrote:
Thanks for your detailed message!
I looked throught the code, and feel like this might be a better solution
for my case: specialize the MeshSerializer
so that only the elements with sides that have boundary ids specified through
an input are s
Hi Roy,
Thanks for your detailed message!
I looked throught the code, and feel like this might be a better
solution for my case: specialize the MeshSerializer so that only the
elements with sides that have boundary ids specified through an input are
serialized. This should make it easier
On Mon, 9 Sep 2013, Manav Bhatia wrote:
I have started to work on this now, and have the following question:
Each element in the boundary mesh keeps a pointer to its parent in the original
mesh. So, if I use MeshSerializer to serialize the boudnary mesh, I am
assuming that it will also retai
On Fri, 6 Sep 2013, Manav Bhatia wrote:
-- BoundaryInfo::sync() still calles the MeshSerializer on the parent mesh.
Considering that this is a bottleneck that
I am trying to get away from, is this something that can somehow be
circumvented?
It's something that circumvents itself. Investi
A couple of questions:
-- BoundaryInfo::sync() still calles the MeshSerializer on the parent
mesh. Considering that this is a bottleneck that I am trying to get away
from, is this something that can somehow be circumvented?
-- Is it possible to create a BoundaryMesh and then call the
MeshSeria
On Sep 6, 2013, at 3:01 PM, Roy Stogner
wrote:
>
> Whoa, wait a minute:
>
> Didn't we fix that abuse? There's now an Elem::interior_parent()
> method; I added that a year or two ago to fix up the interaction
> between boundary meshes and adaptive meshes.
Indeed - your memory is better than m
Whoa, wait a minute:
Didn't we fix that abuse? There's now an Elem::interior_parent()
method; I added that a year or two ago to fix up the interaction
between boundary meshes and adaptive meshes.
---
Roy
On Fri, 6 Sep 2013, Kirk, Benjamin (JSC-EG311) wrote:
> On Sep 6, 2013, at 2:25 PM, Manav
Thanks, Roy.
I will give this a go and let you know if any issues come up.
-Manav
On Fri, Sep 6, 2013 at 4:24 PM, Roy Stogner wrote:
>
> On Fri, 6 Sep 2013, Manav Bhatia wrote:
>
> -- BoundaryInfo::sync() still calles the MeshSerializer on the parent
>> mesh. Considering that this is a bottlenec
Ah.. awesome.. just what I was looking for..!!
Thanks Ben.
-Manav
On Fri, Sep 6, 2013 at 3:39 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> On Sep 6, 2013, at 2:25 PM, Manav Bhatia wrote:
>
> > It appears from the code that the BoundaryMesh creates a new set of
> > nodes and
On Sep 6, 2013, at 2:25 PM, Manav Bhatia wrote:
> It appears from the code that the BoundaryMesh creates a new set of
> nodes and elements for its own purpose. So, I am not sure how this could be
> mapped back to the solution vector of the original system.
>
>I would appreciate any inputs.
Hi,
I am trying to figure out how to use BoundaryMesh to iterate over
nodes/sides on the boundary and get the associated variable values
(assuming Lagrange elements) from the system solution.
It appears from the code that the BoundaryMesh creates a new set of
nodes and elements for its ow
12 matches
Mail list logo
