Merge lp:~fluidity-core/fluidity/fluidity-gmsh2triangle-fix-reordering into lp:fluidity
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 3950 | ||||
Proposed branch: | lp:~fluidity-core/fluidity/fluidity-gmsh2triangle-fix-reordering | ||||
Merge into: | lp:fluidity | ||||
Diff against target: |
87 lines (+10/-30) 1 file modified
tools/gmsh2triangle.py (+10/-30) |
||||
To merge this branch: | bzr merge lp:~fluidity-core/fluidity/fluidity-gmsh2triangle-fix-reordering | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Cian Wilson | Approve | ||
Review via email: mp+97371@code.launchpad.net |
Description of the change
This deals with bug https:/
"The script gmsh2triangle tries to identify isolated nodes that are not attached to any elements (isolated nodes) and leaves these out of the output triangle files. This requires a renumbering of the nodes. However this renumbering is only applied to the .ele file but not .edge/.face file. Thus this renumbering only works correctly when the isolated nodes have node numbers that are bigger than any of the boundary nodes. Otherwise the node numbering of the surface mesh and the interior mesh no longer correspond leading to very onobvious errors in fluidity."
Fixed by no longer applying any renumbering. This was decided to be the best fix as gmsh meshes are now also be readable directly by fluidity, in which case isolated nodes would be read as well. So if isolated nodes are present in the input gmsh .msh it's up to the user to fix.
Looks good. Is there a buildbot queue?