| 1 | |
|---|
| 2 | OPEN ISSUES: |
|---|
| 3 | ------------ |
|---|
| 4 | |
|---|
| 5 | |
|---|
| 6 | Issue: Pmesh do not write in msh format |
|---|
| 7 | Importance: Mid-High |
|---|
| 8 | Action: See under pmesh/documentation |
|---|
| 9 | |
|---|
| 10 | Issue: geo_reference is not passed into domain and further on to sww file. Hence we can't export results properly to e.g GIS |
|---|
| 11 | Importance: High |
|---|
| 12 | Action: Make it happen! |
|---|
| 13 | |
|---|
| 14 | Issue: With reflective boundaries, and very small timesteps and very shallow |
|---|
| 15 | stage, there seems to be a situation where we lose mass. Must investigate! |
|---|
| 16 | Importance: Mid-High |
|---|
| 17 | Action: Check out boundary condition |
|---|
| 18 | |
|---|
| 19 | |
|---|
| 20 | |
|---|
| 21 | CLOSED ISSUES: |
|---|
| 22 | ------------ |
|---|
| 23 | Issue: Segments in pmesh that are solely used to separate regions |
|---|
| 24 | (e.g. for different resolution) will appear as an *internal* |
|---|
| 25 | boundary in the resulting domain even though it may not have been intended to |
|---|
| 26 | have a boundary condition applied. |
|---|
| 27 | Background: Genuine internal boundaries are created the same way as |
|---|
| 28 | external boundaries through the 'boundary' dictionary mapping triangle_id |
|---|
| 29 | and edge number to a tag. |
|---|
| 30 | When a mesh is created, this dictionary will override the neighbour structure |
|---|
| 31 | and thereby enforce the internal boundary status. |
|---|
| 32 | This is all very well for 'True' internal boundaries. |
|---|
| 33 | However, once a segment belongs to a boundary (internal or external) |
|---|
| 34 | it must be bound to a boundary condition object in order to supply |
|---|
| 35 | values for the flux computations. Hence there is no way of allowing |
|---|
| 36 | normal flow between neighbouring triangles in the case where they are |
|---|
| 37 | separated by an (unintended) internal boundary. |
|---|
| 38 | An older version of pyvolution allowed None as a boundary object which |
|---|
| 39 | probably meant that a zero dirichlet condition was imposed. |
|---|
| 40 | Not sure about this, though. |
|---|
| 41 | Importance: High |
|---|
| 42 | Action: Actually the older version of pyvolution allowed None to mean |
|---|
| 43 | there are no boundaries. This is a usefull feature. So let's put it |
|---|
| 44 | back. Pmesh no longer defaults to "internal" for an untagged internal |
|---|
| 45 | boundary. It defaults to no tag. |
|---|
| 46 | Status: resolved |
|---|
