dolfin team mailing list archive

[Christine Tobler <christinetobler@xxxxxxxx>]

Public bug reported:

I wanted to save the boundary of a 3d mesh to an m-file, but it turns
out only the x and y coordinate are saved. The function
MFile::operator<<(const Mesh& mesh) uses mesh.type().cell_type() ==
CellType::triangle to determine how many coordinates of the vertices
need to be saved.

I believe it should either save x, y and z all the time, as VTKFile
does; or use mesh.geometry().dim() to determine the number of
coordinates needed, as XMLFile does.

A try for a patch (similar to XMLFile) is in the attachment,
unfortunately it's untested, as I only have a binary installation of
dolfin.

** Affects: dolfin
     Importance: Undecided
         Status: New

-- 
MFile of embedded mesh - 3rd coordinate is cut off
https://bugs.launchpad.net/bugs/595638
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.

Status in DOLFIN: New

Bug description:
I wanted to save the boundary of a 3d mesh to an m-file, but it turns out only the x and y coordinate are saved. The function MFile::operator<<(const Mesh& mesh) uses mesh.type().cell_type() == CellType::triangle to determine how many coordinates of the vertices need to be saved.

I believe it should either save x, y and z all the time, as VTKFile does; or use mesh.geometry().dim() to determine the number of coordinates needed, as XMLFile does.

A try for a patch (similar to XMLFile) is in the attachment, unfortunately it's untested, as I only have a binary installation of dolfin.