Hi Kamil, This is a known bug that we still need to address. In the XML file there is a <CURVED> section which stores the curvature information. If you remove all lines that begin with <F ID="..." FACEID="..." ... </F> the mesh should convert and you should obtain a curved mesh. What happens here is that gmsh supplies face-interior curvature, which presently is not reordered correctly, causing intersecting elements. However edge curvature will still work, and this will be blended onto the interior of the element by our basis functions. Whenever I get a chance I'll try to patch this issue as it's not really ideal! Thanks, Dave On 22 Sep 2014, at 08:46, Kamil Ozden <kamil.ozden.me@gmail.com> wrote:
Dear All,
Regarding my previous question I found that there is an option in Gmsh to get higher order elements for reflecting curvature of the edges into .xml file. However, when I increase the order of the element from 1 to a higher order (e.g. 3) and convert the .xml file to .vtu file I got the message:
Warning: Level 0 assertion violation 3D deformed Jacobian not positive (element ID = 359) (first vertex ID = 206)
and the mesh that MeshConvert obtained from Gmsh's .msh file looks like:
<biabjfca.png>
As far as I know "Jacobian not positive" means there are intersecting elements. What may be the reason for this problem?
Regards, Kamil
On 18-09-2014 11:36, Kamil Ozden wrote:
Dear All,
I mesh a circular pipe in Gmsh very coarsely as below and turn it into a xml file via MeshConvert. However, the curved edge information is not transferred to the xml file (as seen in the figure at right). How can I succeed this? Is there any way of doing it in Gmsh or is this directly related with Nektar++ ?
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users