I think I mentioned this before, but at that point I found a workaround.
But now I'm stuck again...
So - let's say I have a datastructure that is indexed by element id. If
I'm using parallel mesh and adaptivity when the mesh is repartitioned
elements can be sent from one processor to another, right? And the element
ids can change at that point, right?
How do I send the data associated with that element (or node or whatever)
to that other processor?
I am thinking that we need a globally unique identifier for all dof
objects. This would be a serially increasing number that would be attached
to the dof object. When a dof object gets sent over the wire and its "id"
is changed... the unique identifier would stay the same... so we could
always match up data that goes with it.
Last time I ran into this I switched to using Element pointers to index off
of instead... because even if the ID changes the pointer never does.... but
that doesn't work in the case of repartitioning (or a bunch of other
circumstances).
What do you guys think? Are you willing to put an "unsigned long int" into
DofObject? How much memory would we lose....
Derek
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
