On Mon, 11 Aug 2008, Vijay S. Mahadevan wrote: > But now, when I try to call get_data on MeshData, the assertion > > libmesh_assert (_elem_data_closed); > > fails in /libmesh/include/mesh/mesh_data.h, line 956. > > Of course, I'm out of ideas as to how to close() the mesh_data after > setting the data for elems and nodes. Is there a simple call that > would solve my problem or do I really have to call insert_node_data > and insert_elem_data after building the entire array of data. IMO, the > second method seems tedious and is a big requirement on the user part.
I agree. I think the problem is simply that none of the active libMesh developers are MeshData users, so it's about all we can do to keep that functionality from regressing; there's nobody who works with it enough to make informed changes to what may be some flawed API design decisions. Looking over the code, I don't see any better close() method than what you've already identified. We could certainly use one, though; a patch would be appreciated. --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
