| Line | |
|---|
| 1 | |
|---|
| 2 | OPEN ISSUES: |
|---|
| 3 | ------------ |
|---|
| 4 | |
|---|
| 5 | |
|---|
| 6 | Issue: Segments is pmesh used to separate regions |
|---|
| 7 | (e.g. for different resolution) will appear as an *internal* |
|---|
| 8 | boundary in the resulting domain even though it isn't intended to have a boundary condition applied. |
|---|
| 9 | Background: Genuine internal boundaries are created the same way as |
|---|
| 10 | external boundaries through the 'boundary' dictionary mapping triagle_id |
|---|
| 11 | and edge number to a tag. |
|---|
| 12 | When a mesh is created, this dictionary will override the neighbour structure |
|---|
| 13 | and thereby enforce the internal boundary status. |
|---|
| 14 | However, once a segment belongs to a boundary (internal or external) it must be bound to a boundary condition object in order to supply values for the |
|---|
| 15 | flux computations. |
|---|
| 16 | An older version of pyvolution allowed None as a boundary object which |
|---|
| 17 | probably meant that a zero dirichlet condition was imposed. |
|---|
| 18 | Not sure about this, though. |
|---|
| 19 | Importance: High |
|---|
| 20 | Suggested Action: Have pmesh ignore segments that aren't being tagged |
|---|
| 21 | and that way they are only used to to define regions |
|---|
| 22 | (e.g. for variable resolution). |
|---|
| 23 | Status: Unresolved |
|---|
Note: See
TracBrowser
for help on using the repository browser.
