#671 GridFactory: index translation for coarse grid creation
Metadata
Property | Value |
---|---|
Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Reported at | Nov 30, 2009 10:51 |
Type | Bug Report |
Version | Unknown |
Operating System | Unspecified / All |
Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Last edited at | Mar 23, 2010 14:20 |
Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Closed at | Mar 23, 2010 14:20 |
Closed in version | 2.0 |
Resolution | Implemented |
Comment |
Description
From the protocol:
Data stored in files must be associated with entities in a grid-file. The GridFactory must provide the necessary infrastructure…
Two proposals:
-
level-0 elements/vertices/(boundary-segments) are numbered in the order of insertion (only level-0-indexSet).
-
add some kind of indexSet to translate between insertionIndex and entityIndex (methods on the grid factory).
Both indices are only valid until you first modify the grid (e.g. refine, load balance).
Arguments:
* (1) is easier fo the user
* (1) principle of least surprise
* (1) helps for debugging
* (1) requires changes to the grid managers
* (2) imposes less restrictions on future grids
* (2) more efficient (for certain grids) during computation
* (2) requires reorder of data during setup phase
Vote:
-
insertion order: 5
-
indexSet: 6
-
abstained: 3