Thank you for your sharing. To my mind, after we generate Q2 mesh in Gmsh, 
we have all the information about vertices and cells. We can read these 
information to deal.ii as point list and cell list, and then generate mesh 
like step-14 and 49. But still, I am not sure whether deal.ii supports 
higher order elements. 

在 2016年9月21日星期三 UTC-4下午11:27:22,Praveen C写道:
> Having curved boundaries alone is not sufficient sometimes. One would like 
> to use curved elements in the interior also. It would be very useful if one 
> could read high order meshes, e.g., from gmsh. The extra nodes can be used 
> to create an euler vector that can be used in a MappingFEField.
> There has been some discussion on this in the group, see e.g.,
> Chenchen, see "Option A" in Luca's response which is relevant to your 
> problem. 
> I tried to do this approach, but did not complete it yet. See my attempt 
> here
> This code reads a high order gmsh grid but ignores all extra points. In a 
> second step, one has to read all the points and create an euler vector. 
> There is a reordering of vertices in each cell (see line 486), which needs 
> extra work to create the euler vector. I was pursuing a different approach 
> to high order meshes, and haven't been able to work on this.
> Best
> praveen

The deal.II project is located at
For mailing list/forum options, see
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to