From: Michael Povolotskyi <mpovolot@pu...> - 2010-12-16 02:22:40
Dear Libmesh developers,
I have a question about the node id.
Is it assumed in the libmesh code that node id's are not just the unique
numbers but rather belong to consecutive set from 0 to n?
I ask because of the function void libMesh::TecplotIO::write_ascii(...).
In this function there is a loop:
for (unsigned int i=0; i<mesh.n_nodes(); i++)
// Print the point without a newline
I'm asking this because I've created a mesh myself with node id's being unique but not consecutive numbers. The code worked well until
From: Roy Stogner <roystgnr@ic...> - 2010-12-18 05:05:51
On Wed, 15 Dec 2010, Michael Povolotskyi wrote:
> Dear Libmesh developers,
> I have a question about the node id.
> Is it assumed in the libmesh code that node id's are not just the unique
> numbers but rather belong to consecutive set from 0 to n?
I think we don't make that assumption in most code, but we do renumber
nodes and elements to make them contiguous during a typical
prepare_for_use and I think many of the IO methods assume they're
Also SerialMesh stores things in vectors indexed by ID; *too* much
sparsity would be a memory suck.