On Thu, 3 Apr 2008, Tim Kroeger wrote: > Dear John, > > On Thu, 3 Apr 2008, John Peterson wrote: > >> Roy could give you more details I think, but I'm fairly certain it had >> to do with the parallelization of the mesh.
Actually, Ben was the one to make those changes, but yes, it was part of the ParallelMesh I/O development. You'll have to ask him for the details. ;-) >> Is elem->id() not suitable for your purposes? > > Good question. Maybe, when I looked for a function that serves my > purpose, I didn't find that for whatever reason -- or let's say I > found Elem::key() first. If Elem::id() returns a unique value, it is > certainly the right thing for me. One potential problem is that elem->id() is unique, but not fixed. Mesh refinement, repartitioning, basically anything requiring an EquationSystems::reinit() will cause those ids to be renumbered. On the other hand, I think this was the case with Elem::key() as well. --- Roy ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
