Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gmsh
gmsh
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gmsh
  • gmshgmsh
  • Issues
  • #1197

Closed
Open
Opened Feb 11, 2021 by marc belleau@spacecadet

Is the AttractorAnisoCurve Field really anisotropic ?

Hi everybody

My very first post and it is very simple: just a unit square geometry. This short .geo file uses the Gmsh 4.7.1 keywords. AttractorAnisoCurve should be computing the distance from Line(1) only, using the defaults for this field as listed in the Gmsh manual.

------- start of script -------

lc = .01;

Point(1) = { 0, 0, 0, lc} ; Point(2) = { 1, 0, 0, lc} ; Point(3) = { 1, 1, 0, lc} ; Point(4) = { 0, 1, 0, lc} ;

Line(1) = {1,2} ; Line(2) = {2,3} ; Line(3) = {3,4} ; Line(4) = {4,1} ;

Curve Loop(1) = {1, 2, 3, 4} ;

Plane Surface(1) = {1} ; //air only

Field[1] = AttractorAnisoCurve; Field[1].CurvesList = {1};

Background Field = 1;

Mesh.CharacteristicLengthFromPoints = 0; Mesh.CharacteristicLengthExtendFromBoundary = 0;

------- end of script -------

When you click on Mesh 2D in the GUI you end up with a mesh dimension in the direction tangent to Line(1) that varies as you move away from Line(1) even though it is clear from the defaults that SizeMaxTangent = SizeMinTangent = .5

Moreover, you get the same generated mesh irrespective of the values you assign to any of this field keywords

Field[1].NumPointsPerCurve Field[1].dMax Field[1].dMin Field[1].SizeMaxNormal Field[1].SizeMaxTangent Field[1].SizeMinNormal Field[1].SizeMinTangent

(So you cannot even override defaults)

Therefore I conclude that either there is a bug or I else I do not even grasp the basics of Gmsh.

Any reply welcome Thank you in advance

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gmsh/gmsh#1197