dolfin-convert crashes on meshes generated by triangle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DOLFIN |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Consider trying to use a simple mesh generated by triangle:
[pef@aislinn:/tmp]$ cat simple.node
4 2 0 0
0 0 0
1 0 1
2 1 0
3 1 1
[pef@aislinn:/tmp]$ triangle simple.node
Opening simple.node.
Constructing Delaunay triangulation by divide-and-conquer method.
Delaunay milliseconds: 0
Writing simple.1.node.
Writing simple.1.ele.
Output milliseconds: 0
Total running milliseconds: 0
Statistics:
Input vertices: 4
Mesh vertices: 4
Mesh triangles: 2
Mesh edges: 5
Mesh exterior boundary edges: 4
[pef@aislinn:/tmp]$ dolfin-convert simple.1.node simple.xml
Converting from Triangle format {.node, .ele} to DOLFIN XML format
Expecting 4 vertices
Found all vertices
Expecting 2 cells
Traceback (most recent call last):
File "/usr/bin/
main(
File "/usr/bin/
meshconvert
File "/usr/lib/
convert(
File "/usr/lib/
triangle2xm
File "/usr/lib/
write_
NameError: global name 'write_
I've attached a (very simple) patch.
Related branches
- Registry Administrators: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifiedsite-packages/dolfin_utils/meshconvert/meshconvert.py (+1/-1)
Changed in dolfin: | |
status: | New → In Progress |
Changed in dolfin: | |
status: | In Progress → Fix Committed |
Changed in dolfin: | |
status: | Fix Committed → Fix Released |
That's embarrassing. Do we not run tests on the supplied meshes in scripts/ dolfin- convert ?