Thank you for the file. I have found and fixed the problem.
Just to let you know - Gmsh 4.12 is finally out. From changelog:
4.12.0 (December 21, 2023): new high-order mesh optimisation mode for periodic
meshes; new element qualities available through API; new IGES export; new volume
glyph; OCC curve loops can now be oriented based on the sign of the first curve;
better mesh node visualization; added suppport for model attributes in MSH2
files; new mesh renumbering capabilities in the API; new GAMBIT mesh reader;
replaced Geometry.OCCSafeUnbind with more flexible Geometry.OCCFastUnbind (which
can be set for boolean operations as well); added support for editing STEP
headers; small bug fixes.
New API functions: model/getEntitiesForPhysicalName, mesh/computeRenumbering,
mesh/getVisibility.Incompatible API changes: new optional argument to occ/addCircleArc,
mesh/renumberNodes, mesh/renumberElements and view/getListData; new optional
“interruptible” argument to gmsh.initialize() in Python
thanks, hopefully it’s not having serious problem in PrePoMax to upgrades.
as i know, R-Tree algorithm for hex-dominant mesh being re-enabled at this version, even the result is not so good as previous version in 3.x due to some reasons.
Hi,
just one more thing i’d like to suggest is adding the option “progression” for edges (bias factor).
Thank you
indeed it’s a useful feature i’m missing also. similar to bias command in CGX
I agree, but I need to add a feature to define the number of elements per edge first.