[Gmsh] High-Order Boundary layer with Subdivision Algorithm

[Willem Deconinck]

Thanks Christophe,

It worked like a charm! Really wonderful :-)

-Willem

On 04 Mar 2014, at 14:07, Christophe Geuzaine <cgeuzaine at ulg.ac.be> wrote:

> 
> On 24 Feb 2014, at 20:07, Willem Deconinck <willem.deconinck at vub.ac.be> wrote:
> 
>> Dear Thomas,
>> 
>> First off, congratulations for the nice work on high-order boundary layers.
>> There are however a few things I noticed that were not working properly, and I don't know if you are aware.
>> 
>> I have tested following also with todays nightly build (24/02/2014)
>> 
>> I found the high-order boundary layer optimization algorithm to work very well for cases without subdivision algorithms.
>> However, when I recombine with "All Quads" subdivision algorithm, the subdivision-node is not recognized to fall on the CAD edge for non-linear
>> boundaries. The high-order optimization algorithm also fails to correct for this.
>> In attachment I send the geo file illustrating this problem, with a very simple square geometry with a hole.
>> If I enlarge the hole, to a point there are no intersections, all is fine.
>> 
>> 
>> On another note, when I last spoke with you at VKI, I mentioned it would be nice to have more parallel support for field visualisation in gmsh.
>> A parallel-aware file format e.g. which combines multiple  ".msh" files generated by a parallel simulation.
>> It would then e.g. combine all views that belong to the same field in one view, and when options are modified for one,
>> it modifies it for all of them together.
>> I have tried to do this by creating a file "out.msh"  with content
>> """
>> Merge "out_P0.msh";
>> Merge "out_P1.msh";
>> Merge "out_P2.msh";
>> Merge "out_P3.msh";
>> """
> 
> Dear Willem,
> 
> Just add a partition ID as a forth value in the list of integers describing the view; merging the different files will "complete" the view as they are loaded. (This is fully dynamic; you can load partial results/time steps; each result can also be based on a completely different mesh.)
> 
> Hope this helps,
> 
> Christophe
> 
> 
>> I thought perhaps "Combine elements by name" would then do the trick,
>> but I get "Combine space is not implemented for this kind of data".
>> Not sure how much work this involves, but that is really a must-have feature to me.
>> The type of options I would modify on this parallel view would mostly be "Adapt Visualization Mesh", and global Contour-Min-Max values.
>> 
>> Best regards,
>> Willem
>> 
>> <circle_bdry_layer.geo>_______________________________________________
>> gmsh mailing list
>> gmsh at geuz.org
>> http://www.geuz.org/mailman/listinfo/gmsh
> 
> -- 
> Prof. Christophe Geuzaine
> University of Liege, Electrical Engineering and Computer Science 
> http://www.montefiore.ulg.ac.be/~geuzaine
> 
> 
>