#1258 ALUGrid: Invalid global Ids during load balance
Metadata
| Property | Value |
|---|---|
| Reported by | Bernd Flemisch (bernd@iws.uni-stuttgart.de) |
| Reported at | Feb 22, 2013 12:16 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
Description
During the scatter step of the load balancing, the global Ids are not persistent. The attached program triggers the issue:
Process 0: 0: 0.5 0.5 0.5: gather id ([2,3,8,14],8,0) 0: 0.7 0.5 0.5: gather id ([3,4,9,15],8,0) 0: 0.9 0.5 0.5: gather id ([4,5,10,16],8,0) Process 1: 1: 0.5 0.5 0.5: scatter id ([2,3,8,14],71,0) 1: 0.7 0.5 0.5: scatter id ([2,3,8,14],70,0) 1: 0.9 0.5 0.5: scatter id ([2,3,8,14],69,0)
This bug report evolved from a mailing list discussion, http://lists.dune-project.org/pipermail/dune/2013-February/012211.html
The final comment from Andreas there sums it up: I assumed so far that the global ids are available during gather/scatter but probably they are not since they are constructed through the dune bindings after the load balance is complete. So in gather/scatter only local ids seem to be available. As Martin said, Bernd seems to be the first who tried to use global ids together with the callback load balancing. I guess this has to be chalked down as a 'known bug' in alu at the moment....