#266 Semantics of adaptation and refinement methods
Metadata
| Property | Value |
|---|---|
| Reported by | Carsten Gräser (graeser@math.fu-berlin.de) |
| Reported at | Feb 26, 2007 13:59 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Carsten Gräser (graeser@math.fu-berlin.de) |
| Last edited at | Jul 13, 2009 16:23 |
| Closed by | Carsten Gräser (graeser@math.fu-berlin.de) |
| Closed at | Jul 13, 2009 16:23 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment | Fixed by enhenced doc in rev5301. |
Description
Semantics of preAdapt(), adapt(), postAdapt(), globalRefine(), mightBeCoarsened() are unclear. The documentation does not answer the following questions:
-
Must preAdapt() be called before adapt() ?
-
Must postAdapt() be called after adapt() (and before marking elements again) ?
-
How does the grid state differ before and after preAdapt(), adapt() and postAdapt() ?
-
Must preAdapt() be called before globalRefine() ?
-
Must postAdapt() be called after globalRefine() ?
-
Is the state after globalRefine() the same as after adapt() or postAdapt() ?
-
Does "element might be coarsened" mean "element might disappear" or "elements children might diappear" ?