I've never tried this, but at a minimum something like dof_map.reinit() would
be needed I think, as it is here the object->dof index mapping is constructed.
The map stating which variables are active where is still valid, but the
changes in the mesh are not automatically propagated.
-Ben
On
On Nov 15, 2013, at 12:15 AM, John Peterson
wrote:
> Would it be possible to have the mesh_inserter_iterator do something other
> than call mesh.add_node(n)? I think if it did something with logic more
> similar to Mesh::add_point(), which inserts a node with a valid ID in the
> appropriate
On Fri, Nov 15, 2013 at 7:13 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> On Nov 15, 2013, at 12:15 AM, John Peterson
> wrote:
>
> > Would it be possible to have the mesh_inserter_iterator do something
> other than call mesh.add_node(n)? I think if it did something with log
On Fri, 15 Nov 2013, John Peterson wrote:
All I'm proposing at the moment is to try and make sure that various parts of
the library are working OK with _nodes and
_elements vectors that have NULLs in them.
That shouldn't be too much trouble. We have a lot of things in the
library that are
On Fri, Nov 15, 2013 at 10:12 AM, Roy Stogner wrote:
>
> On Fri, 15 Nov 2013, John Peterson wrote:
>
> All I'm proposing at the moment is to try and make sure that various
>> parts of the library are working OK with _nodes and
>> _elements vectors that have NULLs in them.
>>
>
> That shouldn't be
